[PATCH] f2fs-tools: move_curseg_info only if check_curseg_offset fails

Current design will lose recovery process when check_curseg_offset is OK. Signed-off-by: Yunlong Song --- fsck/fsck.c | 8 +--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/fsck/fsck.c b/fsck/fsck.c index cb341ba..56a47be 100644 --- a/fsck/fsck.c

[PATCH] f2fs-tools: move_curseg_info only if check_curseg_offset fails

Current design will lose recovery process when check_curseg_offset is OK. Signed-off-by: Yunlong Song --- fsck/fsck.c | 8 +--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/fsck/fsck.c b/fsck/fsck.c index cb341ba..56a47be 100644 --- a/fsck/fsck.c +++ b/fsck/fsck.c @@

Re: [PATCH v6] iio: accel: mma8452: improvements to handle multiple events

> I stripped the version change stuff from the commit message - they > should have been below the --- Useful during review, but generally > not worth retaining once we have accepted it. I didn't know that, thanks for letting me know. Next time I will keep that in mind. Thanks, Hari On Sun, Sep

Re: [PATCH v6] iio: accel: mma8452: improvements to handle multiple events

> I stripped the version change stuff from the commit message - they > should have been below the --- Useful during review, but generally > not worth retaining once we have accepted it. I didn't know that, thanks for letting me know. Next time I will keep that in mind. Thanks, Hari On Sun, Sep

Re: dtc: imx6 warnings on unit address format errors

On Sun, Sep 10, 2017 at 1:06 PM, Enrico Weigelt, metux IT consult wrote: > Hi folks, > > > I'm getting lots of warnings from dtc about unit address format errors: > > For example in imx6q.dtsi: > > ocram: sram@0090 { > > The node name's address part has leading zeros which

Re: dtc: imx6 warnings on unit address format errors

On Sun, Sep 10, 2017 at 1:06 PM, Enrico Weigelt, metux IT consult wrote: > Hi folks, > > > I'm getting lots of warnings from dtc about unit address format errors: > > For example in imx6q.dtsi: > > ocram: sram@0090 { > > The node name's address part has leading zeros which dtc doesn't

Re: iov_iter_pipe warning.

On Sun, Sep 10, 2017 at 03:57:21AM +0100, Al Viro wrote: > On Sat, Sep 09, 2017 at 09:07:56PM -0400, Dave Jones wrote: > > > With this in place, I'm still seeing -EBUSY from > > invalidate_inode_pages2_range > > which doesn't end well... > > Different issue, and I'm not sure why that

Re: iov_iter_pipe warning.

On Sun, Sep 10, 2017 at 03:57:21AM +0100, Al Viro wrote: > On Sat, Sep 09, 2017 at 09:07:56PM -0400, Dave Jones wrote: > > > With this in place, I'm still seeing -EBUSY from > > invalidate_inode_pages2_range > > which doesn't end well... > > Different issue, and I'm not sure why that

dtc: imx6 warnings on unit address format errors

Hi folks, I'm getting lots of warnings from dtc about unit address format errors: For example in imx6q.dtsi: ocram: sram@0090 { The node name's address part has leading zeros which dtc doesn't like. It doesn't seem to have a big influence (yet ?), but I'd guess this warning is there

dtc: imx6 warnings on unit address format errors

Hi folks, I'm getting lots of warnings from dtc about unit address format errors: For example in imx6q.dtsi: ocram: sram@0090 { The node name's address part has leading zeros which dtc doesn't like. It doesn't seem to have a big influence (yet ?), but I'd guess this warning is there

Re: [PATCH] iio: stm32: fix adc/trigger link error

On Wed, 6 Sep 2017 18:16:33 +0200 Fabrice Gasnier wrote: > On 09/06/2017 02:56 PM, Arnd Bergmann wrote: > > The ADC driver can trigger on either the timer or the lptim > > trigger, but it only uses a Kconfig 'select' statement > > to ensure that the first of the two is

Re: [PATCH] iio: stm32: fix adc/trigger link error

On Wed, 6 Sep 2017 18:16:33 +0200 Fabrice Gasnier wrote: > On 09/06/2017 02:56 PM, Arnd Bergmann wrote: > > The ADC driver can trigger on either the timer or the lptim > > trigger, but it only uses a Kconfig 'select' statement > > to ensure that the first of the two is present. When the lptim >

[PATCH] x86/mm/64: Fix an incorrect warning with CONFIG_DEBUG_VM=y, !PCID

I've been staring at the word PCID too long. Fixes: f13c8e8c58ba ("x86/mm: Reinitialize TLB state on hotplug and resume") Reported-by: Dan Carpenter Signed-off-by: Andy Lutomirski --- arch/x86/mm/tlb.c | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH] x86/mm/64: Fix an incorrect warning with CONFIG_DEBUG_VM=y, !PCID

I've been staring at the word PCID too long. Fixes: f13c8e8c58ba ("x86/mm: Reinitialize TLB state on hotplug and resume") Reported-by: Dan Carpenter Signed-off-by: Andy Lutomirski --- arch/x86/mm/tlb.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/x86/mm/tlb.c

Re: [PATCH v6] iio: accel: mma8452: improvements to handle multiple events

On Sun, 10 Sep 2017 08:36:43 +0200 Martin Kepplinger wrote: > On 2017-09-09 21:56, Harinath Nampally wrote: > > This driver supports multiple devices like mma8653, > > mma8652, mma8452, mma8453 and fxls8471. Almost all > > these devices have more than one event. >

Re: [PATCH v6] iio: accel: mma8452: improvements to handle multiple events

On Sun, 10 Sep 2017 08:36:43 +0200 Martin Kepplinger wrote: > On 2017-09-09 21:56, Harinath Nampally wrote: > > This driver supports multiple devices like mma8653, > > mma8652, mma8452, mma8453 and fxls8471. Almost all > > these devices have more than one event. > > > > Current

[PATCH v2 1/1] scripts/checkpatch.pl: avoid false warning missing break

void foo(int a) switch (a) { case 'h': fun1(); exit(1); default: } creates a warning Possible switch case/default not preceded by break or fallthrough comment exit( should be treated like return. Signed-off-by: Heinrich Schuchardt

[PATCH v2 1/1] scripts/checkpatch.pl: avoid false warning missing break

void foo(int a) switch (a) { case 'h': fun1(); exit(1); default: } creates a warning Possible switch case/default not preceded by break or fallthrough comment exit( should be treated like return. Signed-off-by: Heinrich Schuchardt --- v2:

Re: [PATCH 8/9] arm64: enable KEXEC_FILE config

-support/20170910-143930 base: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-next/core config: arm64-allmodconfig (attached as .config) compiler: aarch64-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705 reproduce: wget https://raw.githubusercontent.com/intel/lkp-tests

Re: [PATCH 8/9] arm64: enable KEXEC_FILE config

-support/20170910-143930 base: https://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-next/core config: arm64-allmodconfig (attached as .config) compiler: aarch64-linux-gnu-gcc (Debian 6.1.1-9) 6.1.1 20160705 reproduce: wget https://raw.githubusercontent.com/intel/lkp-tests

[PATCH 2/2] x86: Fix off-by-one error in loop termination.

An off-by-one error in loop terminantion conditions in create_setup_data_nodes will lead to memory leak when create_setup_data_node return error. Signed-off-by: Sean Fu --- arch/x86/kernel/ksysfs.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 2/2] x86: Fix off-by-one error in loop termination.

An off-by-one error in loop terminantion conditions in create_setup_data_nodes will lead to memory leak when create_setup_data_node return error. Signed-off-by: Sean Fu --- arch/x86/kernel/ksysfs.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/x86/kernel/ksysfs.c

Re: [PATCH] iio: adc: dln2-adc: initialize local struct before using it

On Sun, 10 Sep 2017 14:45:01 +0200 Martin Kepplinger wrote: > struct data is defined and declared locally. Initiliazation has to be done > manually, so let's add that. > > Signed-off-by: Martin Kepplinger > --- > > This is more of a question actually! Did

Re: [PATCH] iio: adc: dln2-adc: initialize local struct before using it

On Sun, 10 Sep 2017 14:45:01 +0200 Martin Kepplinger wrote: > struct data is defined and declared locally. Initiliazation has to be done > manually, so let's add that. > > Signed-off-by: Martin Kepplinger > --- > > This is more of a question actually! Did you have in mind that data is > not

Re: [PATCH v5] iio: accel: mma8452: improvements to handle multiple events

On Sun, 10 Sep 2017 16:00:35 +0200 Martin Kepplinger wrote: > Am 10. September 2017 15:44:24 MESZ schrieb Jonathan Cameron > : > >On Mon, 4 Sep 2017 23:06:37 -0400 > >harinath Nampally wrote: > > > >> > I agree with your

Re: [PATCH v5] iio: accel: mma8452: improvements to handle multiple events

On Sun, 10 Sep 2017 16:00:35 +0200 Martin Kepplinger wrote: > Am 10. September 2017 15:44:24 MESZ schrieb Jonathan Cameron > : > >On Mon, 4 Sep 2017 23:06:37 -0400 > >harinath Nampally wrote: > > > >> > I agree with your understanding. It's a rising threshold, just > >that the input >

Re: [PATCH 2/2] iio: ad7793: Fix the serial interface reset

On Tue, 5 Sep 2017 14:17:21 +0200 Lars-Peter Clausen wrote: > On 09/05/2017 02:16 PM, Dragos Bogdan wrote: > > The serial interface can be reset by writing 32 consecutive 1s to the > > device. > > 'ret' was initialized correctly but its value was overwritten when > >

Re: [PATCH 2/2] iio: ad7793: Fix the serial interface reset

On Tue, 5 Sep 2017 14:17:21 +0200 Lars-Peter Clausen wrote: > On 09/05/2017 02:16 PM, Dragos Bogdan wrote: > > The serial interface can be reset by writing 32 consecutive 1s to the > > device. > > 'ret' was initialized correctly but its value was overwritten when > >

Re: [PATCH 1/2] iio: ad_sigma_delta: Implement a dedicated reset function

On Tue, 5 Sep 2017 14:16:42 +0200 Lars-Peter Clausen wrote: > On 09/05/2017 02:14 PM, Dragos Bogdan wrote: > > Since most of the SD ADCs have the option of reseting the serial > > interface by sending a number of SCLKs with CS = 0 and DIN = 1, > > a dedicated function that can

Re: [PATCH 1/2] iio: ad_sigma_delta: Implement a dedicated reset function

On Tue, 5 Sep 2017 14:16:42 +0200 Lars-Peter Clausen wrote: > On 09/05/2017 02:14 PM, Dragos Bogdan wrote: > > Since most of the SD ADCs have the option of reseting the serial > > interface by sending a number of SCLKs with CS = 0 and DIN = 1, > > a dedicated function that can do this is

Re: [PATCH 1/2] staging: typec: tcpm: Validate source and sink caps

On Sat, Sep 09, 2017 at 09:54:42AM -0700, Guenter Roeck wrote: > On 09/08/2017 12:13 PM, Greg Kroah-Hartman wrote: > > On Fri, Sep 08, 2017 at 10:29:52AM -0700, Badhri Jagan Sridharan wrote: > > > On Fri, Sep 8, 2017 at 2:45 AM, Greg Kroah-Hartman > > > wrote: > > > >

Re: [PATCH 1/2] staging: typec: tcpm: Validate source and sink caps

On Sat, Sep 09, 2017 at 09:54:42AM -0700, Guenter Roeck wrote: > On 09/08/2017 12:13 PM, Greg Kroah-Hartman wrote: > > On Fri, Sep 08, 2017 at 10:29:52AM -0700, Badhri Jagan Sridharan wrote: > > > On Fri, Sep 8, 2017 at 2:45 AM, Greg Kroah-Hartman > > > wrote: > > > > On Thu, Sep 07, 2017 at

Re: [PATCH v6] staging: pi433: Fixes minor typo errors

On Fri, Sep 08, 2017 at 11:18:08PM +0530, Harsha Sharma wrote: > Hello, > I have tried to follow above given instructions but please correct me if I am > wrong somewhere. What "above given instructions"? And please fix your email client to not send html email, it is getting rejected by the

Re: [PATCH v6] staging: pi433: Fixes minor typo errors

On Fri, Sep 08, 2017 at 11:18:08PM +0530, Harsha Sharma wrote: > Hello, > I have tried to follow above given instructions but please correct me if I am > wrong somewhere. What "above given instructions"? And please fix your email client to not send html email, it is getting rejected by the

[PATCH 02/10] staging: rtl8723bs: Add spaces around '+', '|', '*'

Use one space around most binary operators Signed-off-by: Harsha Sharma --- drivers/staging/rtl8723bs/os_dep/os_intfs.c | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/drivers/staging/rtl8723bs/os_dep/os_intfs.c

[PATCH 02/10] staging: rtl8723bs: Add spaces around '+', '|', '*'

Use one space around most binary operators Signed-off-by: Harsha Sharma --- drivers/staging/rtl8723bs/os_dep/os_intfs.c | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/drivers/staging/rtl8723bs/os_dep/os_intfs.c b/drivers/staging/rtl8723bs/os_dep/os_intfs.c

Re: [PATCH v2 3/3] arm64: dts: realtek: Add watchdog node for RTD1295

On 09/04/2017 04:16 PM, Andreas Färber wrote: Add the watchdog node to the RTD1295 Device Tree. Acked-by: Rob Herring Signed-off-by: Andreas Färber Acked-by: Guenter Roeck --- Depends on the pending clock nodes patch. v1 ->

Re: [PATCH v2 3/3] arm64: dts: realtek: Add watchdog node for RTD1295

On 09/04/2017 04:16 PM, Andreas Färber wrote: Add the watchdog node to the RTD1295 Device Tree. Acked-by: Rob Herring Signed-off-by: Andreas Färber Acked-by: Guenter Roeck --- Depends on the pending clock nodes patch. v1 -> v2: Unchanged

Re: [PATCH v2 2/3] watchdog: Add Realtek RTD1295

On 09/04/2017 04:16 PM, Andreas Färber wrote: Add a watchdog driver for the Realtek RTD1295 SoC. Based on QNAP's arch/arm/mach-rtk119x/driver/rtk_watchdog.c code and mach-rtk119x/driver/dc2vo/fpga/include/iso_reg.h register defines. Signed-off-by: Andreas Färber

Re: [PATCH v2 2/3] watchdog: Add Realtek RTD1295

On 09/04/2017 04:16 PM, Andreas Färber wrote: Add a watchdog driver for the Realtek RTD1295 SoC. Based on QNAP's arch/arm/mach-rtk119x/driver/rtk_watchdog.c code and mach-rtk119x/driver/dc2vo/fpga/include/iso_reg.h register defines. Signed-off-by: Andreas Färber Reviewed-by: Guenter Roeck

Re: [PATCH v2 1/3] dt-bindings: watchdog: Add Realtek RTD1295

On 09/04/2017 04:16 PM, Andreas Färber wrote: Add a binding for the Realtek RTD1295 watchdog. Acked-by: Rob Herring Signed-off-by: Andreas Färber Reviewed-by: Guenter Roeck --- v1 -> v2: Unchanged

Re: [PATCH v2 1/3] dt-bindings: watchdog: Add Realtek RTD1295

On 09/04/2017 04:16 PM, Andreas Färber wrote: Add a binding for the Realtek RTD1295 watchdog. Acked-by: Rob Herring Signed-off-by: Andreas Färber Reviewed-by: Guenter Roeck --- v1 -> v2: Unchanged .../devicetree/bindings/watchdog/realtek,rtd119x.txt| 17 + 1

[PATCH 01/10] staging: rtl8723bs: Add spaces around '='

Use one space around (on each side of) '=' operator Signed-off-by: Harsha Sharma --- drivers/staging/rtl8723bs/os_dep/os_intfs.c | 20 ++-- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/drivers/staging/rtl8723bs/os_dep/os_intfs.c

[PATCH 01/10] staging: rtl8723bs: Add spaces around '='

Use one space around (on each side of) '=' operator Signed-off-by: Harsha Sharma --- drivers/staging/rtl8723bs/os_dep/os_intfs.c | 20 ++-- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/drivers/staging/rtl8723bs/os_dep/os_intfs.c

[PATCH 00/10] staging: rtl8723bs: Follow linux-kernel coding style

Linux kernel coding style uses one space around most binary and ternary operators and spaces are prohibited at the start of a line. Concatenated strings should have space between elements and space is required after ','. In conditional statements, do not use unnecessary braces where a single

[PATCH 00/10] staging: rtl8723bs: Follow linux-kernel coding style

Linux kernel coding style uses one space around most binary and ternary operators and spaces are prohibited at the start of a line. Concatenated strings should have space between elements and space is required after ','. In conditional statements, do not use unnecessary braces where a single

unable to open initial console (ENODEV) (WAS: problem w/ kernel init (rootfs vs initial console / init process))

On 10.09.2017 11:09, mtx wrote: it tries to open the initial console, before even attempt to mount the > root fs, which obviously is doomed to fail. (directly passing root=> via cmdline - no initrd etc) Solved it. For the record: the uart2 node was still disabled, so the kernel did allocate a

unable to open initial console (ENODEV) (WAS: problem w/ kernel init (rootfs vs initial console / init process))

On 10.09.2017 11:09, mtx wrote: it tries to open the initial console, before even attempt to mount the > root fs, which obviously is doomed to fail. (directly passing root=> via cmdline - no initrd etc) Solved it. For the record: the uart2 node was still disabled, so the kernel did allocate a

Re: [PATCH 5/5] lmp92001: mfd: doc: Add support LMP92001

On Thu, 31 Aug 2017 01:25:28 +0700 s.abhi...@gmail.com wrote: > From: Abhisit Sangjan > > TI LMP92001 Analog System Monitor and Controller > > 8-bit GPIOs. > 12 DACs with 12-bit resolution. > > The GPIOs and DACs are shared port function with Cy function pin to > take

Re: [PATCH 5/5] lmp92001: mfd: doc: Add support LMP92001

On Thu, 31 Aug 2017 01:25:28 +0700 s.abhi...@gmail.com wrote: > From: Abhisit Sangjan > > TI LMP92001 Analog System Monitor and Controller > > 8-bit GPIOs. > 12 DACs with 12-bit resolution. > > The GPIOs and DACs are shared port function with Cy function pin to > take control the pin suddenly

Re: [PATCH 3/5] lmp92001: mfd: iio: dac: Add support LMP92001

On Thu, 31 Aug 2017 01:17:15 +0700 s.abhi...@gmail.com wrote: > From: Abhisit Sangjan > > TI LMP92001 Analog System Monitor and Controller > > 8-bit GPIOs. > 12 DACs with 12-bit resolution. > > The GPIOs and DACs are shared port function with Cy function pin to > take

Re: [PATCH 3/5] lmp92001: mfd: iio: dac: Add support LMP92001

On Thu, 31 Aug 2017 01:17:15 +0700 s.abhi...@gmail.com wrote: > From: Abhisit Sangjan > > TI LMP92001 Analog System Monitor and Controller > > 8-bit GPIOs. > 12 DACs with 12-bit resolution. > > The GPIOs and DACs are shared port function with Cy function pin to > take control the pin suddenly

Re: [PATCH 3.16 000/233] 3.16.48-rc1 review

On 09/09/2017 02:47 PM, Ben Hutchings wrote: This is the start of the stable review cycle for the 3.16.48 release. There are 233 patches in this series, which will be posted as responses to this one. If anyone has any issues with these being applied, please let me know. Responses should be

Re: [PATCH 3.16 000/233] 3.16.48-rc1 review

On 09/09/2017 02:47 PM, Ben Hutchings wrote: This is the start of the stable review cycle for the 3.16.48 release. There are 233 patches in this series, which will be posted as responses to this one. If anyone has any issues with these being applied, please let me know. Responses should be

Re: [PATCH 3.2 000/106] 3.2.93-rc1 review

On 09/09/2017 02:47 PM, Ben Hutchings wrote: This is the start of the stable review cycle for the 3.2.93 release. There are 106 patches in this series, which will be posted as responses to this one. If anyone has any issues with these being applied, please let me know. Responses should be made

Re: [PATCH 3.2 000/106] 3.2.93-rc1 review

On 09/09/2017 02:47 PM, Ben Hutchings wrote: This is the start of the stable review cycle for the 3.2.93 release. There are 106 patches in this series, which will be posted as responses to this one. If anyone has any issues with these being applied, please let me know. Responses should be made

[lkp-robot] [x86/asm/64] 74cc41d3b6: BUG:unable_to_handle_kernel

FYI, we noticed the following commit: commit: 74cc41d3b6a99fa2caa4e4edc82efea4d13b8d55 ("x86/asm/64: Remove all remaining direct thread_struct::sp0 reads") https://git.kernel.org/cgit/linux/kernel/git/luto/linux.git x86/entry_consolidation in testcase: trinity with following parameters:

[lkp-robot] [x86/asm/64] 74cc41d3b6: BUG:unable_to_handle_kernel

FYI, we noticed the following commit: commit: 74cc41d3b6a99fa2caa4e4edc82efea4d13b8d55 ("x86/asm/64: Remove all remaining direct thread_struct::sp0 reads") https://git.kernel.org/cgit/linux/kernel/git/luto/linux.git x86/entry_consolidation in testcase: trinity with following parameters:

ERROR: "__cmpxchg_u64" [drivers/net/ethernet/intel/i40e/i40e.ko] undefined!

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 4dfc2788033d30dfccfd4268e06dd73ce2c654ed commit: 841c950d67c6facde32a8644ced20c04aebb7dd8 i40e/i40evf: use cmpxchg64 when updating private flags in ethtool date: 2 weeks ago config: parisc-allmodconfig

ERROR: "__cmpxchg_u64" [drivers/net/ethernet/intel/i40e/i40e.ko] undefined!

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: 4dfc2788033d30dfccfd4268e06dd73ce2c654ed commit: 841c950d67c6facde32a8644ced20c04aebb7dd8 i40e/i40evf: use cmpxchg64 when updating private flags in ethtool date: 2 weeks ago config: parisc-allmodconfig

[lkp-robot] [x86/mm] 72c0098d92: WARNING:at_arch/x86/mm/tlb.c:#initialize_tlbstate_and_flush

FYI, we noticed the following commit: commit: 72c0098d92cedb11c7e0151e84918840a4e96b31 ("x86/mm: Reinitialize TLB state on hotplug and resume") https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master in testcase: boot on test machine: qemu-system-x86_64 -enable-kvm -m 420M

[lkp-robot] [x86/mm] 72c0098d92: WARNING:at_arch/x86/mm/tlb.c:#initialize_tlbstate_and_flush

FYI, we noticed the following commit: commit: 72c0098d92cedb11c7e0151e84918840a4e96b31 ("x86/mm: Reinitialize TLB state on hotplug and resume") https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master in testcase: boot on test machine: qemu-system-x86_64 -enable-kvm -m 420M

[lkp-robot] [ACPI / CPPC] 266c175b9b: BUG:KASAN:null-ptr-deref

FYI, we noticed the following commit: commit: 266c175b9b3242f472f0ae5260a97cf62747a1d1 ("ACPI / CPPC: Make cppc acpi driver aware of pcc subspace ids") url: https://github.com/0day-ci/linux/commits/George-Cherian/mailbox-PCC-Move-the-MAX_PCC_SUBSPACES-definition-to-header-file/20170908-060133

[lkp-robot] [ACPI / CPPC] 266c175b9b: BUG:KASAN:null-ptr-deref

FYI, we noticed the following commit: commit: 266c175b9b3242f472f0ae5260a97cf62747a1d1 ("ACPI / CPPC: Make cppc acpi driver aware of pcc subspace ids") url: https://github.com/0day-ci/linux/commits/George-Cherian/mailbox-PCC-Move-the-MAX_PCC_SUBSPACES-definition-to-header-file/20170908-060133

Re: [PATCH 2/5] lmp92001: mfd: iio: adc: Add support LMP92001

On Thu, 31 Aug 2017 01:14:09 +0700 s.abhi...@gmail.com wrote: > From: Abhisit Sangjan > > TI LMP92001 Analog System Monitor and Controller > > 8-bit GPIOs. > 12 DACs with 12-bit resolution. > > The GPIOs and DACs are shared port function with Cy function pin to > take

Re: [PATCH 2/5] lmp92001: mfd: iio: adc: Add support LMP92001

On Thu, 31 Aug 2017 01:14:09 +0700 s.abhi...@gmail.com wrote: > From: Abhisit Sangjan > > TI LMP92001 Analog System Monitor and Controller > > 8-bit GPIOs. > 12 DACs with 12-bit resolution. > > The GPIOs and DACs are shared port function with Cy function pin to > take control the pin suddenly

Re: [PATCH 1/1] scripts/checkpatch.pl: avoid false warning missing break

On Sun, 2017-09-10 at 09:52 +0200, Heinrich Schuchardt wrote: > void foo(int a) > switch (a) { > case 'h': > fun1(); > exit(1); > default: > } > > creates a warning > Possible switch case/default not preceded by break > or fallthrough comment > >

Re: [PATCH 1/1] scripts/checkpatch.pl: avoid false warning missing break

On Sun, 2017-09-10 at 09:52 +0200, Heinrich Schuchardt wrote: > void foo(int a) > switch (a) { > case 'h': > fun1(); > exit(1); > default: > } > > creates a warning > Possible switch case/default not preceded by break > or fallthrough comment > >

Re: [GIT PULL] Security subsystem updates for 4.14

On Sun, 2017-09-10 at 01:10 -0700, Christoph Hellwig wrote: > On Fri, Sep 08, 2017 at 10:25:53AM -0700, Linus Torvalds wrote: > > I don't think anybody actually tests linux-next kernels in any big > > way, and the automated tests that do get run probably don't run with > > any integrity checking

Re: [GIT PULL] Security subsystem updates for 4.14

On Sun, 2017-09-10 at 01:10 -0700, Christoph Hellwig wrote: > On Fri, Sep 08, 2017 at 10:25:53AM -0700, Linus Torvalds wrote: > > I don't think anybody actually tests linux-next kernels in any big > > way, and the automated tests that do get run probably don't run with > > any integrity checking

Re: [RFC PATCH 0/3] kbuild: generate intermediate C files instead of copying _shipped files

Hi Sam, 2017-09-09 15:39 GMT+09:00 Sam Ravnborg : > On Fri, Sep 08, 2017 at 02:38:23PM -0700, Linus Torvalds wrote: >> On Fri, Sep 8, 2017 at 11:39 AM, Linus Torvalds >> wrote: >> > >> > Strange. Does anybody see what the pattern to the failure

Re: [RFC PATCH 0/3] kbuild: generate intermediate C files instead of copying _shipped files

Hi Sam, 2017-09-09 15:39 GMT+09:00 Sam Ravnborg : > On Fri, Sep 08, 2017 at 02:38:23PM -0700, Linus Torvalds wrote: >> On Fri, Sep 8, 2017 at 11:39 AM, Linus Torvalds >> wrote: >> > >> > Strange. Does anybody see what the pattern to the failure is? >> >> Found it. Stupid special case for

Re: [PATCH v5] iio: accel: mma8452: improvements to handle multiple events

Am 10. September 2017 15:44:24 MESZ schrieb Jonathan Cameron : >On Mon, 4 Sep 2017 23:06:37 -0400 >harinath Nampally wrote: > >> > I agree with your understanding. It's a rising threshold, just >that the input >> > will only reflect high frequency

Re: [PATCH v5] iio: accel: mma8452: improvements to handle multiple events

Am 10. September 2017 15:44:24 MESZ schrieb Jonathan Cameron : >On Mon, 4 Sep 2017 23:06:37 -0400 >harinath Nampally wrote: > >> > I agree with your understanding. It's a rising threshold, just >that the input >> > will only reflect high frequency changes in the signal. >> Thank you for the

Re: [RFC PATCH 0/3] kbuild: generate intermediate C files instead of copying _shipped files

Hi Linus, 2017-09-09 6:38 GMT+09:00 Linus Torvalds : > On Fri, Sep 8, 2017 at 11:39 AM, Linus Torvalds > wrote: >> >> Strange. Does anybody see what the pattern to the failure is? > > Found it. Stupid special case for 'typeof()' that

Re: [RFC PATCH 0/3] kbuild: generate intermediate C files instead of copying _shipped files

Hi Linus, 2017-09-09 6:38 GMT+09:00 Linus Torvalds : > On Fri, Sep 8, 2017 at 11:39 AM, Linus Torvalds > wrote: >> >> Strange. Does anybody see what the pattern to the failure is? > > Found it. Stupid special case for 'typeof()' that used > is_reserved_word() in ways I hadn't realized. > > Fix

[PATCH] spi: stm32: Fix logical error in stm32_spi_prepare_mbr()

stm32_spi_prepare_mbr() is returning an error value when div is less than SPI_MBR_DIV_MIN *and* greater than SPI_MBR_DIV_MAX, which always evaluates to false. This should change to use *or*. Signed-off-by: Christos Gkekas --- drivers/spi/spi-stm32.c | 4 ++-- 1 file

[PATCH] spi: stm32: Fix logical error in stm32_spi_prepare_mbr()

stm32_spi_prepare_mbr() is returning an error value when div is less than SPI_MBR_DIV_MIN *and* greater than SPI_MBR_DIV_MAX, which always evaluates to false. This should change to use *or*. Signed-off-by: Christos Gkekas --- drivers/spi/spi-stm32.c | 4 ++-- 1 file changed, 2 insertions(+), 2

Re: [PATCH 7/7] include/linux/string.h: add the option of fortified string.h functions

On Sun, Sep 10, 2017 at 12:55 PM, Geert Uytterhoeven wrote: 55e285a upstream. > >> --- a/include/linux/string.h >> +++ b/include/linux/string.h >> @@ -187,4 +187,204 @@ static inline const char *kbasename(const char *path) >> return tail ? tail + 1 : path; >> } >>

Re: [PATCH 7/7] include/linux/string.h: add the option of fortified string.h functions

On Sun, Sep 10, 2017 at 12:55 PM, Geert Uytterhoeven wrote: 55e285a upstream. > >> --- a/include/linux/string.h >> +++ b/include/linux/string.h >> @@ -187,4 +187,204 @@ static inline const char *kbasename(const char *path) >> return tail ? tail + 1 : path; >> } >> >> +#define

Re: [PATCH v5] iio: accel: mma8452: improvements to handle multiple events

On Mon, 4 Sep 2017 23:06:37 -0400 harinath Nampally wrote: > > I agree with your understanding. It's a rising threshold, just that the > > input > > will only reflect high frequency changes in the signal. > Thank you for the clarification. I am hoping this gets merged

Re: [PATCH v5] iio: accel: mma8452: improvements to handle multiple events

On Mon, 4 Sep 2017 23:06:37 -0400 harinath Nampally wrote: > > I agree with your understanding. It's a rising threshold, just that the > > input > > will only reflect high frequency changes in the signal. > Thank you for the clarification. I am hoping this gets merged in the > next window if

[lkp-robot] [x86/mm] f13c8e8c58: WARNING:at_arch/x86/mm/tlb.c:#initialize_tlbstate_and_flush

FYI, we noticed the following commit: commit: f13c8e8c58ba3b535f1e4cb9e62b50ab37dd69bb ("x86/mm: Reinitialize TLB state on hotplug and resume") https://git.kernel.org/cgit/linux/kernel/git/luto/linux.git x86/fixes in testcase: boot on test machine: qemu-system-x86_64 -enable-kvm -m 420M

[lkp-robot] [x86/mm] f13c8e8c58: WARNING:at_arch/x86/mm/tlb.c:#initialize_tlbstate_and_flush

FYI, we noticed the following commit: commit: f13c8e8c58ba3b535f1e4cb9e62b50ab37dd69bb ("x86/mm: Reinitialize TLB state on hotplug and resume") https://git.kernel.org/cgit/linux/kernel/git/luto/linux.git x86/fixes in testcase: boot on test machine: qemu-system-x86_64 -enable-kvm -m 420M

Re: [PATCH] test_bitmap: Use ULL suffix for 64-bit constants

On Sun, Sep 10, 2017 at 12:48:43PM +0200, Geert Uytterhoeven wrote: > With gcc 4.1.2: > > lib/test_bitmap.c:189: warning: integer constant is too large for ‘long’ > type > lib/test_bitmap.c:190: warning: integer constant is too large for ‘long’ > type > lib/test_bitmap.c:194:

Re: [PATCH] test_bitmap: Use ULL suffix for 64-bit constants

On Sun, Sep 10, 2017 at 12:48:43PM +0200, Geert Uytterhoeven wrote: > With gcc 4.1.2: > > lib/test_bitmap.c:189: warning: integer constant is too large for ‘long’ > type > lib/test_bitmap.c:190: warning: integer constant is too large for ‘long’ > type > lib/test_bitmap.c:194:

[PATCH] m68k: Add braces to __pmd(x) initializer to kill compiler warning

With gcc 4.1.2: include/linux/swapops.h: In function ‘swp_entry_to_pmd’: include/linux/swapops.h:294: warning: missing braces around initializer include/linux/swapops.h:294: warning: (near initialization for ‘(anonymous).pmd’) Due to a GCC zero initializer bug (#53119), the standard

[PATCH] m68k: Add braces to __pmd(x) initializer to kill compiler warning

With gcc 4.1.2: include/linux/swapops.h: In function ‘swp_entry_to_pmd’: include/linux/swapops.h:294: warning: missing braces around initializer include/linux/swapops.h:294: warning: (near initialization for ‘(anonymous).pmd’) Due to a GCC zero initializer bug (#53119), the standard

[PATCH] iio: adc: dln2-adc: initialize local struct before using it

struct data is defined and declared locally. Initiliazation has to be done manually, so let's add that. Signed-off-by: Martin Kepplinger --- This is more of a question actually! Did you have in mind that data is not initialized here? If so, please drop this patch. This is

[PATCH] iio: adc: dln2-adc: initialize local struct before using it

struct data is defined and declared locally. Initiliazation has to be done manually, so let's add that. Signed-off-by: Martin Kepplinger --- This is more of a question actually! Did you have in mind that data is not initialized here? If so, please drop this patch. This is just in case you

[PATCH 2/2] clk: sunxi-ng: add CLK_SET_RATE_PARENT flag to H3 GPU clock

The GPU clock on H3 has only one parent, PLL-GPU, and the PLL is only the parent of the GPU clock. The GPU clock can be tweaked by tweaking the PLL-GPU clock. Add CLK_SET_RATE_PARENT flag to allow tweaking the GPU clock via tweaking PLL-CPU. Fixes: 0577e4853bfb ("clk: sunxi-ng: Add H3 clocks")

[PATCH 1/2] clk: sunxi-ng: add CLK_SET_RATE_UNGATE to all H3 PLLs

The PLLs on H3 have a lock bit, which will only be set to 1 when the PLL is really working. Add CLK_SET_RATE_UNGATE to the PLLs, otherwise it will timeout when trying to set PLL clock frequency without enabling it. Fixes: 0577e4853bfb ("clk: sunxi-ng: Add H3 clocks") Signed-off-by: Icenowy Zheng

[PATCH 2/2] clk: sunxi-ng: add CLK_SET_RATE_PARENT flag to H3 GPU clock

The GPU clock on H3 has only one parent, PLL-GPU, and the PLL is only the parent of the GPU clock. The GPU clock can be tweaked by tweaking the PLL-GPU clock. Add CLK_SET_RATE_PARENT flag to allow tweaking the GPU clock via tweaking PLL-CPU. Fixes: 0577e4853bfb ("clk: sunxi-ng: Add H3 clocks")

[PATCH 1/2] clk: sunxi-ng: add CLK_SET_RATE_UNGATE to all H3 PLLs

The PLLs on H3 have a lock bit, which will only be set to 1 when the PLL is really working. Add CLK_SET_RATE_UNGATE to the PLLs, otherwise it will timeout when trying to set PLL clock frequency without enabling it. Fixes: 0577e4853bfb ("clk: sunxi-ng: Add H3 clocks") Signed-off-by: Icenowy Zheng

[PATCH 0/2] clk: sunxi-ng: Add several flags to H3 CCU

The H3 CCU is the earliest driver that uses sunxi-ng clk framework, and some problems show when doing further development. This patchset fixes some issues by add several clock flags. The first patch solves the problem that setting some PLL before ungating them will trigger timeout for waiting

[PATCH 0/2] clk: sunxi-ng: Add several flags to H3 CCU

The H3 CCU is the earliest driver that uses sunxi-ng clk framework, and some problems show when doing further development. This patchset fixes some issues by add several clock flags. The first patch solves the problem that setting some PLL before ungating them will trigger timeout for waiting

[PATCH] staging: atomisp: add a driver for ov5648 camera sensor

The ov5680 5-megapixel camera sensor from OmniVision supports up to 2592x1944 resolution and MIPI CSI-2 interface. Output format is raw sRGB/Bayer with 10 bits per colour (SGRBG10_1X10). This patch is a port of ov5680 driver from following 01org/ProductionKernelQuilts patches: -

[PATCH] staging: atomisp: add a driver for ov5648 camera sensor

The ov5680 5-megapixel camera sensor from OmniVision supports up to 2592x1944 resolution and MIPI CSI-2 interface. Output format is raw sRGB/Bayer with 10 bits per colour (SGRBG10_1X10). This patch is a port of ov5680 driver from following 01org/ProductionKernelQuilts patches: -

[PATCH] bnx2i: Clean up unused pointers in bnx2i_hwi

Pointers bnx2i_cmd are set but never used, so they can be removed. Signed-off-by: Christos Gkekas --- drivers/scsi/bnx2i/bnx2i_hwi.c | 10 -- 1 file changed, 10 deletions(-) diff --git a/drivers/scsi/bnx2i/bnx2i_hwi.c b/drivers/scsi/bnx2i/bnx2i_hwi.c index

[PATCH] bnx2i: Clean up unused pointers in bnx2i_hwi

Pointers bnx2i_cmd are set but never used, so they can be removed. Signed-off-by: Christos Gkekas --- drivers/scsi/bnx2i/bnx2i_hwi.c | 10 -- 1 file changed, 10 deletions(-) diff --git a/drivers/scsi/bnx2i/bnx2i_hwi.c b/drivers/scsi/bnx2i/bnx2i_hwi.c index 42921db..e3f22cb 100644 ---

<    1   2   3   4   5   6   >