[PATCH v4] ARM: dts: pxa: add mioa701 board description

2018-09-15 Thread Robert Jarzmik
Add device-tree description of the Mitac MIO A701 board. This is aimed at replacing mioa701.c board file, and once stabilized, the leftover, such as the suspend resume mechanics will rely on a new IPL, and not the legacy Windows CE one. Signed-off-by: Robert Jarzmik --- Since v1: fix lcd_supply

[PATCH v4] ARM: dts: pxa: add mioa701 board description

2018-09-15 Thread Robert Jarzmik
Add device-tree description of the Mitac MIO A701 board. This is aimed at replacing mioa701.c board file, and once stabilized, the leftover, such as the suspend resume mechanics will rely on a new IPL, and not the legacy Windows CE one. Signed-off-by: Robert Jarzmik --- Since v1: fix lcd_supply

[PATCH -next] iio: potentiometer: mcp4531: merge calls to of_match_device and of_device_get_match_data

2018-09-15 Thread YueHaibing
Drop call to of_match_device, which is subsumed by the subsequent call to of_device_get_match_data. The code becomes simpler, and a temporary variable can be dropped. Found by coccinelle. Signed-off-by: YueHaibing --- drivers/iio/potentiometer/mcp4531.c | 7 ++- 1 file changed, 2

[PATCH -next] iio: potentiometer: mcp4531: merge calls to of_match_device and of_device_get_match_data

2018-09-15 Thread YueHaibing
Drop call to of_match_device, which is subsumed by the subsequent call to of_device_get_match_data. The code becomes simpler, and a temporary variable can be dropped. Found by coccinelle. Signed-off-by: YueHaibing --- drivers/iio/potentiometer/mcp4531.c | 7 ++- 1 file changed, 2

[PATCH -next] iio: potentiometer: mcp4018: merge calls to of_match_device and of_device_get_match_data

2018-09-15 Thread YueHaibing
Drop call to of_match_device, which is subsumed by the subsequent call to of_device_get_match_data. The code becomes simpler, and a temporary variable can be dropped. Found by coccinelle. Signed-off-by: YueHaibing --- drivers/iio/potentiometer/mcp4018.c | 7 ++- 1 file changed, 2

[PATCH -next] iio: potentiometer: mcp4018: merge calls to of_match_device and of_device_get_match_data

2018-09-15 Thread YueHaibing
Drop call to of_match_device, which is subsumed by the subsequent call to of_device_get_match_data. The code becomes simpler, and a temporary variable can be dropped. Found by coccinelle. Signed-off-by: YueHaibing --- drivers/iio/potentiometer/mcp4018.c | 7 ++- 1 file changed, 2

[PATCH -next] iio: potentiometer: max5481: merge calls to of_match_device and of_device_get_match_data

2018-09-15 Thread YueHaibing
Drop call to of_match_device, which is subsumed by the subsequent call to of_device_get_match_data. The code becomes simpler, and a temporary variable can be dropped. Found by coccinelle. Signed-off-by: YueHaibing --- drivers/iio/potentiometer/max5481.c | 7 ++- 1 file changed, 2

[PATCH -next] iio: potentiometer: max5481: merge calls to of_match_device and of_device_get_match_data

2018-09-15 Thread YueHaibing
Drop call to of_match_device, which is subsumed by the subsequent call to of_device_get_match_data. The code becomes simpler, and a temporary variable can be dropped. Found by coccinelle. Signed-off-by: YueHaibing --- drivers/iio/potentiometer/max5481.c | 7 ++- 1 file changed, 2

Re: [PATCH] x86, mm: Reserver some memory for bootmem allocator for NO_BOOTMEM

2018-09-15 Thread Thomas Gleixner
On Tue, 11 Sep 2018, Feng Tang wrote: > Thanks for the suggestion, and I have 2 patches: one adds a build warning, > the other prepares fixmap page table on demand and doesn't need warning. The latter please. > But I met a problem, that the "__end_of_permanent_fixed_addresses" is > defined in

Re: [PATCH] x86, mm: Reserver some memory for bootmem allocator for NO_BOOTMEM

2018-09-15 Thread Thomas Gleixner
On Tue, 11 Sep 2018, Feng Tang wrote: > Thanks for the suggestion, and I have 2 patches: one adds a build warning, > the other prepares fixmap page table on demand and doesn't need warning. The latter please. > But I met a problem, that the "__end_of_permanent_fixed_addresses" is > defined in

Re: [PATCH 4/9] x86/intel_rdt: Fix invalid mode warning when

2018-09-15 Thread Thomas Gleixner
On Fri, 14 Sep 2018, Fenghua Yu wrote: > If information for a cache instance with more CLOSIDs than another is > being generated we thus encounter a warning like: > > [ 130.010591] [ cut here ] > [ 130.016680] invalid mode for closid 8 > [ 130.021791] WARNING: CPU: 88

Re: [PATCH 4/9] x86/intel_rdt: Fix invalid mode warning when

2018-09-15 Thread Thomas Gleixner
On Fri, 14 Sep 2018, Fenghua Yu wrote: > If information for a cache instance with more CLOSIDs than another is > being generated we thus encounter a warning like: > > [ 130.010591] [ cut here ] > [ 130.016680] invalid mode for closid 8 > [ 130.021791] WARNING: CPU: 88

Good Day To You

2018-09-15 Thread UNITED NATION
Attention Please!, This is to official inform you that we have been having meetings for the past Three (3) Weeks which ended two days ago with the World Bank president and other seven continent presidents on the Congress we treated on solution to Scam victim and the world economic crises that

Good Day To You

2018-09-15 Thread UNITED NATION
Attention Please!, This is to official inform you that we have been having meetings for the past Three (3) Weeks which ended two days ago with the World Bank president and other seven continent presidents on the Congress we treated on solution to Scam victim and the world economic crises that

Re: [PATCH 1/9] x86/intel_rdt: Fix MBA parsing callback

2018-09-15 Thread Thomas Gleixner
On Fri, 14 Sep 2018, Fenghua Yu wrote: > int parse_cbm(void *_data, struct rdt_resource *r, struct rdt_domain *d); > -int parse_bw(void *_buf, struct rdt_resource *r, struct rdt_domain *d); > +int parse_bw(void *_data, struct rdt_resource *r, struct rdt_domain *d); Sorry no. This keeps the code

Re: [PATCH 1/9] x86/intel_rdt: Fix MBA parsing callback

2018-09-15 Thread Thomas Gleixner
On Fri, 14 Sep 2018, Fenghua Yu wrote: > int parse_cbm(void *_data, struct rdt_resource *r, struct rdt_domain *d); > -int parse_bw(void *_buf, struct rdt_resource *r, struct rdt_domain *d); > +int parse_bw(void *_data, struct rdt_resource *r, struct rdt_domain *d); Sorry no. This keeps the code

Re: [RFC v10 PATCH 0/3] mm: zap pages with read mmap_sem in munmap for large mapping

2018-09-15 Thread Matthew Wilcox
On Sat, Sep 15, 2018 at 04:34:56AM +0800, Yang Shi wrote: > Regression and performance data: > Did the below regression test with setting thresh to 4K manually in the code: > * Full LTP > * Trinity (munmap/all vm syscalls) > * Stress-ng: mmap/mmapfork/mmapfixed/mmapaddr/mmapmany/vm > *

Re: [RFC v10 PATCH 0/3] mm: zap pages with read mmap_sem in munmap for large mapping

2018-09-15 Thread Matthew Wilcox
On Sat, Sep 15, 2018 at 04:34:56AM +0800, Yang Shi wrote: > Regression and performance data: > Did the below regression test with setting thresh to 4K manually in the code: > * Full LTP > * Trinity (munmap/all vm syscalls) > * Stress-ng: mmap/mmapfork/mmapfixed/mmapaddr/mmapmany/vm > *

Linux 4.18.8

2018-09-15 Thread Greg KH
I'm announcing the release of the 4.18.8 kernel. All users of the 4.18 kernel series must upgrade. The updated 4.18.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.18.y and can be browsed at the normal kernel.org git web browser:

Linux 4.18.8

2018-09-15 Thread Greg KH
I'm announcing the release of the 4.18.8 kernel. All users of the 4.18 kernel series must upgrade. The updated 4.18.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.18.y and can be browsed at the normal kernel.org git web browser:

Linux 4.14.70

2018-09-15 Thread Greg KH
I'm announcing the release of the 4.14.70 kernel. All users of the 4.14 kernel series must upgrade. The updated 4.14.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.14.y and can be browsed at the normal kernel.org git web

Linux 4.14.70

2018-09-15 Thread Greg KH
I'm announcing the release of the 4.14.70 kernel. All users of the 4.14 kernel series must upgrade. The updated 4.14.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.14.y and can be browsed at the normal kernel.org git web

Re: Linux 4.9.127

2018-09-15 Thread Greg KH
diff --git a/Makefile b/Makefile index b26481fef3f0..4e37716ae395 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 4 PATCHLEVEL = 9 -SUBLEVEL = 126 +SUBLEVEL = 127 EXTRAVERSION = NAME = Roaring Lionus diff --git a/arch/arm/configs/imx_v6_v7_defconfig

Re: Linux 4.14.70

2018-09-15 Thread Greg KH
diff --git a/Makefile b/Makefile index 3ecda1d2e23a..aa458afa7fa2 100644 --- a/Makefile +++ b/Makefile @@ -1,7 +1,7 @@ # SPDX-License-Identifier: GPL-2.0 VERSION = 4 PATCHLEVEL = 14 -SUBLEVEL = 69 +SUBLEVEL = 70 EXTRAVERSION = NAME = Petit Gorille diff --git

Re: Linux 4.9.127

2018-09-15 Thread Greg KH
diff --git a/Makefile b/Makefile index b26481fef3f0..4e37716ae395 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 4 PATCHLEVEL = 9 -SUBLEVEL = 126 +SUBLEVEL = 127 EXTRAVERSION = NAME = Roaring Lionus diff --git a/arch/arm/configs/imx_v6_v7_defconfig

Re: Linux 4.14.70

2018-09-15 Thread Greg KH
diff --git a/Makefile b/Makefile index 3ecda1d2e23a..aa458afa7fa2 100644 --- a/Makefile +++ b/Makefile @@ -1,7 +1,7 @@ # SPDX-License-Identifier: GPL-2.0 VERSION = 4 PATCHLEVEL = 14 -SUBLEVEL = 69 +SUBLEVEL = 70 EXTRAVERSION = NAME = Petit Gorille diff --git

Linux 4.9.127

2018-09-15 Thread Greg KH
I'm announcing the release of the 4.9.127 kernel. All users of the 4.9 kernel series must upgrade. The updated 4.9.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.9.y and can be browsed at the normal kernel.org git web browser:

Re: Linux 4.4.156

2018-09-15 Thread Greg KH
diff --git a/Makefile b/Makefile index 2d9f89ec8397..6dd5924a7ea5 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 4 PATCHLEVEL = 4 -SUBLEVEL = 155 +SUBLEVEL = 156 EXTRAVERSION = NAME = Blurry Fish Butt diff --git a/arch/arm/configs/imx_v6_v7_defconfig

Linux 4.9.127

2018-09-15 Thread Greg KH
I'm announcing the release of the 4.9.127 kernel. All users of the 4.9 kernel series must upgrade. The updated 4.9.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.9.y and can be browsed at the normal kernel.org git web browser:

Re: Linux 4.4.156

2018-09-15 Thread Greg KH
diff --git a/Makefile b/Makefile index 2d9f89ec8397..6dd5924a7ea5 100644 --- a/Makefile +++ b/Makefile @@ -1,6 +1,6 @@ VERSION = 4 PATCHLEVEL = 4 -SUBLEVEL = 155 +SUBLEVEL = 156 EXTRAVERSION = NAME = Blurry Fish Butt diff --git a/arch/arm/configs/imx_v6_v7_defconfig

Linux 4.4.156

2018-09-15 Thread Greg KH
I'm announcing the release of the 4.4.156 kernel. All users of the 4.4 kernel series must upgrade. The updated 4.4.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.4.y and can be browsed at the normal kernel.org git web browser:

Linux 4.4.156

2018-09-15 Thread Greg KH
I'm announcing the release of the 4.4.156 kernel. All users of the 4.4 kernel series must upgrade. The updated 4.4.y git tree can be found at: git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git linux-4.4.y and can be browsed at the normal kernel.org git web browser:

[PATCH v5] iio: proximity: Add driver support for ST's VL53L0X ToF ranging sensor.

2018-09-15 Thread Song Qiang
This driver was originally written by ST in 2016 as a misc input device driver, and hasn't been maintained for a long time. I grabbed some code from it's API and reformed it into an iio proximity device driver. This version of driver uses i2c bus to talk to the sensor and polling for measuring

[PATCH v5] iio: proximity: Add driver support for ST's VL53L0X ToF ranging sensor.

2018-09-15 Thread Song Qiang
This driver was originally written by ST in 2016 as a misc input device driver, and hasn't been maintained for a long time. I grabbed some code from it's API and reformed it into an iio proximity device driver. This version of driver uses i2c bus to talk to the sensor and polling for measuring

Re: [RFC v10 PATCH 2/3] mm: unmap VM_HUGETLB mappings with optimized path

2018-09-15 Thread Matthew Wilcox
On Sat, Sep 15, 2018 at 04:34:58AM +0800, Yang Shi wrote: > When unmapping VM_HUGETLB mappings, vm flags need to be updated. Since > the vmas have been detached, so it sounds safe to update vm flags with > read mmap_sem. > > Cc: Michal Hocko > Cc: Vlastimil Babka > Signed-off-by: Yang Shi

Re: [RFC v10 PATCH 3/3] mm: unmap VM_PFNMAP mappings with optimized path

2018-09-15 Thread Matthew Wilcox
On Sat, Sep 15, 2018 at 04:34:59AM +0800, Yang Shi wrote: > When unmapping VM_PFNMAP mappings, vm flags need to be updated. Since > the vmas have been detached, so it sounds safe to update vm flags with > read mmap_sem. > > Cc: Michal Hocko > Cc: Vlastimil Babka > Signed-off-by: Yang Shi

Re: [RFC v10 PATCH 2/3] mm: unmap VM_HUGETLB mappings with optimized path

2018-09-15 Thread Matthew Wilcox
On Sat, Sep 15, 2018 at 04:34:58AM +0800, Yang Shi wrote: > When unmapping VM_HUGETLB mappings, vm flags need to be updated. Since > the vmas have been detached, so it sounds safe to update vm flags with > read mmap_sem. > > Cc: Michal Hocko > Cc: Vlastimil Babka > Signed-off-by: Yang Shi

Re: [RFC v10 PATCH 3/3] mm: unmap VM_PFNMAP mappings with optimized path

2018-09-15 Thread Matthew Wilcox
On Sat, Sep 15, 2018 at 04:34:59AM +0800, Yang Shi wrote: > When unmapping VM_PFNMAP mappings, vm flags need to be updated. Since > the vmas have been detached, so it sounds safe to update vm flags with > read mmap_sem. > > Cc: Michal Hocko > Cc: Vlastimil Babka > Signed-off-by: Yang Shi

Re: [Patch v3 00/16] CIFS: add support for direct I/O

2018-09-15 Thread Steve French
could you rebase these, patch 1 was merged quite a while ago, and patch 2 etc. doesn't apply cleanly On Fri, Sep 7, 2018 at 9:18 PM Long Li wrote: > > From: Long Li > > This patch set implements direct I/O. > > In normal code path (even with cache=none), CIFS copies I/O data from > user-space to

Re: [Patch v3 00/16] CIFS: add support for direct I/O

2018-09-15 Thread Steve French
could you rebase these, patch 1 was merged quite a while ago, and patch 2 etc. doesn't apply cleanly On Fri, Sep 7, 2018 at 9:18 PM Long Li wrote: > > From: Long Li > > This patch set implements direct I/O. > > In normal code path (even with cache=none), CIFS copies I/O data from > user-space to

Re: [RFC v10 PATCH 1/3] mm: mmap: zap pages with read mmap_sem in munmap

2018-09-15 Thread Matthew Wilcox
On Sat, Sep 15, 2018 at 04:34:57AM +0800, Yang Shi wrote: > Suggested-by: Michal Hocko > Suggested-by: Kirill A. Shutemov > Suggested-by: Matthew Wilcox Reviewed-by: Matthew Wilcox Looks good! Thanks for sticking with this patch series. Minor spelling fixes: > - /* > - * Remove

Re: [RFC v10 PATCH 1/3] mm: mmap: zap pages with read mmap_sem in munmap

2018-09-15 Thread Matthew Wilcox
On Sat, Sep 15, 2018 at 04:34:57AM +0800, Yang Shi wrote: > Suggested-by: Michal Hocko > Suggested-by: Kirill A. Shutemov > Suggested-by: Matthew Wilcox Reviewed-by: Matthew Wilcox Looks good! Thanks for sticking with this patch series. Minor spelling fixes: > - /* > - * Remove

Re: [PATCH] arm64: dts: rockchip: add initial dts support for Rockpro64 board

2018-09-15 Thread agajjar
Hi Heiko, On 9/14/2018 11:23 PM, Heiko Stuebner wrote: Hi Akash, Am Freitag, 14. September 2018, 14:09:09 CEST schrieb Akash Gajjar: Rockpro64 board is a rockchip RK3399 based board from pine64.org. This commit adds initial device tree support for Rockpro64 board. Signed-off-by: Akash Gajjar

Re: [PATCH] arm64: dts: rockchip: add initial dts support for Rockpro64 board

2018-09-15 Thread agajjar
Hi Heiko, On 9/14/2018 11:23 PM, Heiko Stuebner wrote: Hi Akash, Am Freitag, 14. September 2018, 14:09:09 CEST schrieb Akash Gajjar: Rockpro64 board is a rockchip RK3399 based board from pine64.org. This commit adds initial device tree support for Rockpro64 board. Signed-off-by: Akash Gajjar

[BUG] mfd: ezx-pcap: Possible sleep-in-atomic-context bugs in pcap_adc_irq()

2018-09-15 Thread Jia-Ju Bai
The driver may sleep in an interrupt handler. The function call paths (from bottom to top) in Linux-4.17 are: [FUNC] mutex_lock_nested drivers/mfd/ezx-pcap.c, 272: mutex_lock_nested in pcap_adc_irq (interrupt handler) [FUNC] mutex_lock_nested drivers/mfd/ezx-pcap.c, 100:

[BUG] mfd: ezx-pcap: Possible sleep-in-atomic-context bugs in pcap_adc_irq()

2018-09-15 Thread Jia-Ju Bai
The driver may sleep in an interrupt handler. The function call paths (from bottom to top) in Linux-4.17 are: [FUNC] mutex_lock_nested drivers/mfd/ezx-pcap.c, 272: mutex_lock_nested in pcap_adc_irq (interrupt handler) [FUNC] mutex_lock_nested drivers/mfd/ezx-pcap.c, 100:

Task group cleanups and optimizations (was: Re: [RFC 00/60] Coscheduling for Linux)

2018-09-15 Thread Jan H. Schönherr
On 09/14/2018 06:25 PM, Jan H. Schönherr wrote: > On 09/14/2018 01:12 PM, Peter Zijlstra wrote: >> >> There are known scalability problems with the existing cgroup muck; you >> just made things a ton worse. The existing cgroup overhead is >> significant, you also made that many times worse. >> >>

Task group cleanups and optimizations (was: Re: [RFC 00/60] Coscheduling for Linux)

2018-09-15 Thread Jan H. Schönherr
On 09/14/2018 06:25 PM, Jan H. Schönherr wrote: > On 09/14/2018 01:12 PM, Peter Zijlstra wrote: >> >> There are known scalability problems with the existing cgroup muck; you >> just made things a ton worse. The existing cgroup overhead is >> significant, you also made that many times worse. >> >>

[tip:x86/urgent] x86/APM: Fix build warning when PROC_FS is not enabled

2018-09-15 Thread tip-bot for Randy Dunlap
Commit-ID: 002b87d2aace62b4f3841c3aa43309d2380092be Gitweb: https://git.kernel.org/tip/002b87d2aace62b4f3841c3aa43309d2380092be Author: Randy Dunlap AuthorDate: Fri, 14 Sep 2018 15:10:29 -0700 Committer: Thomas Gleixner CommitDate: Sat, 15 Sep 2018 10:16:25 +0200 x86/APM: Fix build

[tip:x86/urgent] x86/APM: Fix build warning when PROC_FS is not enabled

2018-09-15 Thread tip-bot for Randy Dunlap
Commit-ID: 002b87d2aace62b4f3841c3aa43309d2380092be Gitweb: https://git.kernel.org/tip/002b87d2aace62b4f3841c3aa43309d2380092be Author: Randy Dunlap AuthorDate: Fri, 14 Sep 2018 15:10:29 -0700 Committer: Thomas Gleixner CommitDate: Sat, 15 Sep 2018 10:16:25 +0200 x86/APM: Fix build

Re: [PATCH 4.14 000/115] 4.14.70-stable review

2018-09-15 Thread Greg Kroah-Hartman
On Fri, Sep 14, 2018 at 03:47:47PM -0700, Eduardo Valentin wrote: > On Thu, Sep 13, 2018 at 03:30:20PM +0200, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.14.70 release. > > There are 115 patches in this series, all will be posted as a response > > to this

Re: [PATCH 4.14 000/115] 4.14.70-stable review

2018-09-15 Thread Greg Kroah-Hartman
On Fri, Sep 14, 2018 at 03:47:47PM -0700, Eduardo Valentin wrote: > On Thu, Sep 13, 2018 at 03:30:20PM +0200, Greg Kroah-Hartman wrote: > > This is the start of the stable review cycle for the 4.14.70 release. > > There are 115 patches in this series, all will be posted as a response > > to this

Re: [patch V2 04/10] x86/mm/cpa: Add debug mechanism

2018-09-15 Thread kbuild test robot
/linux/commits/Thomas-Gleixner/x86-mm-cpa-Improve-large-page-preservation-handling/20180915-062636 config: i386-randconfig-sb0-09151101 (attached as .config) compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4 reproduce: # save the attached .config to linux build tree make ARCH=i386 All warnings

Re: [patch V2 04/10] x86/mm/cpa: Add debug mechanism

2018-09-15 Thread kbuild test robot
/linux/commits/Thomas-Gleixner/x86-mm-cpa-Improve-large-page-preservation-handling/20180915-062636 config: i386-randconfig-sb0-09151101 (attached as .config) compiler: gcc-4.9 (Debian 4.9.4-2) 4.9.4 reproduce: # save the attached .config to linux build tree make ARCH=i386 All warnings

Re: [PTCH] x86: APM: fix build warning when PROC_FS is not enabled

2018-09-15 Thread Christoph Hellwig
Thanks, this looks good to me: Reviewed-by: Christoph Hellwig

Re: [PTCH] x86: APM: fix build warning when PROC_FS is not enabled

2018-09-15 Thread Christoph Hellwig
Thanks, this looks good to me: Reviewed-by: Christoph Hellwig

Re: [PATCH] cpufreq: intel_pstate: Optimize IO boost in non HWP mode

2018-09-15 Thread Francisco Jerez
"Rafael J. Wysocki" writes: > On Tuesday, September 11, 2018 7:35:15 PM CEST Francisco Jerez wrote: >> >> "Rafael J. Wysocki" writes: >> >> > On Thursday, September 6, 2018 6:20:08 AM CEST Francisco Jerez wrote: >> > >> >> Srinivas Pandruvada writes: >> >>=20 >> >> > [...] >> >> > >> >> >> >

Re: [PATCH] cpufreq: intel_pstate: Optimize IO boost in non HWP mode

2018-09-15 Thread Francisco Jerez
"Rafael J. Wysocki" writes: > On Tuesday, September 11, 2018 7:35:15 PM CEST Francisco Jerez wrote: >> >> "Rafael J. Wysocki" writes: >> >> > On Thursday, September 6, 2018 6:20:08 AM CEST Francisco Jerez wrote: >> > >> >> Srinivas Pandruvada writes: >> >>=20 >> >> > [...] >> >> > >> >> >> >

Re: [PATCH] arm: common: use match_string() helper to simplify the code

2018-09-15 Thread zhong jiang
us a note to > help improve the system] > > url: > https://github.com/0day-ci/linux/commits/zhong-jiang/arm-common-use-match_string-helper-to-simplify-the-code/20180915-035510 > base: https://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git > for-next > config: a

Re: [PATCH] arm: common: use match_string() helper to simplify the code

2018-09-15 Thread zhong jiang
us a note to > help improve the system] > > url: > https://github.com/0day-ci/linux/commits/zhong-jiang/arm-common-use-match_string-helper-to-simplify-the-code/20180915-035510 > base: https://git.kernel.org/pub/scm/linux/kernel/git/arm/arm-soc.git > for-next > config: a

[PATCH] misc: echo: Remove unnecessary parentheses and simplify check for zero

2018-09-15 Thread Nathan Chancellor
Clang warns when multiple pairs of parentheses are used for a single conditional statement. drivers/misc/echo/echo.c:384:27: warning: equality comparison with extraneous parentheses [-Wparentheses-equality] if ((ec->nonupdate_dwell == 0)) { ^~~~

[PATCH] misc: echo: Remove unnecessary parentheses and simplify check for zero

2018-09-15 Thread Nathan Chancellor
Clang warns when multiple pairs of parentheses are used for a single conditional statement. drivers/misc/echo/echo.c:384:27: warning: equality comparison with extraneous parentheses [-Wparentheses-equality] if ((ec->nonupdate_dwell == 0)) { ^~~~

<    1   2   3