[PATCH 1/1] ASoC: Intel: Atom: add a missing star in a memcpy call

In sst_prepare_and_post_msg(), when a response is received in "block", the following code gets executed: *data = kzalloc(block->size, GFP_KERNEL); memcpy(data, (void *) block->data, block->size); The memcpy() call overwrites the content of the *data pointer instead of filling the

[PATCH 1/1] ASoC: Intel: Atom: add a missing star in a memcpy call

In sst_prepare_and_post_msg(), when a response is received in "block", the following code gets executed: *data = kzalloc(block->size, GFP_KERNEL); memcpy(data, (void *) block->data, block->size); The memcpy() call overwrites the content of the *data pointer instead of filling the

Re: constification and cocci / kernel build test robot ?

On Sun, 2016-08-28 at 15:13 +0200, Julia Lawall wrote: > [Adding Kees, in case it's of interest] > Below is the list of types of top-level initialized structures and the > number that are const.  For quicker reading, here are some that are > sometimes const (numerator), but not always

Re: constification and cocci / kernel build test robot ?

On Sun, 2016-08-28 at 15:13 +0200, Julia Lawall wrote: > [Adding Kees, in case it's of interest] > Below is the list of types of top-level initialized structures and the > number that are const.  For quicker reading, here are some that are > sometimes const (numerator), but not always

[PATCH 3/6] KVM: PPC: e500: Delete an unnecessary initialisation in kvm_vcpu_ioctl_config_tlb()

From: Markus Elfring Date: Sun, 28 Aug 2016 17:37:10 +0200 The local variable "g2h_bitmap" will be set to an appropriate value a bit later. Thus omit the explicit initialisation at the beginning. Signed-off-by: Markus Elfring ---

[PATCH 3/6] KVM: PPC: e500: Delete an unnecessary initialisation in kvm_vcpu_ioctl_config_tlb()

From: Markus Elfring Date: Sun, 28 Aug 2016 17:37:10 +0200 The local variable "g2h_bitmap" will be set to an appropriate value a bit later. Thus omit the explicit initialisation at the beginning. Signed-off-by: Markus Elfring --- arch/powerpc/kvm/e500_mmu.c | 2 +- 1 file changed, 1

[PATCH 6/6] KVM: PPC: e500: Rename jump labels in kvmppc_e500_tlb_init()

From: Markus Elfring Date: Sun, 28 Aug 2016 18:45:26 +0200 Adjust jump labels according to the current Linux coding style convention. Signed-off-by: Markus Elfring --- arch/powerpc/kvm/e500_mmu.c | 9 - 1 file changed, 4

[PATCH 6/6] KVM: PPC: e500: Rename jump labels in kvmppc_e500_tlb_init()

From: Markus Elfring Date: Sun, 28 Aug 2016 18:45:26 +0200 Adjust jump labels according to the current Linux coding style convention. Signed-off-by: Markus Elfring --- arch/powerpc/kvm/e500_mmu.c | 9 - 1 file changed, 4 insertions(+), 5 deletions(-) diff --git

[PATCH 5/6] KVM: PPC: e500: Use kmalloc_array() in kvmppc_e500_tlb_init()

From: Markus Elfring Date: Sun, 28 Aug 2016 18:40:08 +0200 * 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 5/6] KVM: PPC: e500: Use kmalloc_array() in kvmppc_e500_tlb_init()

From: Markus Elfring Date: Sun, 28 Aug 2016 18:40:08 +0200 * 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

[PATCH 4/6] KVM: PPC: e500: Replace kzalloc() calls by kcalloc() in two functions

From: Markus Elfring Date: Sun, 28 Aug 2016 18:30:38 +0200 * A multiplication for the size determination of a memory allocation indicated that an array data structure should be processed. Thus use the corresponding function "kcalloc". Suggested-by: Paolo

[PATCH 4/6] KVM: PPC: e500: Replace kzalloc() calls by kcalloc() in two functions

From: Markus Elfring Date: Sun, 28 Aug 2016 18:30:38 +0200 * A multiplication for the size determination of a memory allocation indicated that an array data structure should be processed. Thus use the corresponding function "kcalloc". Suggested-by: Paolo Bonzini This issue was

Re: checkkpatch (in)sanity ?

On Sat, 2016-08-27 at 22:47 -0400, Levin, Alexander wrote: > Would you agree that by default we shouldn't show anything that's > not an error/defect? Not particularly, no. > That doesn't deal with newlines people add to hide the 80 character stuff, > nor it > deals with the "harder to read"

Re: checkkpatch (in)sanity ?

On Sat, 2016-08-27 at 22:47 -0400, Levin, Alexander wrote: > Would you agree that by default we shouldn't show anything that's > not an error/defect? Not particularly, no. > That doesn't deal with newlines people add to hide the 80 character stuff, > nor it > deals with the "harder to read"

[PATCH 2/6] KVM: PPC: e500: Less function calls in kvm_vcpu_ioctl_config_tlb() after error detection

From: Markus Elfring Date: Sun, 28 Aug 2016 17:34:46 +0200 The kfree() function was called in two cases by the kvm_vcpu_ioctl_config_tlb() function during error handling even if the passed data structure element contained a null pointer. * Split a condition check

[PATCH 2/6] KVM: PPC: e500: Less function calls in kvm_vcpu_ioctl_config_tlb() after error detection

From: Markus Elfring Date: Sun, 28 Aug 2016 17:34:46 +0200 The kfree() function was called in two cases by the kvm_vcpu_ioctl_config_tlb() function during error handling even if the passed data structure element contained a null pointer. * Split a condition check for memory allocation failures.

[PATCH 1/6] KVM: PPC: e500: Use kmalloc_array() in kvm_vcpu_ioctl_config_tlb()

From: Markus Elfring Date: Sun, 28 Aug 2016 16:30:07 +0200 * 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

[PATCH 1/6] KVM: PPC: e500: Use kmalloc_array() in kvm_vcpu_ioctl_config_tlb()

From: Markus Elfring Date: Sun, 28 Aug 2016 16:30:07 +0200 * 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

[PATCH 0/6] KVM: PPC: e500: Fine-tuning for two function implementations

From: Markus Elfring Date: Sun, 28 Aug 2016 19:01:02 +0200 Several update suggestions were taken into account from static source code analysis. Markus Elfring (6): Use kmalloc_array() in kvm_vcpu_ioctl_config_tlb() Less function calls in

[PATCH 0/6] KVM: PPC: e500: Fine-tuning for two function implementations

From: Markus Elfring Date: Sun, 28 Aug 2016 19:01:02 +0200 Several update suggestions were taken into account from static source code analysis. Markus Elfring (6): Use kmalloc_array() in kvm_vcpu_ioctl_config_tlb() Less function calls in kvm_vcpu_ioctl_config_tlb() after error detection

Re: [PATCH] toshiba_acpi: Fix the kbd_backlight_mode_show printed value

On Tue, Aug 16, 2016 at 12:07:55PM -0600, Azael Avalos wrote: > The mentioned function prints the value in decimal, but the > documentation and its parent function available_kbd_modes_show > are showing the value as hexadecimal. > > This patch simply changes the value printed from decimal to hex,

Re: [PATCH] toshiba_acpi: Fix the kbd_backlight_mode_show printed value

On Tue, Aug 16, 2016 at 12:07:55PM -0600, Azael Avalos wrote: > The mentioned function prints the value in decimal, but the > documentation and its parent function available_kbd_modes_show > are showing the value as hexadecimal. > > This patch simply changes the value printed from decimal to hex,

Re: [PATCH 3/3] toshiba_acpi: Fix typo in *_cooling_method_set function

On Tue, Aug 16, 2016 at 12:06:17PM -0600, Azael Avalos wrote: > This patch simply fixes a typo in the error string printed in such > function. > > Signed-off-by: Azael Avalos Thanks, queued to for-next. -- Darren Hart Intel Open Source Technology Center

Re: [PATCH 3/3] toshiba_acpi: Fix typo in *_cooling_method_set function

On Tue, Aug 16, 2016 at 12:06:17PM -0600, Azael Avalos wrote: > This patch simply fixes a typo in the error string printed in such > function. > > Signed-off-by: Azael Avalos Thanks, queued to for-next. -- Darren Hart Intel Open Source Technology Center

Re: Linux 4.8: Reported regressions as of Sunday, 2016-08-28

On Sun, Aug 28, 2016 at 8:23 AM, Thorsten Leemhuis wrote: > > Desc: irqdomain: Don't set type when mapping an IRQ breaks nexus7 gpio buttons > Repo: 2016-07-30 https://marc.info/?l=linux-kernel=146985356305280=2 > Stat: 2016-08-12

Re: Linux 4.8: Reported regressions as of Sunday, 2016-08-28

On Sun, Aug 28, 2016 at 8:23 AM, Thorsten Leemhuis wrote: > > Desc: irqdomain: Don't set type when mapping an IRQ breaks nexus7 gpio buttons > Repo: 2016-07-30 https://marc.info/?l=linux-kernel=146985356305280=2 > Stat: 2016-08-12 https://marc.info/?l=linux-kernel=147093069326172=2 > Note: fix

Re: [PATCH] toshiba-wmi: Fix loading the driver on non Toshiba laptops

On Thu, Aug 25, 2016 at 12:50:55PM -0600, Azael Avalos wrote: > Bug 150611 uncovered that the WMI ID used by the toshiba-wmi driver > is not Toshiba specific, and as such, the driver was being loaded > on non Toshiba laptops too. > > This patch adds a DMI matching list checking for TOSHIBA as the

Re: [PATCH] toshiba-wmi: Fix loading the driver on non Toshiba laptops

On Thu, Aug 25, 2016 at 12:50:55PM -0600, Azael Avalos wrote: > Bug 150611 uncovered that the WMI ID used by the toshiba-wmi driver > is not Toshiba specific, and as such, the driver was being loaded > on non Toshiba laptops too. > > This patch adds a DMI matching list checking for TOSHIBA as the

[PATCH 1/1] ARM: add printf format attribute to early_print()

Adding such an attribute is helpful to detect errors related to printf formats at compile-time. Signed-off-by: Nicolas Iooss --- arch/arm/include/asm/setup.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/include/asm/setup.h

[PATCH 1/1] ARM: add printf format attribute to early_print()

Adding such an attribute is helpful to detect errors related to printf formats at compile-time. Signed-off-by: Nicolas Iooss --- arch/arm/include/asm/setup.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/arm/include/asm/setup.h b/arch/arm/include/asm/setup.h index

Re: [PATCH 2/3] toshiba_acpi: Change error checking logic from TCI functions

On Tue, Aug 16, 2016 at 12:06:16PM -0600, Azael Avalos wrote: > Currently the success/error checking logic is intermixed, making the > code a bit cumbersome to understand. > > This patch changes the affected functions to first check for errors > and take appropriate actions, then check for the

undefined reference to `printk'

Hi Peter, It's probably a bug fix that unveils the link errors. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: af56ff27eba54fceee5f5643e79bf6531f2e1739 commit: 63a3f603413ffe82ad775f2d62a5afff87fd94a0 timeconst.pl: Eliminate Perl warning date: 3

Re: [PATCH 2/3] toshiba_acpi: Change error checking logic from TCI functions

On Tue, Aug 16, 2016 at 12:06:16PM -0600, Azael Avalos wrote: > Currently the success/error checking logic is intermixed, making the > code a bit cumbersome to understand. > > This patch changes the affected functions to first check for errors > and take appropriate actions, then check for the

undefined reference to `printk'

Hi Peter, It's probably a bug fix that unveils the link errors. tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: af56ff27eba54fceee5f5643e79bf6531f2e1739 commit: 63a3f603413ffe82ad775f2d62a5afff87fd94a0 timeconst.pl: Eliminate Perl warning date: 3

Re: [PATCH] qla2xxx: fix spelling mistake "retyring" -> "retrying"

On 8/28/16, 4:24 AM, "Colin King" wrote: >From: Colin Ian King > >Trivial fix to spelling mistakes in ql_dbg messages. > >Signed-off-by: Colin Ian King >--- > drivers/scsi/qla2xxx/qla_os.c | 6 +++--- > 1 file

Re: [PATCH] qla2xxx: fix spelling mistake "retyring" -> "retrying"

On 8/28/16, 4:24 AM, "Colin King" wrote: >From: Colin Ian King > >Trivial fix to spelling mistakes in ql_dbg messages. > >Signed-off-by: Colin Ian King >--- > drivers/scsi/qla2xxx/qla_os.c | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) > >diff --git

Re: [PATCH 1/3] toshiba_acpi: Cleanup variable declaration

On Tue, Aug 16, 2016 at 12:06:15PM -0600, Azael Avalos wrote: > This patch moves all the multiple line variable declaration to a > single line declaration (except variables being initialized) > following the reverse tree order, to conform to the practices > of the kernel. Azael, Apologies for

Re: [PATCH 1/3] toshiba_acpi: Cleanup variable declaration

On Tue, Aug 16, 2016 at 12:06:15PM -0600, Azael Avalos wrote: > This patch moves all the multiple line variable declaration to a > single line declaration (except variables being initialized) > following the reverse tree order, to conform to the practices > of the kernel. Azael, Apologies for

[PATCH 1/1] ceph: do not modify fi->frag in need_reset_readdir()

Commit f3c4ebe65ea1 ("ceph: using hash value to compose dentry offset") modified "if (fpos_frag(new_pos) != fi->frag)" to "if (fi->frag |= fpos_frag(new_pos))" in need_reset_readdir(), thus replacing a comparison operator with an assignment one. This looks like a typo which is reported by clang

[PATCH 1/1] ceph: do not modify fi->frag in need_reset_readdir()

Commit f3c4ebe65ea1 ("ceph: using hash value to compose dentry offset") modified "if (fpos_frag(new_pos) != fi->frag)" to "if (fi->frag |= fpos_frag(new_pos))" in need_reset_readdir(), thus replacing a comparison operator with an assignment one. This looks like a typo which is reported by clang

Re: [PATCH][v8] PM / hibernate: Verify the consistent of e820 memory map by md5 value

On Mon 2016-08-29 00:35:40, Chen Yu wrote: > On some platforms, there is occasional panic triggered when trying to > resume from hibernation, a typical panic looks like: > > "BUG: unable to handle kernel paging request at 880085894000 > IP: [] load_image_lzo+0x8c2/0xe70" > > This is because

Re: [PATCH][v8] PM / hibernate: Verify the consistent of e820 memory map by md5 value

On Mon 2016-08-29 00:35:40, Chen Yu wrote: > On some platforms, there is occasional panic triggered when trying to > resume from hibernation, a typical panic looks like: > > "BUG: unable to handle kernel paging request at 880085894000 > IP: [] load_image_lzo+0x8c2/0xe70" > > This is because

Re: [PATCH v3 1/4] pwm: Add support for Meson PWM Controller

om/xdarklight/linux/tree/meson-gxbb-integration-4.8-20160828

Re: [PATCH v3 1/4] pwm: Add support for Meson PWM Controller

5-meta clone, which uses pwm_e to generate the LPO clock for the wifi module (see [0] for the corresponding patches). So thank you Neil, and: Tested-by: Martin Blumenstingl [0] https://github.com/xdarklight/linux/tree/meson-gxbb-integration-4.8-20160828

[PATCH][RFC v5] timekeeping: Ignore the bogus sleep time if pm_trace is enabled

Previously we encountered some memory overflow issues due to the bogus sleep time brought by inconsistent rtc, which is triggered when pm_trace is enabled, and we have fixed it in recent kernel. However it's improper in the first place to call __timekeeping_inject_sleeptime() in case that pm_trace

[PATCH][RFC v5] timekeeping: Ignore the bogus sleep time if pm_trace is enabled

Previously we encountered some memory overflow issues due to the bogus sleep time brought by inconsistent rtc, which is triggered when pm_trace is enabled, and we have fixed it in recent kernel. However it's improper in the first place to call __timekeeping_inject_sleeptime() in case that pm_trace

[PATCH 2/4] barrier.h: Move smp_mb__after_unlock_lock to barrier.h

spin_unlock() + spin_lock() together do not form a full memory barrier: (everything initialized to 0) CPU1: a=1; spin_unlock(); spin_lock(); + smp_mb__after_unlock_lock(); r1=d; CPU2: d=1; smp_mb(); r2=a; Without the smp_mb__after_unlock_lock(), r1==0 && r2==0 would be possible.

[PATCH 2/4] barrier.h: Move smp_mb__after_unlock_lock to barrier.h

spin_unlock() + spin_lock() together do not form a full memory barrier: (everything initialized to 0) CPU1: a=1; spin_unlock(); spin_lock(); + smp_mb__after_unlock_lock(); r1=d; CPU2: d=1; smp_mb(); r2=a; Without the smp_mb__after_unlock_lock(), r1==0 && r2==0 would be possible.

Re: [PATCH v3 3/4] ARM64: dts: meson-gxbb: Add Meson GXBB PWM Controller nodes

I have successfully tested pwm_e on my meson-gxbb-vega-s95-meta clone (see [0] for the corresponding patches), thus: Tested-by: Martin Blumenstingl <martin.blumensti...@googlemail.com> [0] https://github.com/xdarklight/linux/tree/meson-gxbb-integration-4.8-20160828

Re: [PATCH v3 3/4] ARM64: dts: meson-gxbb: Add Meson GXBB PWM Controller nodes

uot;; > + reg = <0x0 0x086c0 0x0 0x10>; > + #pwm-cells = <3>; > + status = "disabled"; > + }; I have successfully tested pwm_e on my meson-gxbb-vega-s95-meta clone (see [0] for the corresponding patches), thus: Tested-by: Martin Blumenstingl [0] https://github.com/xdarklight/linux/tree/meson-gxbb-integration-4.8-20160828

[PATCH][v8] PM / hibernate: Verify the consistent of e820 memory map by md5 value

On some platforms, there is occasional panic triggered when trying to resume from hibernation, a typical panic looks like: "BUG: unable to handle kernel paging request at 880085894000 IP: [] load_image_lzo+0x8c2/0xe70" This is because e820 map has been changed by BIOS across hibernation, and

[PATCH][v8] PM / hibernate: Verify the consistent of e820 memory map by md5 value

On some platforms, there is occasional panic triggered when trying to resume from hibernation, a typical panic looks like: "BUG: unable to handle kernel paging request at 880085894000 IP: [] load_image_lzo+0x8c2/0xe70" This is because e820 map has been changed by BIOS across hibernation, and

[PATCH -next] staging: fsl-mc: convert to use ATTRIBUTE_GROUPS macro

From: Wei Yongjun Use ATTRIBUTE_GROUPS macro to reduce the number of lines of code. Generated by Coccinelle semantic patch. Signed-off-by: Wei Yongjun --- drivers/staging/fsl-mc/bus/mc-bus.c | 8 +--- 1 file changed, 1 insertion(+), 7

[PATCH -next] staging: fsl-mc: convert to use ATTRIBUTE_GROUPS macro

From: Wei Yongjun Use ATTRIBUTE_GROUPS macro to reduce the number of lines of code. Generated by Coccinelle semantic patch. Signed-off-by: Wei Yongjun --- drivers/staging/fsl-mc/bus/mc-bus.c | 8 +--- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git

Re: [PATCH v06] uapi dm-log-userspace.h: use __u32, __s32, __u64 and __s64 from linux/types.h

On 08/27/16 23:43, Mikko Rapeli wrote: > Fixes userspace compilation errors like: > > linux/dm-log-userspace.h:416:2: error: unknown type name ‘uint64_t’ Reviewed-by: Bart Van Assche

Re: [PATCH v06] uapi dm-log-userspace.h: use __u32, __s32, __u64 and __s64 from linux/types.h

On 08/27/16 23:43, Mikko Rapeli wrote: > Fixes userspace compilation errors like: > > linux/dm-log-userspace.h:416:2: error: unknown type name ‘uint64_t’ Reviewed-by: Bart Van Assche

Re: [PATCH v2] i2c: move locking operations to their own struct

On Thu, Aug 25, 2016 at 11:07:01PM +0200, Peter Rosin wrote: > This makes it trivial to constify them, so do that. > > Signed-off-by: Peter Rosin Acked-by: Daniel Vetter Feel free to merge through i2c tree. -Daniel > --- >

Re: [PATCH v2] i2c: move locking operations to their own struct

On Thu, Aug 25, 2016 at 11:07:01PM +0200, Peter Rosin wrote: > This makes it trivial to constify them, so do that. > > Signed-off-by: Peter Rosin Acked-by: Daniel Vetter Feel free to merge through i2c tree. -Daniel > --- > drivers/gpu/drm/drm_dp_helper.c | 10 +++--- >

Linux 4.8: Reported regressions as of Sunday, 2016-08-28

Hi! Here is my second regression report for Linux 4.8. It lists 11 regressions. 5 of them are new; 5 mentioned in the last report two weeks ago got fixed. FWIW: A small detail: I did not include "Regression - SATA disks behind USB ones on v4.8-rc1, breaking boot. [Re: Who reordered my disks]"

Linux 4.8: Reported regressions as of Sunday, 2016-08-28

Hi! Here is my second regression report for Linux 4.8. It lists 11 regressions. 5 of them are new; 5 mentioned in the last report two weeks ago got fixed. FWIW: A small detail: I did not include "Regression - SATA disks behind USB ones on v4.8-rc1, breaking boot. [Re: Who reordered my disks]"

Re: [RFC PATCH] clk: rockchip: rk3399: support pll setting automatically

Hi Xing, Elaine, Am Dienstag, 2. August 2016, 21:34:12 schrieb Xing Zheng: > From: Elaine Zhang > > The goal is that we can configure the most suitable pll params > automatically. > > If setting freq is not supported in rockchip_pll_rate_table > rk3399_pll_rates[], we

Re: [RFC PATCH] clk: rockchip: rk3399: support pll setting automatically

Hi Xing, Elaine, Am Dienstag, 2. August 2016, 21:34:12 schrieb Xing Zheng: > From: Elaine Zhang > > The goal is that we can configure the most suitable pll params > automatically. > > If setting freq is not supported in rockchip_pll_rate_table > rk3399_pll_rates[], we can set pll params

Re: [PATCH 3/6] rtl8188eu: declare internal function as static

Dear Andy, thanks for your review. On 28/08/2016 14:28, Andy Shevchenko wrote: > On Sat, 2016-08-27 at 14:40 +0200, Luca Ceresoli wrote: > > Put here few words _why_ you are doing this. I'm doing it because this function is only used inside rtw_recv.c. Which is quite logical, since it's a

Re: [PATCH 3/6] rtl8188eu: declare internal function as static

Dear Andy, thanks for your review. On 28/08/2016 14:28, Andy Shevchenko wrote: > On Sat, 2016-08-27 at 14:40 +0200, Luca Ceresoli wrote: > > Put here few words _why_ you are doing this. I'm doing it because this function is only used inside rtw_recv.c. Which is quite logical, since it's a

[PATCH v2] arch: all: include: asm: bitops: Use bool instead of int for all bit test functions

From: Chen Gang Also use the same changing to asm-generic, and also use bool variable instead of int variable for mips, mn10300, parisc and tile related functions, and also avoid checkpatch.pl to report ERROR. Include linux/types.h for alpha, arm, arm64, m68k, and

[PATCH v2] arch: all: include: asm: bitops: Use bool instead of int for all bit test functions

From: Chen Gang Also use the same changing to asm-generic, and also use bool variable instead of int variable for mips, mn10300, parisc and tile related functions, and also avoid checkpatch.pl to report ERROR. Include linux/types.h for alpha, arm, arm64, m68k, and openrisc to pass building.

[PATCH v3] IB/cxgb4: Mark symbols static for _free_qp

We get 1 warning when build kernel with W=1: drivers/infiniband/hw/cxgb4/qp.c:686:6: warning: no previous prototype for '_free_qp' [-Wmissing-prototypes] In fact, this function is only used in the file in which it is declared and don't need a declaration, but can be made static. so this patch

[PATCH v3] IB/cxgb4: Mark symbols static for _free_qp

We get 1 warning when build kernel with W=1: drivers/infiniband/hw/cxgb4/qp.c:686:6: warning: no previous prototype for '_free_qp' [-Wmissing-prototypes] In fact, this function is only used in the file in which it is declared and don't need a declaration, but can be made static. so this patch

[patch 1/2] i2c: add master driver for mellanox systems

From: Vadim Pasternak Device driver for Mellanox I2C controller logic, implemented in Lattice CPLD device. Device supports: - Master mode - One physical bus - Polling mode The Kconfig currently controlling compilation of this code is: drivers/i2c/busses/Kconfig:config

Re: [PATCH] arch: all: include: asm: bitops: Use bool instead of int for all bit test functions

s-Use-bool-instead-of-int-for-all-bit-test-functions/20160828-134633 > config: m68k-sun3_defconfig (attached as .config) > compiler: m68k-linux-gcc (GCC) 4.9.0 > reproduce: > wget > https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross > -O ~/bin/mak

[patch 2/2] i2c: mux: mellanox: add driver

From: Vadim Pasternak This driver allows I2C routing controlled through CPLD select registers on wide range of Mellanox systems (CPLD Lattice device). MUX selection is provided by digital and analog HW. Analog part is not under SW control. Digital part is under CPLD control

[patch 1/2] i2c: add master driver for mellanox systems

From: Vadim Pasternak Device driver for Mellanox I2C controller logic, implemented in Lattice CPLD device. Device supports: - Master mode - One physical bus - Polling mode The Kconfig currently controlling compilation of this code is: drivers/i2c/busses/Kconfig:config I2C_MLXCPLD

Re: [PATCH] arch: all: include: asm: bitops: Use bool instead of int for all bit test functions

s-Use-bool-instead-of-int-for-all-bit-test-functions/20160828-134633 > config: m68k-sun3_defconfig (attached as .config) > compiler: m68k-linux-gcc (GCC) 4.9.0 > reproduce: > wget > https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross > -O ~/bin/mak

[patch 2/2] i2c: mux: mellanox: add driver

From: Vadim Pasternak This driver allows I2C routing controlled through CPLD select registers on wide range of Mellanox systems (CPLD Lattice device). MUX selection is provided by digital and analog HW. Analog part is not under SW control. Digital part is under CPLD control (channel

Re: [PATCH 2/4] barrier.h: Move smp_mb__after_unlock_lock to barrier.h

tch --base= (or --base=auto for convenience) to record what (public, well-known) commit your patch series was built on] [Check https://git-scm.com/docs/git-format-patch for more information] url: https://github.com/0day-ci/linux/commits/Manfred-Spraul/spinlock-Document-memory-barrier-rules/20160

Re: [PATCH 2/4] barrier.h: Move smp_mb__after_unlock_lock to barrier.h

tch --base= (or --base=auto for convenience) to record what (public, well-known) commit your patch series was built on] [Check https://git-scm.com/docs/git-format-patch for more information] url: https://github.com/0day-ci/linux/commits/Manfred-Spraul/spinlock-Document-memory-barrier-rules/20160

[PATCH 3/3] userfaultfd: selftest: add test for FORK, MADVDONTNEED and REMAP events

Add test for userfaultfd events used in non-cooperative scenario when the process that monitors the userfaultfd and handles user faults is not the same process that causes the page faults. Signed-off-by: Mike Rapoport --- tools/testing/selftests/vm/userfaultfd.c | 174

[PATCH 3/3] userfaultfd: selftest: add test for FORK, MADVDONTNEED and REMAP events

Add test for userfaultfd events used in non-cooperative scenario when the process that monitors the userfaultfd and handles user faults is not the same process that causes the page faults. Signed-off-by: Mike Rapoport --- tools/testing/selftests/vm/userfaultfd.c | 174

[PATCH 1/3] userfaultfd: selftest: introduce userfaultfd_open

Signed-off-by: Mike Rapoport --- tools/testing/selftests/vm/userfaultfd.c | 41 +++- 1 file changed, 25 insertions(+), 16 deletions(-) diff --git a/tools/testing/selftests/vm/userfaultfd.c b/tools/testing/selftests/vm/userfaultfd.c index

[PATCH 0/3] userfaultfd: selftest: add event tests

Hi, These patches add tests for userfaultfd events used in non-cooperative scenario. The tests verify that fork(), mremap() and madvise(MADV_DONTNEED) can be properly handled when the process that monitors userfaultfd is not the process that causes the pagefaults. Mike Rapoport (3):

[PATCH 2/3] userfaultfd: selftest: add ufd parameter to copy_page

With future addition of event tests, copy_page will be called with different userfault file descriptors Signed-off-by: Mike Rapoport --- tools/testing/selftests/vm/userfaultfd.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git

[PATCH 1/3] userfaultfd: selftest: introduce userfaultfd_open

Signed-off-by: Mike Rapoport --- tools/testing/selftests/vm/userfaultfd.c | 41 +++- 1 file changed, 25 insertions(+), 16 deletions(-) diff --git a/tools/testing/selftests/vm/userfaultfd.c b/tools/testing/selftests/vm/userfaultfd.c index a5e5808..75540e7 100644 ---

[PATCH 0/3] userfaultfd: selftest: add event tests

Hi, These patches add tests for userfaultfd events used in non-cooperative scenario. The tests verify that fork(), mremap() and madvise(MADV_DONTNEED) can be properly handled when the process that monitors userfaultfd is not the process that causes the pagefaults. Mike Rapoport (3):

[PATCH 2/3] userfaultfd: selftest: add ufd parameter to copy_page

With future addition of event tests, copy_page will be called with different userfault file descriptors Signed-off-by: Mike Rapoport --- tools/testing/selftests/vm/userfaultfd.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git

dri: WARNING in idr_remove

Hello, The following program causes a WARNING in idr_remove: [ cut here ] WARNING: CPU: 3 PID: 26766 at lib/idr.c:505 idr_remove called for id=1 which is not allocated. CPU: 3 PID: 26766 Comm: syz-executor Not tainted 4.8.0-rc3+ #33 Hardware name: QEMU Standard PC (i440FX

dri: WARNING in idr_remove

Hello, The following program causes a WARNING in idr_remove: [ cut here ] WARNING: CPU: 3 PID: 26766 at lib/idr.c:505 idr_remove called for id=1 which is not allocated. CPU: 3 PID: 26766 Comm: syz-executor Not tainted 4.8.0-rc3+ #33 Hardware name: QEMU Standard PC (i440FX

Re: [PATCH V6 0/5] perf: Driver specific configuration for PMU

On Thu, Aug 25, 2016 at 02:20:40PM -0600, Mathieu Poirier wrote: SNIP > perf record -e some_event/@cfg1,@cfg2=config/ ... > > The above are all valid configuration and will see the strings 'cfg1' > and 'cfg2=config' sent to the PMU driver for parsing and interpretation > using the existing

Re: [PATCH V6 0/5] perf: Driver specific configuration for PMU

On Thu, Aug 25, 2016 at 02:20:40PM -0600, Mathieu Poirier wrote: SNIP > perf record -e some_event/@cfg1,@cfg2=config/ ... > > The above are all valid configuration and will see the strings 'cfg1' > and 'cfg2=config' sent to the PMU driver for parsing and interpretation > using the existing

Re: [PATCH V6 1/5] perf tools: making coresight PMU listable

On Thu, Aug 25, 2016 at 02:20:41PM -0600, Mathieu Poirier wrote: SNIP > ARM/CORGI MACHINE SUPPORT > M: Richard Purdie > diff --git a/tools/perf/Makefile.config b/tools/perf/Makefile.config > index 24803c58049a..72edf83d76b7 100644 > --- a/tools/perf/Makefile.config > +++

Re: [PATCH V6 5/5] perf tools: adding sink configuration for cs_etm PMU

On Thu, Aug 25, 2016 at 02:20:45PM -0600, Mathieu Poirier wrote: SNIP > return NULL; > } > + > +static FILE *cs_device__open_file(const char *name) > +{ > + struct stat st; > + char path[PATH_MAX]; > + const char *sysfs; > + > + sysfs = sysfs__mountpoint(); > + if

Re: [PATCH V6 5/5] perf tools: adding sink configuration for cs_etm PMU

On Thu, Aug 25, 2016 at 02:20:45PM -0600, Mathieu Poirier wrote: SNIP > return NULL; > } > + > +static FILE *cs_device__open_file(const char *name) > +{ > + struct stat st; > + char path[PATH_MAX]; > + const char *sysfs; > + > + sysfs = sysfs__mountpoint(); > + if

Re: [PATCH V6 1/5] perf tools: making coresight PMU listable

On Thu, Aug 25, 2016 at 02:20:41PM -0600, Mathieu Poirier wrote: SNIP > ARM/CORGI MACHINE SUPPORT > M: Richard Purdie > diff --git a/tools/perf/Makefile.config b/tools/perf/Makefile.config > index 24803c58049a..72edf83d76b7 100644 > --- a/tools/perf/Makefile.config > +++

[PATCH] f2fs crypto: avoid unneeded memory allocation in ->readdir

From: Chao Yu When decrypting dirents in ->readdir, fscrypt_fname_disk_to_usr won't change content of original encrypted dirent, we don't need to allocate additional buffer for storing mirror of it, so get rid of it. Signed-off-by: Chao Yu ---

[PATCH] f2fs crypto: avoid unneeded memory allocation in ->readdir

From: Chao Yu When decrypting dirents in ->readdir, fscrypt_fname_disk_to_usr won't change content of original encrypted dirent, we don't need to allocate additional buffer for storing mirror of it, so get rid of it. Signed-off-by: Chao Yu --- fs/f2fs/dir.c | 7 --- 1 file changed, 7

Re: [PATCH 2/4] barrier.h: Move smp_mb__after_unlock_lock to barrier.h

On Sun, Aug 28, 2016 at 01:56:14PM +0200, Manfred Spraul wrote: > spin_unlock() + spin_lock() together do not form a full memory barrier: > > a=1; > spin_unlock(); > spin_lock(); > + smp_mb__after_unlock_lock(); > d=1; Better would be s/d=1/r1=d/ above. Then another process doing this:

Re: [PATCH 2/4] barrier.h: Move smp_mb__after_unlock_lock to barrier.h

On Sun, Aug 28, 2016 at 01:56:14PM +0200, Manfred Spraul wrote: > spin_unlock() + spin_lock() together do not form a full memory barrier: > > a=1; > spin_unlock(); > spin_lock(); > + smp_mb__after_unlock_lock(); > d=1; Better would be s/d=1/r1=d/ above. Then another process doing this:

RE: [PATCH][v6] PM / hibernate: Print the possible panic reason when resuming with inconsistent e820 map

> -Original Message- > From: Pavel Machek [mailto:pa...@ucw.cz] > Sent: Sunday, August 28, 2016 9:15 PM > To: Chen, Yu C > Cc: joeyli; Rafael J. Wysocki; linux...@vger.kernel.org; linux- > ker...@vger.kernel.org > Subject: Re: [PATCH][v6] PM / hibernate: Print the possible panic reason

RE: [PATCH][v6] PM / hibernate: Print the possible panic reason when resuming with inconsistent e820 map

> -Original Message- > From: Pavel Machek [mailto:pa...@ucw.cz] > Sent: Sunday, August 28, 2016 9:15 PM > To: Chen, Yu C > Cc: joeyli; Rafael J. Wysocki; linux...@vger.kernel.org; linux- > ker...@vger.kernel.org > Subject: Re: [PATCH][v6] PM / hibernate: Print the possible panic reason

[PATCH] lib/rbtree.c: fix typo in comment of ____rb_erase_color

From: cee1 In Case 3 of `sibling == parent->rb_right': Right rotation will not change color of sl and S in the diagram (i.e. should not change "sl" to "Sl", "S" to "s") In Case 3 of `sibling == parent->rb_left': (p) (p) / \ / \ S N-->

[PATCH] lib/rbtree.c: fix typo in comment of ____rb_erase_color

From: cee1 In Case 3 of `sibling == parent->rb_right': Right rotation will not change color of sl and S in the diagram (i.e. should not change "sl" to "Sl", "S" to "s") In Case 3 of `sibling == parent->rb_left': (p) (p) / \ / \ S N--> sr N / \

<    1   2   3   4   5   6   >