ctags indexing ("make tags" command) throws this warning:
ctags: Warning: include/linux/notifier.h:125:
null expansion of name pattern "\1"
This is the result of DEFINE_PER_CPU() macro exapansion. Fix that by
getting rid of line break.
Similar fix was already done in commit 25528213fe9f
On 10/29/18 2:00 PM, Bart Van Assche wrote:
> On Mon, 2018-10-29 at 13:53 -0600, Jens Axboe wrote:
>> On 10/29/18 1:40 PM, Bart Van Assche wrote:
>>> On Mon, 2018-10-29 at 10:37 -0600, Jens Axboe wrote:
-static int cpu_to_queue_index(unsigned int nr_queues, const int cpu)
+static int cpu_
Hi Greg,
On Mon, Oct 29, 2018 at 10:09 PM, Sam Protsenko
wrote:
> ctags indexing ("make tags" command) throws this warning:
>
> ctags: Warning: include/linux/notifier.h:125:
> null expansion of name pattern "\1"
>
> This is the result of DEFINE_PER_CPU() macro exapansion. Fix that by
> ge
On Wed 17-10-18 16:54:08, Alexander Duyck wrote:
> This change makes it so that we use the same approach that was already in
> use on Sparc on all the archtectures that support a 64b long.
>
> This is mostly motivated by the fact that 7 to 10 store/move instructions
> are likely always going to be
On Mon, Oct 29, 2018 at 10:09 PM Sam Protsenko
wrote:
>
> ctags indexing ("make tags" command) throws this warning:
>
> ctags: Warning: include/linux/notifier.h:125:
> null expansion of name pattern "\1"
>
> This is the result of DEFINE_PER_CPU() macro exapansion. Fix that by
> getting rid
Dear RT Folks,
This is the RT stable review cycle of patch v4.4.162-rt176-rc1.
Please scream at me if I messed something up. Please test the patches
too.
The -rc release will be uploaded to kernel.org and will be deleted
when the final release is out. This is just a review release (or
release ca
From: Daniel Wagner
v4.4.162-rt176-rc1 stable review patch.
If anyone has any objections, please let me know.
---
Sebastian writes:
"""
We reproducibly observe cache line starvation on a Core2Duo E6850 (2
cores), a i5-6400 SKL (4 cores) and on a NXP LS2044A ARM Cortex-A72 (4
cores).
v4.4.162-rt176-rc1 stable review patch.
If anyone has any objections, please let me know.
---
Signed-off-by: Daniel Wagner
---
localversion-rt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/localversion-rt b/localversion-rt
index 8ead11a7cbc7..c3267d6bdd98 100644
-
From: Long Li Sent: Monday, October 22, 2018 6:41 PM
>
> In irq_matrix, "available" is set when IRQs are allocated earlier in the IRQ
> assigning process.
>
> Later, when IRQs are activated those values are not good indicators of what
> CPU to choose to assign to this IRQ.
>
> Change to choose
Hi Loic,
On 10/24/18 10:14 AM, Loic PALLARDY wrote:
> Hi Suman,
>
>> -Original Message-
>> From: Suman Anna
>> Sent: mercredi 24 octobre 2018 02:14
>> To: Loic PALLARDY ; bjorn.anders...@linaro.org;
>> o...@wizery.com
>> Cc: linux-remotep...@vger.kernel.org; linux-kernel@vger.kernel.org;
On Mon 29-10-18 18:54:19, Roman Gushchin wrote:
> On Mon, Oct 29, 2018 at 05:35:38PM +0100, Mike Galbraith wrote:
> > On Mon, 2018-10-29 at 14:20 +0100, Michal Hocko wrote:
> > >
> > > > [4.420976] Code: f3 c3 0f 1f 00 0f 1f 44 00 00 48 85 ff 0f 84 a8 00
> > > > 00 00 41 56 48 89 f8 41 55 49
On 10/29/2018 04:00 PM, Davidlohr Bueso wrote:
> On Mon, 29 Oct 2018, Waiman Long wrote:
>
>> I am wondering if /proc/stat_noirqs will be a more descriptive name of
>> the intent of this new procfs file or we should just go with the more
>> generic stat2 name.
>
> The reason why I went with '2' ins
Andrei,
On Sat, 20 Oct 2018, Andrei Vagin wrote:
> When a container is migrated to another host, we have to restore its
> monotonic and boottime clocks, but we still expect that the container
> will continue using the host real-time clock.
>
> Before stating this series, I was thinking about this
On Mon, 29 Oct 2018, Waiman Long wrote:
BTW, since you are making stat2 compatible with stat, will that be
easier from the user API perspective if we use a sysctl parameter to
turn on and off IRQs reporting for /proc/stat, for example?
For one /proc/stat is also common for debugging envs (ie:
On Mon, 2018-10-29 at 18:54 +, Roman Gushchin wrote:
>
> Hi Mike!
>
> Thank you for the report!
>
> Do you see it reliable every time you boot up the machine?
Yeah.
> How do you run kvm?
My VMs are full SW/data clones of my i7-4790/openSUSE box.
> Is there something special about your
Hello, Jiri,
Thank you for the reply and your opinion. It appeared that my own implementation
of a ring buffer was kind of "inventing a wheel", as "kfifo" is already is the
kernel and it may work as a ring buffer quite well. I would like to rewrite my
patchset and use kfifo instead in a new one. P
On 10/29/2018 04:38 PM, Davidlohr Bueso wrote:
> On Mon, 29 Oct 2018, Waiman Long wrote:
>
>> BTW, since you are making stat2 compatible with stat, will that be
>> easier from the user API perspective if we use a sysctl parameter to
>> turn on and off IRQs reporting for /proc/stat, for example?
>
>
On 10/29/2018 03:25 PM, Davidlohr Bueso wrote:
> A recent report from a large database vendor which I shall not name
> shows concerns about poor performance when consuming /proc/stat info.
> Particularly kstat_irq() pops up in the profiles and most time is
> being spent there. The overall system i
Hi Linus,
please pull three small patches for the parisc architecture for 4.20-rc1 from:
git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux.git
parisc-4.20-2
Three small patches:
- A boot fix for A500 machines, crash was caused by the new alternative
patching code from this
[+cc Rafael, Len, Tony, Borislav, Tyler, Christoph, linux-acpi, LKML]
On Fri, Oct 26, 2018 at 02:19:04PM -0600, Jon Derrick wrote:
> Add a bit in pci_host_bridge to indicate to leave the System Error
> Interrupts as configured by the pre-boot environment. Propagate this to
> the AER driver which d
Hi, Oleg:
Yes, it should be the "real_parent" that is more interested in the notification.
Will revert back.
+static void do_notify_parent_predump(void)
+{
+ struct task_struct *parent;
+ int sig;
+
+ rcu_read_lock();
+ parent = rcu_dereference(current->real_parent);
+
On Mon, Oct 29, 2018 at 12:17 PM Harry Cutts wrote:
>
> I don't really understand why the half-multiplier thing would cause
> the instability; there's still a low-res threshold every 8 high-res
> units whichever way you do it
No there isn't.
So what the half-multiplier did, assuming a multiplier
In multi-master environment, this driver's master cannot know
exactly when a peer master sends data to this driver's slave so a
case can be happened that this master tries to send data through
the master_xfer function but slave data from peer master is still
being processed by this driver. To preve
This commit removes hard-coded bus timeout value setting so that
it can be set by i2c-core-base.
Signed-off-by: Jae Hyun Yoo
Reviewed-by: Joel Stanley
Reviewed-by: Brendan Higgins
---
drivers/i2c/busses/i2c-aspeed.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/i2c/busses/i2c-aspe
In multi-master environment, this driver's master cannot know
exactly when a peer master sends data to this driver's slave so a
case can be happened that this master tries to send data through
the master_xfer function but slave data from peer master is still
being processed by this driver.
To prev
This commit adds 'bus-timeout-ms' and '#retries' properties as
common optional properties that can be used for setting 'timeout'
and 'retries' values of 'struct i2c_adapter'. With this patch, the
bus timeout value and the master transfer retries count can be set
through these properties at the regi
This commit adds 'bus-timeout-ms' property as an optional property
which can be used for setting the bus timeout value of an adapter.
With this patch, the bus timeout value can be set through this
property at the probing time of this module. Still the bus timeout
value can be set by an I2C_TIMEOUT
This commit adds support for 'bus-timeout-ms' and '#retries'
properties to set 'timeout' and 'retries' values in
'struct i2c_adapter' in case an adapter node has the properties.
Still the values can be set by I2C_TIMEOUT and I2C_RETRIES ioctls
on cdev at runtime too.
These properties may not be su
From: "Liang, Kan"
Date: Mon, 29 Oct 2018 14:20:15 -0400
> You didn't see any warning before the patch. I think it is just
> because perf top hides the problem.
Quite honestly, the last time I played around with this:
1) The new ring buffer mode didn't exist
2) perf started up much more quickl
On 25/10/2018 01:13, Peter Zijlstra wrote:
On Wed, Oct 24, 2018 at 12:35:03AM +0300, Igor Stoppa wrote:
+static __always_inline
+bool __pratomic_long_op(bool inc, struct pratomic_long_t *l)
+{
+ struct page *page;
+ uintptr_t base;
+ uintptr_t offset;
+ unsigned long f
Hi Linus,
Here are the arm-soc changes for the current merge window, with a
little delay due to the conference travel last week.
This is feels a little bigger than the last few I did before Olof took
over for the summer. We have 965 non-merge changesets in the
branch, and we pulled from a total o
The following changes since commit 57361846b52bc686112da6ca5368d11210796804:
Linux 4.19-rc2 (2018-09-02 14:37:30 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git tags/armsoc-dt
for you to fetch changes up to be59a3282cf8e0c9c82e883
The following changes since commit 11da3a7f84f19c26da6f86af878298694ede0804:
Linux 4.19-rc3 (2018-09-09 17:26:43 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git
tags/armsoc-defconfig
for you to fetch changes up to e8c3f6322cc85308
On Mon, Oct 29, 2018 at 04:59:03PM -0400, Waiman Long wrote:
> On 10/29/2018 04:38 PM, Davidlohr Bueso wrote:
> > On Mon, 29 Oct 2018, Waiman Long wrote:
> >
> >> BTW, since you are making stat2 compatible with stat, will that be
> >> easier from the user API perspective if we use a sysctl paramete
Thomas Gleixner writes:
> Andrei,
>
> On Sat, 20 Oct 2018, Andrei Vagin wrote:
>> When a container is migrated to another host, we have to restore its
>> monotonic and boottime clocks, but we still expect that the container
>> will continue using the host real-time clock.
>>
>> Before stating th
The following changes since commit 5a1eb8b9542884592a018829bb1ff20c9695d925:
soc: fsl: qman_portals: defer probe after qman's probe (2018-10-01
17:47:43 -0500)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git
tags/armsoc-drivers
for you t
The following changes since commit 57361846b52bc686112da6ca5368d11210796804:
Linux 4.19-rc2 (2018-09-02 14:37:30 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git tags/armsoc-soc
for you to fetch changes up to f4f9554f16d0a14b8ced9b
Long,
On Tue, 23 Oct 2018, Long Li wrote:
thanks for this patch.
A trivial formal thing ahead. The subject line
[PATCH] Choose CPU based on allocated IRQs
is lacking a proper subsystem prefix. In most cases you can figure the
prefix out by running 'git log path/to/file' which in this case w
On Mon, 29 Oct 2018 13:56:54 -0500
Wenwen Wang wrote:
> Hello,
>
> Could you please apply this patch? Thanks!
I'd like to see testing and/or review from David or Alexey since I also
don't have an environment for spapr/eeh. We're already late into the
v4.20 merge window so this is probably v4.2
On 10/29/2018 05:23 PM, Vito Caputo wrote:
> On Mon, Oct 29, 2018 at 04:59:03PM -0400, Waiman Long wrote:
>> On 10/29/2018 04:38 PM, Davidlohr Bueso wrote:
>>> On Mon, 29 Oct 2018, Waiman Long wrote:
>>>
BTW, since you are making stat2 compatible with stat, will that be
easier from the us
On Mon, Oct 29, 2018 at 4:32 PM Alex Williamson
wrote:
>
> On Mon, 29 Oct 2018 13:56:54 -0500
> Wenwen Wang wrote:
>
> > Hello,
> >
> > Could you please apply this patch? Thanks!
>
> I'd like to see testing and/or review from David or Alexey since I also
> don't have an environment for spapr/eeh.
Eric,
On Mon, 29 Oct 2018, Eric W. Biederman wrote:
> Thomas Gleixner writes:
> >
> > I'll try to find some time in the next weeks to look deeper into that, but
> > I can't promise anything before returning from LPC. Btw, LPC would be a
> > great opportunity to discuss that. Are you and the other
On Mon, 29 Oct 2018 at 14:12, Linus Torvalds
> So what the half-multiplier did, assuming a multiplier of 8 (which is
> what my MX Anywhere 2S reports) would be:
>
> - remainder starts at 3
> - high-res is +1
> - now remainder is 3+1, and it triggers the >= half logic
> - 4/8 is 0, but then the
On Mon, Oct 29, 2018 at 7:58 AM, Christian Brauner wrote:
> On Wed, Oct 17, 2018 at 12:33:20AM +0200, Christian Brauner wrote:
>> Hey,
>>
>> Here is v3 of this patchset. Changelogs are in the individual commits.
>>
>> Currently, when writing
>>
>> echo 18446744073709551616 > /proc/sys/fs/file-max
On Mon, Oct 29, 2018 at 12:05 PM Wolfram Sang wrote:
>
> I2C has not so much stuff this time. Mostly driver enablement for new
> SoCs, some driver bugfixes, and some cleanups.
Pulled,
Linus
On Mon, Oct 29, 2018 at 09:26:34PM +0100, Michal Hocko wrote:
> On Mon 29-10-18 18:54:19, Roman Gushchin wrote:
> > On Mon, Oct 29, 2018 at 05:35:38PM +0100, Mike Galbraith wrote:
> > > On Mon, 2018-10-29 at 14:20 +0100, Michal Hocko wrote:
> > > >
> > > > > [4.420976] Code: f3 c3 0f 1f 00 0f
On Mon, Oct 29, 2018 at 09:46:54PM +0100, Mike Galbraith wrote:
> On Mon, 2018-10-29 at 18:54 +, Roman Gushchin wrote:
> >
> > Hi Mike!
> >
> > Thank you for the report!
> >
> > Do you see it reliable every time you boot up the machine?
>
> Yeah.
>
> > How do you run kvm?
>
> My VMs are f
Hi Fenghua, Sai,
> -Original Message-
> From: Fenghua Yu
> Sent: Thursday, October 25, 2018 6:07 PM
> To: Thomas Gleixner ; Ingo Molnar
> ; H Peter Anvin ; Tony Luck
> ; Peter Zijlstra ; Reinette
> Chatre ; Moger, Babu
> ; James Morse ; Ravi V
> Shankar ; Sai Praneeth Prakhya
> ; Arshiya
Mike Galbraith reported a regression caused by the commit 9b6f7e163cd0
("mm: rework memcg kernel stack accounting") on a system with
"cgroup_disable=memory" boot option: the system panics with the
following stack trace:
[0.928542] BUG: unable to handle kernel NULL pointer dereference at
000
On 10/29/18 12:59 PM, Rob Herring wrote:
> +Ard who last touched this.
>
> On Mon, Oct 29, 2018 at 2:23 PM Florian Fainelli wrote:
>>
>> ARM64 is the only architecture that re-defines
>> __early_init_dt_declare_initrd() in order for that function to populate
>> initrd_start/initrd_end with physic
On 29 October 2018 at 16:59, Rob Herring wrote:
> +Ard who last touched this.
>
> On Mon, Oct 29, 2018 at 2:23 PM Florian Fainelli wrote:
>>
>> ARM64 is the only architecture that re-defines
>> __early_init_dt_declare_initrd() in order for that function to populate
>> initrd_start/initrd_end with
Fenghua, Sai
> -Original Message-
> From: Fenghua Yu
> Sent: Thursday, October 25, 2018 6:07 PM
> To: Thomas Gleixner ; Ingo Molnar
> ; H Peter Anvin ; Tony Luck
> ; Peter Zijlstra ; Reinette
> Chatre ; Moger, Babu
> ; James Morse ; Ravi V
> Shankar ; Sai Praneeth Prakhya
> ; Arshiya Haya
On Mon, Oct 29, 2018 at 2:42 PM Harry Cutts wrote:
>
> Ah, I see what you mean. So, if we move the threshold to (multiplier -
> 1)/multiplier (7/8) in this case, I think the equivalent scenario
> would be:
That would work, yes.
Except I think you *do* want the "reset on direction change" logic,
On 10/29/18 2:08 PM, Dean Wallace wrote:
On 29-10-18, Andy Shevchenko wrote:
On Mon, Oct 29, 2018 at 7:52 PM Andy Shevchenko
wrote:
Cc: Pierre as well.
On Mon, Oct 29, 2018 at 7:48 PM Stephen Boyd wrote:
Quoting Dean Wallace (2018-10-25 16:25:17)
I have found a regression in 4.18.15 that
Hi Fenghua/Sai,
> -Original Message-
> From: Fenghua Yu
> Sent: Thursday, October 25, 2018 6:07 PM
> To: Thomas Gleixner ; Ingo Molnar
> ; H Peter Anvin ; Tony Luck
> ; Peter Zijlstra ; Reinette
> Chatre ; Moger, Babu
> ; James Morse ; Ravi V
> Shankar ; Sai Praneeth Prakhya
> ; Arshiya
On Mon, Oct 29, 2018 at 2:04 PM Helge Deller wrote:
>
> Three small patches:
Pulled,
Linus
Add a simple proc-based kill interface. To use /proc/pid/kill, just
write the signal number in base-10 ASCII to the kill file of the
process to be killed: for example, 'echo 9 > /proc/$$/kill'.
Semantically, /proc/pid/kill works like kill(2), except that the
process ID comes from the proc filesyst
Fenghua/Sai,
> -Original Message-
> From: Fenghua Yu
> Sent: Thursday, October 25, 2018 6:07 PM
> To: Thomas Gleixner ; Ingo Molnar
> ; H Peter Anvin ; Tony Luck
> ; Peter Zijlstra ; Reinette
> Chatre ; Moger, Babu
> ; James Morse ; Ravi V
> Shankar ; Sai Praneeth Prakhya
> ; Arshiya Haya
Problem:
The card detect IRQ does not work with modern BIOS (that want
to use _DSD to provide the card detect GPIO to the driver).
Details:
The mmc core provides the mmc_gpiod_request_cd() API to let host drivers
request the gpio descriptor for the "card detect" pin.
This pin is specified in the
For simplicity and consistency, this patch provides an implementation
for signal-based fault notification prior to the coredump of a child
process. A new prctl command, PR_SET_PREDUMP_SIG, is defined that can
be used by an application to express its interest and to specify the
signal for such a not
There is no problem with the message, the problem is the thread where
the message is being displayed, just signal the display thread to
display the warning, not doing that in the event processing thread.
How about this patch (just did some simple test)? It moves the warning
to display thr
Building with -Wformat-nonliteral, gcc complains
kernel/trace/trace_output.c: In function ‘seq_print_sym’:
kernel/trace/trace_output.c:356:3: warning: format not a string literal,
argument types not checked [-Wformat-nonliteral]
trace_seq_printf(s, fmt, name);
But seq_print_sym only has a sin
Playing around with -Wformat-nonliteral, I stumbled on two instances
in trace_output.c. Looking at the code a bit, turns out one can remove
the use of the non-constant format string and eliminate some code
duplication at the same time.
v2: Include cover letter, rename argument with_offset -> offse
trace_seq_printf(..., "%s", ...) can be done with trace_seq_puts()
instead, avoiding printf overhead. In the second instance, the string
we're copying was just created from an snprintf() to a stack buffer, so
we might as well do that printf directly. This naturally leads to moving
the declaration o
These two functions are nearly identical, so we can avoid some code
duplication by moving the conditional into a common implementation.
Signed-off-by: Rasmus Villemoes
---
kernel/trace/trace_output.c | 34 +++---
1 file changed, 7 insertions(+), 27 deletions(-)
diff
Raju,
On Thu, 11 Oct 2018, Raju P.L.S.S.S.N wrote:
>
> +/**
> + * tick_nohz_get_next_wakeup - return the next wake up of the CPU
Lacks documentation of @cpu. Please include kernel docs into your test
builds.
> + */
> +ktime_t tick_nohz_get_next_wakeup(int cpu)
> +{
> + struct clock_event_d
This patch introduces a means for syscalls matched in seccomp to notify
some other task that a particular filter has been triggered.
The motivation for this is primarily for use with containers. For example,
if a container does an init_module(), we obviously don't want to load this
untrusted code,
Hi everyone,
Here's v8 of the seccomp trap to userspace series. Major changes are:
* dropped the ptrace API all together. I believe based on the last
thread that it could be made safe by adding a check on the refcount of
the filter when grabbing it, but that sort of feels like a hack and
it
On Mon, Oct 29, 2018 at 2:18 PM Arnd Bergmann wrote:
>
> Here are the arm-soc changes for the current merge window, with a
> little delay due to the conference travel last week.
All merged. A few conflicts in MAINTAINERS, and a couple of trivial
ones, but nothing that looked too annoying.
Please
The idea here is just to give a demonstration of how one could safely use
the SECCOMP_RET_USER_NOTIF feature to do mount policies. This particular
policy is (as noted in the comment) not very interesting, but it serves to
illustrate how one might apply a policy dodging the various TOCTOU issues.
S
On Mon, Oct 29, 2018 at 05:35:15PM -0400, Waiman Long wrote:
> On 10/29/2018 05:23 PM, Vito Caputo wrote:
> > On Mon, Oct 29, 2018 at 04:59:03PM -0400, Waiman Long wrote:
> >> On 10/29/2018 04:38 PM, Davidlohr Bueso wrote:
> >>> On Mon, 29 Oct 2018, Waiman Long wrote:
> >>>
> BTW, since you ar
From: "Liang, Kan"
Date: Mon, 29 Oct 2018 18:32:40 -0400
> - struct annotation_options *annotation_options
> __maybe_unused)
> + struct annotation_options *annotation_options __maybe_unused,
> + atomic_t *nr_rb_read __maybe_unused)
> {
On Mon, 29 Oct 2018 21:15:01 +0800 kernel test robot
wrote:
> FYI, we noticed the following commit (built with gcc-7):
>
> commit: 68c37ccedcde10514898f4ba3b28c0de85c590d1 ("mm: nobootmem: remove
> bootmem allocation APIs")
> https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git mas
On Thu, Oct 25, 2018 at 07:56:26AM +, visionsofal...@redchan.it wrote:
> The linux devs can rescind their license grant.
Greg KH responded on Thu, 25 Oct 2018 09:19:11 +0100:
>> No they can not, please do not keep spreading false information.
I was explicitly cc'ed on this thread by visionsofa
Hi Jae,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on wsa/i2c/for-next]
[also build test WARNING on v4.19 next-20181029]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci
On 10/26/18 4:44 PM, Jan H. Schönherr wrote:
On 19/10/2018 02.26, Subhra Mazumdar wrote:
Hi Jan,
Hi. Sorry for the delay.
On 9/7/18 2:39 PM, Jan H. Schönherr wrote:
The collective context switch from one coscheduled set of tasks to another
-- while fast -- is not atomic. If a use-case need
Hi Fenghua,
> -Original Message-
> From: linux-kernel-ow...@vger.kernel.org ow...@vger.kernel.org> On Behalf Of Fenghua Yu
> Sent: Thursday, October 25, 2018 6:07 PM
> To: Thomas Gleixner ; Ingo Molnar
> ; H Peter Anvin ; Tony Luck
> ; Peter Zijlstra ; Reinette
> Chatre ; Moger, Babu
> ;
On Mon, 29 Oct 2018 at 15:01, Linus Torvalds
wrote:
> That would work, yes.
OK, I'll write a patch for this. (It may be next week, though, as I
have a deadline on a separate project this week.)
> Except I think you *do* want the "reset on direction change" logic,
> because otherwise we still end
On Mon, Oct 29, 2018 at 7:25 PM, Davidlohr Bueso wrote:
> This patch introduces a new /proc/stat2 file that is identical to the
> regular 'stat' except that it zeroes all hard irq statistics. The new
> file is a drop in replacement to stat for users that need performance.
For a while now, I've be
On 2018-10-29 21:16:16 [+0100], Daniel Wagner wrote:
> From: Daniel Wagner
>
> v4.4.162-rt176-rc1 stable review patch.
> If anyone has any objections, please let me know.
I though that we are going to route this via Greg/stable for v4.4?
> --- a/arch/x86/Kconfig
> +++ b/arch/x86/Kconfig
> @@ -4
On 28/10/18 1:39 am, Boris Brezillon wrote:
> Hi Brett,
>
> On Tue, 16 Oct 2018 00:57:41 +
> "Grandbois, Brett" wrote:
>
>> Add support to expose the SPI boot flash on AMD Family 16h CPUs as a
>> standard mtd device to give userspace BIOS updaters greater feature
>> support. The BIOS and Ker
From: Alex Williams
Now the DMA engine is free to float elsewhere in the system map.
Signed-off-by: Alex Williams
---
Documentation/devicetree/bindings/net/nixge.txt | 14 +++---
1 file changed, 11 insertions(+), 3 deletions(-)
diff --git a/Documentation/devicetree/bindings/net/nixge.
From: Colin Ian King
Currently a failure when calling ubifs_read_nnode results in a leak
of desc and buf because of a direct return. Fix this by exiting via
label 'out' that performs the necessary free'ing of the resources.
Fixes: a1dc58140f7e ("ubifs: authentication: Authenticate LPT")
Signed-
On Mon, Oct 29, 2018 at 4:58 PM Ard Biesheuvel
wrote:
>
> On 29 October 2018 at 16:59, Rob Herring wrote:
> > +Ard who last touched this.
> >
> > On Mon, Oct 29, 2018 at 2:23 PM Florian Fainelli
> > wrote:
> >>
> >> ARM64 is the only architecture that re-defines
> >> __early_init_dt_declare_ini
The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:
Linux 4.19-rc1 (2018-08-26 14:11:59 -0700)
are available in the Git repository at:
git://github.com/andersson/remoteproc tags/rproc-v4.20
for you to fetch changes up to f18b7e914fd2ed5e8b5733644cefcf62f7582679:
The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:
Linux 4.19-rc1 (2018-08-26 14:11:59 -0700)
are available in the Git repository at:
git://github.com/andersson/remoteproc tags/rpmsg-v4.20
for you to fetch changes up to 928002a5e9dab2ddc1a0fe3e00739e89be30dc6b:
On Mon, Oct 29, 2018 at 04:40:31PM -0600, Tycho Andersen wrote:
> The idea here is just to give a demonstration of how one could safely use
> the SECCOMP_RET_USER_NOTIF feature to do mount policies. This particular
> policy is (as noted in the comment) not very interesting, but it serves to
> illus
From: Colin Ian King
Replace a bunch of spaces with tab, cleans up indentation
Signed-off-by: Colin Ian King
---
kernel/events/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/events/core.c b/kernel/events/core.c
index 8c490130c4fb..84530ab358c3 100644
--- a/ke
Am Dienstag, 30. Oktober 2018, 00:21:46 CET schrieb Colin King:
> From: Colin Ian King
>
> Currently a failure when calling ubifs_read_nnode results in a leak
> of desc and buf because of a direct return. Fix this by exiting via
> label 'out' that performs the necessary free'ing of the resources.
> I'd much rather move to a model in which userspace *explicitly* tells
> the kernel which fields it wants, with the kernel replying with just
> those particular fields, maybe in their raw binary representations.
> The ASCII-text bag-of-everything files would remain available for
> ad-hoc and non-p
On Mon, Oct 29, 2018 at 11:34 PM, Alexey Dobriyan wrote:
>> I'd much rather move to a model in which userspace *explicitly* tells
>> the kernel which fields it wants, with the kernel replying with just
>> those particular fields, maybe in their raw binary representations.
>> The ASCII-text bag-of-
Hi Miguel,
Today's linux-next merge of the compiler-attributes tree got a conflict
in:
include/linux/compiler-gcc.h
between commit:
94c7dfd01652 ("kernel hacking: support building kernel with -Og optimization
level")
from the kbuild tree and commits:
5c67a52f3da0 ("Compiler Attributes:
Hi all,
On Tue, 30 Oct 2018 10:46:37 +1100 Stephen Rothwell
wrote:
>
> Today's linux-next merge of the compiler-attributes tree got a conflict
> in:
>
> include/linux/compiler-gcc.h
>
> between commit:
>
> 94c7dfd01652 ("kernel hacking: support building kernel with -Og
> optimization lev
Hi all,
The numbers no longer make any sense since I either did not correctly
understand the feedback being given, or dramatically changed the
approach.
This version introduces an architecture symbol: ARCH_HAS_PHYS_INITRD
which indicates whether the architecture cares/supports parsing the
physica
This will conflict with a subsequent change making phys_initrd_start and
phys_initrd_size global variables. nds32 does not make use of those nor
provides a suitable declarations so just get rid of them.
Signed-off-by: Florian Fainelli
---
arch/nds32/mm/init.c | 2 --
1 file changed, 2 deletions(
--
I solicit your cooperation to transfer $7 million to your bank account
and you will be entitled to 40% of this fund, respond urgent if you
are interested for more details.
Make phys_initrd_start and phys_initrd_size global variables that will
later be referenced by generic code under drivers/of/fdt.c.
Signed-off-by: Florian Fainelli
---
arch/arm/mm/init.c | 4 ++--
arch/unicore32/mm/init.c | 4 ++--
include/linux/initrd.h | 3 +++
3 files changed, 7 insert
With the one and only architecture (ARM64) no longer defining a custom
__early_init_dt_declare_initrd() function, just get rid of the check for
that function being already defined.
Signed-off-by: Florian Fainelli
---
drivers/of/fdt.c | 2 --
1 file changed, 2 deletions(-)
diff --git a/drivers/o
If the architecture implements ARCH_HAS_PHYS_INITRD, make the FDT
scanning code populate the physical address of the start of the FDT and
its size.
Signed-off-by: Florian Fainelli
---
arch/arm/mm/init.c | 2 +-
drivers/of/fdt.c | 4
2 files changed, 5 insertions(+), 1 deletion(-)
diff --
Make ARM and Unicore32 select ARCH_HAS_PHYS_INITRD meaning that they do
define phys_initrd_start/phys_initrd_size and make use of it.
Signed-off-by: Florian Fainelli
---
arch/Kconfig | 7 +++
arch/arm/Kconfig | 1 +
arch/unicore32/Kconfig | 1 +
3 files changed, 9 insertions(
401 - 500 of 572 matches
Mail list logo
