[PATCH v2 6/6] clk: mvebu: Expand mv98dx3236-core-clock support

The initial implementation in commit e120c17a70e5 ("clk: mvebu: support for 98DX3236 SoC") hardcoded a fixed value for the main PLL frequency. Port code from the Marvell supplied Linux kernel to support different PLL frequencies and provide clock gating support. Signed-off-by: Chris Packham

[PATCH v2 6/6] clk: mvebu: Expand mv98dx3236-core-clock support

The initial implementation in commit e120c17a70e5 ("clk: mvebu: support for 98DX3236 SoC") hardcoded a fixed value for the main PLL frequency. Port code from the Marvell supplied Linux kernel to support different PLL frequencies and provide clock gating support. Signed-off-by: Chris Packham ---

[PATCH v2 1/6] ARM: dts: Fix typo in armada-xp-98dx4251

The compatible should be 98dx4251 not 98dx4521. Signed-off-by: Chris Packham --- Notes: Changes in v2 - new arch/arm/boot/dts/armada-xp-98dx4251.dtsi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH v2 4/6] ARM: mvebu: Add mv98dx3236-soc-id

The DFX server on the 98dx3236 and compatible SoCs has an ID register that provides revision information that the PCI based ID register doesn't have. Use this if it's available. Signed-off-by: Chris Packham --- Notes: Changes in v2: - none

[PATCH v2 1/6] ARM: dts: Fix typo in armada-xp-98dx4251

The compatible should be 98dx4251 not 98dx4521. Signed-off-by: Chris Packham --- Notes: Changes in v2 - new arch/arm/boot/dts/armada-xp-98dx4251.dtsi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/boot/dts/armada-xp-98dx4251.dtsi

[PATCH v2 4/6] ARM: mvebu: Add mv98dx3236-soc-id

The DFX server on the 98dx3236 and compatible SoCs has an ID register that provides revision information that the PCI based ID register doesn't have. Use this if it's available. Signed-off-by: Chris Packham --- Notes: Changes in v2: - none

[PATCH] mm-page_alloc-use-static-global-work_struct-for-draining-per-cpu-pages-fix

From: Michal Hocko there is no need to have both pcpu_drain and pcpu_drain_mutex visible outside of drain_all_pages. This might just attract abuse. Signed-off-by: Michal Hocko --- Hi Andrew, Mel, I think this would be a good cleanup to be folded into

[PATCH] mm-page_alloc-use-static-global-work_struct-for-draining-per-cpu-pages-fix

From: Michal Hocko there is no need to have both pcpu_drain and pcpu_drain_mutex visible outside of drain_all_pages. This might just attract abuse. Signed-off-by: Michal Hocko --- Hi Andrew, Mel, I think this would be a good cleanup to be folded into

Re: [PATCH 00/12] Cqm2: Intel Cache quality monitoring fixes

On Tue, 7 Feb 2017, Stephane Eranian wrote: Hi, I wanted to take a few steps back and look at the overall goals for cache monitoring. From the various threads and discussion, my understanding is as follows. I think the design must ensure that the following usage models can be monitored: -

Re: [PATCH 00/12] Cqm2: Intel Cache quality monitoring fixes

On Tue, 7 Feb 2017, Stephane Eranian wrote: Hi, I wanted to take a few steps back and look at the overall goals for cache monitoring. From the various threads and discussion, my understanding is as follows. I think the design must ensure that the following usage models can be monitored: -

Re: [RFC/PATCH] arm64: Rename macro arguments to silence sparse

On 02/06/2017 05:50 PM, Luc Van Oostenryck wrote: > On Mon, Feb 06, 2017 at 05:08:17PM -0800, Stephen Boyd wrote: >> On 02/06/2017 05:01 PM, Stephen Boyd wrote: >>> When I compile files with sparse, I get these sorts of warnings: >>> >>> arch/arm64/include/asm/lse.h:14:28: warning: Unknown escape

Re: [RFC/PATCH] arm64: Rename macro arguments to silence sparse

On 02/06/2017 05:50 PM, Luc Van Oostenryck wrote: > On Mon, Feb 06, 2017 at 05:08:17PM -0800, Stephen Boyd wrote: >> On 02/06/2017 05:01 PM, Stephen Boyd wrote: >>> When I compile files with sparse, I get these sorts of warnings: >>> >>> arch/arm64/include/asm/lse.h:14:28: warning: Unknown escape

[PATCH] mm, page_alloc: do not depend on cpu hotplug locks inside the allocator

From: Michal Hocko Dmitry has reported the following lockdep splat [] lock_acquire+0x2a1/0x630 kernel/locking/lockdep.c:3753 [] __mutex_lock_common kernel/locking/mutex.c:521 [inline] [] mutex_lock_nested+0x24e/0xff0 kernel/locking/mutex.c:621 [] pcpu_alloc+0xbda/0x1280

[PATCH] mm, page_alloc: do not depend on cpu hotplug locks inside the allocator

From: Michal Hocko Dmitry has reported the following lockdep splat [] lock_acquire+0x2a1/0x630 kernel/locking/lockdep.c:3753 [] __mutex_lock_common kernel/locking/mutex.c:521 [inline] [] mutex_lock_nested+0x24e/0xff0 kernel/locking/mutex.c:621 [] pcpu_alloc+0xbda/0x1280 mm/percpu.c:896 []

Re: [PATCH 5/6] KVM: x86: do not scan IRR twice on APICv vmentry

2016-12-19 17:17+0100, Paolo Bonzini: > Calls to apic_find_highest_irr are scanning IRR twice, once > in vmx_sync_pir_from_irr and once in apic_search_irr. Change > sync_pir_from_irr to get the new maximum IRR from kvm_apic_update_irr; > now that it does the computation, it can also do the RVI

Re: [PATCH 5/6] KVM: x86: do not scan IRR twice on APICv vmentry

2016-12-19 17:17+0100, Paolo Bonzini: > Calls to apic_find_highest_irr are scanning IRR twice, once > in vmx_sync_pir_from_irr and once in apic_search_irr. Change > sync_pir_from_irr to get the new maximum IRR from kvm_apic_update_irr; > now that it does the computation, it can also do the RVI

Re: [PATCH v9] fs: clear file privilege bits when mmap writing

On Fri, Jan 27, 2017 at 7:47 PM, Andy Lutomirski wrote: > On Wed, May 25, 2016 at 2:49 PM, Al Viro wrote: >> On Wed, May 25, 2016 at 02:36:57PM -0700, Kees Cook wrote: >> >>> Hm, this didn't end up getting picked up. (This jumped out at me again >>>

Re: [PATCH v9] fs: clear file privilege bits when mmap writing

On Fri, Jan 27, 2017 at 7:47 PM, Andy Lutomirski wrote: > On Wed, May 25, 2016 at 2:49 PM, Al Viro wrote: >> On Wed, May 25, 2016 at 02:36:57PM -0700, Kees Cook wrote: >> >>> Hm, this didn't end up getting picked up. (This jumped out at me again >>> because i_mutex just vanished...) >>> >>> Al,

[for-next][PATCH 2/5] ktest: Fix child exit code processing

From: "Steven Rostedt (VMware)" The child_exit errno needs to be shifted by 8 bits to compare against the return values for the bisect variables. Fixes: c5dacb88f0a64 ("ktest: Allow overriding bisect test results") Cc: sta...@vger.kernel.org Signed-off-by: Steven Rostedt

[for-next][PATCH 4/5] ktest.pl: Powercycle the box on reboot if no connection can be made

From: "Steven Rostedt (VMware)" When performing a reboot of the test box, try to ssh to it. If it can't connect for 5 seconds, then powercycle the box. This is useful because the reboot is done via ssh, and if you can't ssh to the box because it is hung, the reboot fails to

[for-next][PATCH 2/5] ktest: Fix child exit code processing

From: "Steven Rostedt (VMware)" The child_exit errno needs to be shifted by 8 bits to compare against the return values for the bisect variables. Fixes: c5dacb88f0a64 ("ktest: Allow overriding bisect test results") Cc: sta...@vger.kernel.org Signed-off-by: Steven Rostedt (VMware) ---

[for-next][PATCH 4/5] ktest.pl: Powercycle the box on reboot if no connection can be made

From: "Steven Rostedt (VMware)" When performing a reboot of the test box, try to ssh to it. If it can't connect for 5 seconds, then powercycle the box. This is useful because the reboot is done via ssh, and if you can't ssh to the box because it is hung, the reboot fails to reboot.

[for-next][PATCH 3/5] ktest: Add timeout to ssh command

From: "Steven Rostedt (VMware)" Add a timeout to performing an ssh command. This will let testing if a machine is alive or not, or if something else may be amiss. A timeout can be passed to ssh, where ssh will fail if it does not complete within the given timeout.

[for-next][PATCH 1/5] ktest: Have POST_TEST run after the test has totally completed

From: "Steven Rostedt (VMware)" The POST_TEST config is to be executed after a test has fully compeleted, whether the test passed or failed. It currently is executed at the moment that the test has been decided if it failed or not. As the test does other clean ups, it isn't

[for-next][PATCH 3/5] ktest: Add timeout to ssh command

From: "Steven Rostedt (VMware)" Add a timeout to performing an ssh command. This will let testing if a machine is alive or not, or if something else may be amiss. A timeout can be passed to ssh, where ssh will fail if it does not complete within the given timeout. Signed-off-by: Steven Rostedt

[for-next][PATCH 1/5] ktest: Have POST_TEST run after the test has totally completed

From: "Steven Rostedt (VMware)" The POST_TEST config is to be executed after a test has fully compeleted, whether the test passed or failed. It currently is executed at the moment that the test has been decided if it failed or not. As the test does other clean ups, it isn't truly finished. Move

[for-next][PATCH 0/5] ktest: Updates for 4.11

git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-ktest.git for-next Head SHA1: 5739438b725c09938bb6af9e4477c4283b8326cf Steven Rostedt (VMware) (5): ktest: Have POST_TEST run after the test has totally completed ktest: Fix child exit code processing ktest: Add

[for-next][PATCH 0/5] ktest: Updates for 4.11

git://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-ktest.git for-next Head SHA1: 5739438b725c09938bb6af9e4477c4283b8326cf Steven Rostedt (VMware) (5): ktest: Have POST_TEST run after the test has totally completed ktest: Fix child exit code processing ktest: Add

[for-next][PATCH 5/5] ktest: Add variable run_command_status to save status of commands executed

From: "Steven Rostedt (VMware)" Create a variable called run_command_status that saves the status of the executed commands and can be used by other functions later to test for status. Signed-off-by: Steven Rostedt (VMware) ---

[for-next][PATCH 5/5] ktest: Add variable run_command_status to save status of commands executed

From: "Steven Rostedt (VMware)" Create a variable called run_command_status that saves the status of the executed commands and can be used by other functions later to test for status. Signed-off-by: Steven Rostedt (VMware) --- tools/testing/ktest/ktest.pl | 22 +++--- 1 file

Re: [PATCH 6/6] kvm: x86: do not use KVM_REQ_EVENT for APICv interrupt injection

2016-12-19 17:17+0100, Paolo Bonzini: > Since bf9f6ac8d749 ("KVM: Update Posted-Interrupts Descriptor when vCPU > is blocked", 2015-09-18) the posted interrupt descriptor is checked > unconditionally for PIR.ON. Therefore we don't need KVM_REQ_EVENT to > trigger the scan and, if NMIs or SMIs are

Re: [PATCH 6/6] kvm: x86: do not use KVM_REQ_EVENT for APICv interrupt injection

2016-12-19 17:17+0100, Paolo Bonzini: > Since bf9f6ac8d749 ("KVM: Update Posted-Interrupts Descriptor when vCPU > is blocked", 2015-09-18) the posted interrupt descriptor is checked > unconditionally for PIR.ON. Therefore we don't need KVM_REQ_EVENT to > trigger the scan and, if NMIs or SMIs are

Re: [PATCH] userfaultfd: mcopy_atomic: update cases returning -ENOENT

On Tue, Feb 07, 2017 at 05:02:50PM +0200, Mike Rapoport wrote: > Hello Andrew, > > The patch below is an incremental fixup for concerns Andrea raised at [1]. > Please let me know if you prefer me to update the original patch and > resend. > > [1]

Re: [PATCH] userfaultfd: mcopy_atomic: update cases returning -ENOENT

On Tue, Feb 07, 2017 at 05:02:50PM +0200, Mike Rapoport wrote: > Hello Andrew, > > The patch below is an incremental fixup for concerns Andrea raised at [1]. > Please let me know if you prefer me to update the original patch and > resend. > > [1]

Re: [PATCH] nohz: Fix possible missing clock reprog after tick soft restart

On Tue, 2017-02-07 at 17:44 +0100, Frederic Weisbecker wrote: > ts->next_tick keeps track of the next tick deadline in order to > optimize > clock programmation on irq exit and avoid redundant clock device > writes. > > Now if ts->next_tick missed an update, we may spuriously miss a clock >

Re: [PATCH] nohz: Fix possible missing clock reprog after tick soft restart

On Tue, 2017-02-07 at 17:44 +0100, Frederic Weisbecker wrote: > ts->next_tick keeps track of the next tick deadline in order to > optimize > clock programmation on irq exit and avoid redundant clock device > writes. > > Now if ts->next_tick missed an update, we may spuriously miss a clock >

Re: [RFC 1/1] shiftfs: uid/gid shifting bind mount

On Tue, 2017-02-07 at 11:49 -0800, Christoph Hellwig wrote: > On Tue, Feb 07, 2017 at 11:02:03AM -0800, James Bottomley wrote: > > > Another option would be to require something like a project as > > > used > > > for project quotas as the root. This would also be conveniant as > > > it > > >

Re: [RFC 1/1] shiftfs: uid/gid shifting bind mount

On Tue, 2017-02-07 at 11:49 -0800, Christoph Hellwig wrote: > On Tue, Feb 07, 2017 at 11:02:03AM -0800, James Bottomley wrote: > > > Another option would be to require something like a project as > > > used > > > for project quotas as the root. This would also be conveniant as > > > it > > >

[PATCH 15/18] HID-debug: Return an error code only as a constant in hid_debug_events_open()

From: Markus Elfring Date: Tue, 7 Feb 2017 20:08:04 +0100 * Return an error code without storing it in an intermediate variable. * Delete the local variable "err" and the jump label "out" which became unnecessary with this refactoring. Signed-off-by: Markus

[PATCH 15/18] HID-debug: Return an error code only as a constant in hid_debug_events_open()

From: Markus Elfring Date: Tue, 7 Feb 2017 20:08:04 +0100 * Return an error code without storing it in an intermediate variable. * Delete the local variable "err" and the jump label "out" which became unnecessary with this refactoring. Signed-off-by: Markus Elfring ---

[PATCH 14/18] HID-debug: Adjust two function calls together with a variable assignment

From: Markus Elfring Date: Tue, 7 Feb 2017 20:06:31 +0100 * The script "checkpatch.pl" pointed information out like the following. ERROR: do not use assignment in if condition Thus fix the affected source code places. * Replace the specification of a data

[PATCH 14/18] HID-debug: Adjust two function calls together with a variable assignment

From: Markus Elfring Date: Tue, 7 Feb 2017 20:06:31 +0100 * The script "checkpatch.pl" pointed information out like the following. ERROR: do not use assignment in if condition Thus fix the affected source code places. * Replace the specification of a data structure by a pointer

[PATCH 13/18] HID-debug: Combine 11 seq_printf() calls into one call in hid_dump_field()

From: Markus Elfring Date: Tue, 7 Feb 2017 20:04:28 +0100 Some data were printed into a sequence by eleven separate function calls. Print the same data by a single function call instead. Signed-off-by: Markus Elfring ---

[PATCH 13/18] HID-debug: Combine 11 seq_printf() calls into one call in hid_dump_field()

From: Markus Elfring Date: Tue, 7 Feb 2017 20:04:28 +0100 Some data were printed into a sequence by eleven separate function calls. Print the same data by a single function call instead. Signed-off-by: Markus Elfring --- drivers/hid/hid-debug.c | 23 +++ 1 file changed, 11

[PATCH 18/18] HID-picoLCD: Use seq_puts() in picolcd_debug_reset_show()

From: Markus Elfring Date: Tue, 7 Feb 2017 20:14:16 +0100 A string which did not contain a data format specification should be put into a sequence. Thus use the corresponding function "seq_puts". This issue was detected by using the Coccinelle software.

[PATCH 18/18] HID-picoLCD: Use seq_puts() in picolcd_debug_reset_show()

From: Markus Elfring Date: Tue, 7 Feb 2017 20:14:16 +0100 A string which did not contain a data format specification should be put into a sequence. Thus use the corresponding function "seq_puts". This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

[PATCH 16/18] HID-debug: Add some spaces for better code readability

From: Markus Elfring Date: Tue, 7 Feb 2017 20:10:40 +0100 Use space characters at some source code places according to the Linux coding style convention. Signed-off-by: Markus Elfring --- drivers/hid/hid-debug.c | 26

[PATCH 16/18] HID-debug: Add some spaces for better code readability

From: Markus Elfring Date: Tue, 7 Feb 2017 20:10:40 +0100 Use space characters at some source code places according to the Linux coding style convention. Signed-off-by: Markus Elfring --- drivers/hid/hid-debug.c | 26 ++ 1 file changed, 14 insertions(+), 12

[PATCH 17/18] HID-debug: Delete an unnecessary variable initialisation in hid_resolv_usage()

From: Markus Elfring Date: Tue, 7 Feb 2017 20:12:09 +0100 The local variable "buf" will be set to an appropriate pointer by the following statement. Thus omit the explicit initialisation at the beginning. Signed-off-by: Markus Elfring

[PATCH 17/18] HID-debug: Delete an unnecessary variable initialisation in hid_resolv_usage()

From: Markus Elfring Date: Tue, 7 Feb 2017 20:12:09 +0100 The local variable "buf" will be set to an appropriate pointer by the following statement. Thus omit the explicit initialisation at the beginning. Signed-off-by: Markus Elfring --- drivers/hid/hid-debug.c | 2 +- 1 file changed, 1

ATENCIÓN;

ATENCIÓN; Su buzón ha superado el límite de almacenamiento, que es de 5 GB definidos por el administrador, quien actualmente está ejecutando en 10.9GB, no puede ser capaz de enviar o recibir correo nuevo hasta que vuelva a validar su buzón de correo electrónico. Para revalidar su buzón de

ATENCIÓN;

ATENCIÓN; Su buzón ha superado el límite de almacenamiento, que es de 5 GB definidos por el administrador, quien actualmente está ejecutando en 10.9GB, no puede ser capaz de enviar o recibir correo nuevo hasta que vuelva a validar su buzón de correo electrónico. Para revalidar su buzón de

[PATCH 11/18] HID-debug: Delete an unnecessary seq_printf() call in hid_dump_device()

From: Markus Elfring Date: Tue, 7 Feb 2017 19:23:03 +0100 An information should be put into a sequence together with a line break. Pass the desired data in a single function call instead. Signed-off-by: Markus Elfring ---

[PATCH 11/18] HID-debug: Delete an unnecessary seq_printf() call in hid_dump_device()

From: Markus Elfring Date: Tue, 7 Feb 2017 19:23:03 +0100 An information should be put into a sequence together with a line break. Pass the desired data in a single function call instead. Signed-off-by: Markus Elfring --- drivers/hid/hid-debug.c | 3 +-- 1 file changed, 1 insertion(+), 2

[PATCH 12/18] HID-debug: Replace 12 seq_printf() calls by seq_puts()

From: Markus Elfring Date: Tue, 7 Feb 2017 20:02:45 +0100 Strings which did not contain data format specifications should be put into a sequence. Thus use the corresponding function "seq_puts". This issue was detected by using the Coccinelle software.

[PATCH 12/18] HID-debug: Replace 12 seq_printf() calls by seq_puts()

From: Markus Elfring Date: Tue, 7 Feb 2017 20:02:45 +0100 Strings which did not contain data format specifications should be put into a sequence. Thus use the corresponding function "seq_puts". This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

[PATCH 1/3] kprobes: introduce weak variant of kprobe_exceptions_notify

kprobe_exceptions_notify() is not used on some of the architectures such as arm[64] and powerpc anymore. Introduce a weak variant for such architectures. Signed-off-by: Naveen N. Rao --- kernel/kprobes.c | 6 ++ 1 file changed, 6 insertions(+) diff --git

[PATCH 3/3] powerpc: kprobes: remove kprobe_exceptions_notify()

... as the weak variant will do. Signed-off-by: Naveen N. Rao --- arch/powerpc/kernel/kprobes.c | 9 - 1 file changed, 9 deletions(-) diff --git a/arch/powerpc/kernel/kprobes.c b/arch/powerpc/kernel/kprobes.c index 45e4f82b230d..fce05a38851c 100644 ---

[PATCH 1/3] kprobes: introduce weak variant of kprobe_exceptions_notify

kprobe_exceptions_notify() is not used on some of the architectures such as arm[64] and powerpc anymore. Introduce a weak variant for such architectures. Signed-off-by: Naveen N. Rao --- kernel/kprobes.c | 6 ++ 1 file changed, 6 insertions(+) diff --git a/kernel/kprobes.c

[PATCH 3/3] powerpc: kprobes: remove kprobe_exceptions_notify()

... as the weak variant will do. Signed-off-by: Naveen N. Rao --- arch/powerpc/kernel/kprobes.c | 9 - 1 file changed, 9 deletions(-) diff --git a/arch/powerpc/kernel/kprobes.c b/arch/powerpc/kernel/kprobes.c index 45e4f82b230d..fce05a38851c 100644 --- a/arch/powerpc/kernel/kprobes.c

[PATCH 2/3] arm: kprobes: remove kprobe_exceptions_notify

... as the weak variant will do. Signed-off-by: Naveen N. Rao --- arch/arm/probes/kprobes/core.c | 10 -- arch/arm64/kernel/probes/kprobes.c | 6 -- 2 files changed, 16 deletions(-) diff --git a/arch/arm/probes/kprobes/core.c

[PATCH 2/3] arm: kprobes: remove kprobe_exceptions_notify

... as the weak variant will do. Signed-off-by: Naveen N. Rao --- arch/arm/probes/kprobes/core.c | 10 -- arch/arm64/kernel/probes/kprobes.c | 6 -- 2 files changed, 16 deletions(-) diff --git a/arch/arm/probes/kprobes/core.c b/arch/arm/probes/kprobes/core.c index

Re: [PATCH v3 0/3] locking/spinlock_debug: Change it to a mostly fair lock

On Tue, Feb 07, 2017 at 02:46:31PM -0500, Waiman Long wrote: > On 02/07/2017 04:48 AM, Ingo Molnar wrote: > > * Peter Zijlstra wrote: > > > >> On Thu, Feb 02, 2017 at 09:15:26AM -0500, Waiman Long wrote: > >>> v2->v3: > >>> - Keep the original v1 patches but move patch 3

Re: [PATCH v3 0/3] locking/spinlock_debug: Change it to a mostly fair lock

On Tue, Feb 07, 2017 at 02:46:31PM -0500, Waiman Long wrote: > On 02/07/2017 04:48 AM, Ingo Molnar wrote: > > * Peter Zijlstra wrote: > > > >> On Thu, Feb 02, 2017 at 09:15:26AM -0500, Waiman Long wrote: > >>> v2->v3: > >>> - Keep the original v1 patches but move patch 3 of v2 in front so >

[PATCH 10/18] HID-debug: Replace five seq_printf() calls by seq_putc()

From: Markus Elfring Date: Tue, 7 Feb 2017 19:21:17 +0100 Single characters should be put into a sequence. Thus use the corresponding function "seq_putc". This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring

[PATCH 10/18] HID-debug: Replace five seq_printf() calls by seq_putc()

From: Markus Elfring Date: Tue, 7 Feb 2017 19:21:17 +0100 Single characters should be put into a sequence. Thus use the corresponding function "seq_putc". This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring --- drivers/hid/hid-debug.c | 12 +++- 1

[PATCH 09/18] HID: Return an error code only as a constant in hid_allocate_device()

From: Markus Elfring Date: Tue, 7 Feb 2017 19:17:36 +0100 * Return an error code without storing it in an intermediate variable. * Delete the local variable "ret" which became unnecessary with this refactoring. Signed-off-by: Markus Elfring

[PATCH 09/18] HID: Return an error code only as a constant in hid_allocate_device()

From: Markus Elfring Date: Tue, 7 Feb 2017 19:17:36 +0100 * Return an error code without storing it in an intermediate variable. * Delete the local variable "ret" which became unnecessary with this refactoring. Signed-off-by: Markus Elfring --- drivers/hid/hid-core.c | 3 +-- 1 file

[GIT] Networking

1) Load correct firmware in rtl8192ce wireless driver, from Jurij Smakov. 2) Fix leak of tx_ring and tx_cq due to overwriting in mlx4 driver, from Martin KaFai Lau. 3) Need to reference count PHY driver module when it is attached, from Mao Wenan. 4) Don't do zero length vzalloc() in

[PATCH 08/18] HID: Adjust five checks for null pointers

From: Markus Elfring Date: Tue, 7 Feb 2017 19:15:21 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The script "checkpatch.pl" pointed information out like the following. Comparison to NULL could be written !… Thus

[GIT] Networking

1) Load correct firmware in rtl8192ce wireless driver, from Jurij Smakov. 2) Fix leak of tx_ring and tx_cq due to overwriting in mlx4 driver, from Martin KaFai Lau. 3) Need to reference count PHY driver module when it is attached, from Mao Wenan. 4) Don't do zero length vzalloc() in

[PATCH 08/18] HID: Adjust five checks for null pointers

From: Markus Elfring Date: Tue, 7 Feb 2017 19:15:21 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The script "checkpatch.pl" pointed information out like the following. Comparison to NULL could be written !… Thus fix affected source code

Re: [RFC 1/1] shiftfs: uid/gid shifting bind mount

On Tue, Feb 07, 2017 at 11:02:03AM -0800, James Bottomley wrote: > > Another option would be to require something like a project as used > > for project quotas as the root. This would also be conveniant as it > > could storge the used remapping tables. > > So this would be like the current

Re: [RFC 1/1] shiftfs: uid/gid shifting bind mount

On Tue, Feb 07, 2017 at 11:02:03AM -0800, James Bottomley wrote: > > Another option would be to require something like a project as used > > for project quotas as the root. This would also be conveniant as it > > could storge the used remapping tables. > > So this would be like the current

[PATCH 04/18] HID: Improve another size determination in open_collection()

From: Markus Elfring Date: Mon, 6 Feb 2017 19:19:22 +0100 Replace the specification of a data structure by pointer dereferences as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style

[PATCH 04/18] HID: Improve another size determination in open_collection()

From: Markus Elfring Date: Mon, 6 Feb 2017 19:19:22 +0100 Replace the specification of a data structure by pointer dereferences as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style convention. Signed-off-by:

[PATCH 07/18] HID: Improve another size determination in hid_register_report()

From: Markus Elfring Date: Tue, 7 Feb 2017 19:12:56 +0100 Replace the specification of a data structure by a pointer dereference as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style

[PATCH 07/18] HID: Improve another size determination in hid_register_report()

From: Markus Elfring Date: Tue, 7 Feb 2017 19:12:56 +0100 Replace the specification of a data structure by a pointer dereference as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style convention. Signed-off-by:

[PATCH 03/18] HID: Use kmalloc_array() in open_collection()

From: Markus Elfring Date: Mon, 6 Feb 2017 19:09:42 +0100 * A multiplication for the size determination of a memory allocation indicated that an array data structure should be processed. Thus use the corresponding function "kmalloc_array". * Replace the

[PATCH 03/18] HID: Use kmalloc_array() in open_collection()

From: Markus Elfring Date: Mon, 6 Feb 2017 19:09:42 +0100 * A multiplication for the size determination of a memory allocation indicated that an array data structure should be processed. Thus use the corresponding function "kmalloc_array". * Replace the specification of a data structure by

Re: [PATCH 1/4] perf tools: pass PYTHON config to feature detection

Em Wed, Feb 01, 2017 at 10:38:01PM -0800, David Carrillo-Cisneros escreveu: > Python's CC and link Makefile variables were not passed to feature > detection, causing feature detection to use system's Python rather than > PYTHON_CONFIG's one. This created a mismatch between the detected Python >

Re: [PATCH 1/4] perf tools: pass PYTHON config to feature detection

Em Wed, Feb 01, 2017 at 10:38:01PM -0800, David Carrillo-Cisneros escreveu: > Python's CC and link Makefile variables were not passed to feature > detection, causing feature detection to use system's Python rather than > PYTHON_CONFIG's one. This created a mismatch between the detected Python >

[PATCH 05/18] HID: Improve two size determinations in hid_open_report()

From: Markus Elfring Date: Mon, 6 Feb 2017 22:00:07 +0100 Replace the specification of data structures by pointer dereferences as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style

[PATCH 05/18] HID: Improve two size determinations in hid_open_report()

From: Markus Elfring Date: Mon, 6 Feb 2017 22:00:07 +0100 Replace the specification of data structures by pointer dereferences as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style convention. Signed-off-by:

Re: [PATCH] gdrom: Add missing error code

Looks fine, Reviewed-by: Christoph Hellwig

Re: [PATCH] gdrom: Add missing error code

Looks fine, Reviewed-by: Christoph Hellwig

Re: [RFC 1/1] shiftfs: uid/gid shifting bind mount

On Tue, Feb 07, 2017 at 11:01:08AM -0800, James Bottomley wrote: > I was talking about inode stability in the filesystem underlying the > export. I believe you're talking about inode number stability > guarantees of the nfs client code itself, which are unrelated to the > inode number guarantees

[PATCH 06/18] HID: Improve another size determination in hid_scan_report()

From: Markus Elfring Date: Tue, 7 Feb 2017 19:10:53 +0100 Replace the specification of a data structure by a pointer dereference as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style

Re: [PATCH v3 0/3] locking/spinlock_debug: Change it to a mostly fair lock

On 02/07/2017 04:48 AM, Ingo Molnar wrote: > * Peter Zijlstra wrote: > >> On Thu, Feb 02, 2017 at 09:15:26AM -0500, Waiman Long wrote: >>> v2->v3: >>> - Keep the original v1 patches but move patch 3 of v2 in front so >>> as to disable GENERIC_LOCKBREAK when

Re: [RFC 1/1] shiftfs: uid/gid shifting bind mount

On Tue, Feb 07, 2017 at 11:01:08AM -0800, James Bottomley wrote: > I was talking about inode stability in the filesystem underlying the > export. I believe you're talking about inode number stability > guarantees of the nfs client code itself, which are unrelated to the > inode number guarantees

[PATCH 06/18] HID: Improve another size determination in hid_scan_report()

From: Markus Elfring Date: Tue, 7 Feb 2017 19:10:53 +0100 Replace the specification of a data structure by a pointer dereference as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style convention. Signed-off-by:

Re: [PATCH v3 0/3] locking/spinlock_debug: Change it to a mostly fair lock

On 02/07/2017 04:48 AM, Ingo Molnar wrote: > * Peter Zijlstra wrote: > >> On Thu, Feb 02, 2017 at 09:15:26AM -0500, Waiman Long wrote: >>> v2->v3: >>> - Keep the original v1 patches but move patch 3 of v2 in front so >>> as to disable GENERIC_LOCKBREAK when DEBUG_LOCK_ALLOC is on. >>> >>>

Re: [RFC 1/1] shiftfs: uid/gid shifting bind mount

On Tue, Feb 7, 2017 at 7:20 PM, James Bottomley wrote: > On Tue, 2017-02-07 at 19:59 +0200, Amir Goldstein wrote: >> On Tue, Feb 7, 2017 at 6:37 PM, James Bottomley >> wrote: >> > On Tue, 2017-02-07 at 01:19 -0800,

Re: [RFC 1/1] shiftfs: uid/gid shifting bind mount

On Tue, Feb 7, 2017 at 7:20 PM, James Bottomley wrote: > On Tue, 2017-02-07 at 19:59 +0200, Amir Goldstein wrote: >> On Tue, Feb 7, 2017 at 6:37 PM, James Bottomley >> wrote: >> > On Tue, 2017-02-07 at 01:19 -0800, Christoph Hellwig wrote: >> > > On Sat, Feb 04, 2017 at 11:19:32AM -0800, James

[PATCH 01/18] HID: Use kmalloc_array() in hid_input_field()

From: Markus Elfring Date: Mon, 6 Feb 2017 18:18:41 +0100 A multiplication for the size determination of a memory allocation indicated that an array data structure should be processed. Thus use the corresponding function "kmalloc_array". This issue was detected by

[PATCH 02/18] HID: Delete an error message for a failed memory allocation in open_collection()

From: Markus Elfring Date: Mon, 6 Feb 2017 18:42:26 +0100 The script "checkpatch.pl" pointed information out like the following. WARNING: Possible unnecessary 'out of memory' message Thus fix the affected source code place. Signed-off-by: Markus Elfring

[PATCH 01/18] HID: Use kmalloc_array() in hid_input_field()

From: Markus Elfring Date: Mon, 6 Feb 2017 18:18:41 +0100 A multiplication for the size determination of a memory allocation indicated that an array data structure should be processed. Thus use the corresponding function "kmalloc_array". This issue was detected by using the Coccinelle software.

[PATCH 02/18] HID: Delete an error message for a failed memory allocation in open_collection()

From: Markus Elfring Date: Mon, 6 Feb 2017 18:42:26 +0100 The script "checkpatch.pl" pointed information out like the following. WARNING: Possible unnecessary 'out of memory' message Thus fix the affected source code place. Signed-off-by: Markus Elfring --- drivers/hid/hid-core.c | 5 ++---

[PATCH] net: qcom/emac: fix semicolon.cocci warnings

drivers/net/ethernet/qualcomm/emac/emac-ethtool.c:155:49-50: Unneeded semicolon Remove unneeded semicolon. Generated by: scripts/coccinelle/misc/semicolon.cocci CC: Timur Tabi Signed-off-by: Fengguang Wu --- emac-ethtool.c |2 +- 1 file

[PATCH] net: qcom/emac: fix semicolon.cocci warnings

drivers/net/ethernet/qualcomm/emac/emac-ethtool.c:155:49-50: Unneeded semicolon Remove unneeded semicolon. Generated by: scripts/coccinelle/misc/semicolon.cocci CC: Timur Tabi Signed-off-by: Fengguang Wu --- emac-ethtool.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) ---

<    2   3   4   5   6   7   8   9   10   11   >