[PATCH v3 22/25] dt-bindings: power: Add Owl SPS power domains

Define power domains for all non-reserved S500 power gates. Signed-off-by: Andreas Färber --- v3: new .../devicetree/bindings/power/actions,owl-sps.txt | 17 + include/dt-bindings/power/s500-powergate.h| 19 +++ 2 files changed, 36

[PATCH v3 21/25] ARM: dts: s500: Set CPU enable-method

Use a custom S500 enable-method for all CPUs. Signed-off-by: Andreas Färber --- v3: new arch/arm/boot/dts/s500.dtsi | 4 1 file changed, 4 insertions(+) diff --git a/arch/arm/boot/dts/s500.dtsi b/arch/arm/boot/dts/s500.dtsi index 1973181..b4ebd27 100644 ---

[PATCH v3 18/25] ARM: dts: s500-guitar-bb-rev-b: Add fake uart3 clock

Add a fixed-clock for baudrate 115200. Signed-off-by: Andreas Färber --- v2 -> v3: unchanged v2: new arch/arm/boot/dts/s500-guitar-bb-rev-b.dts | 7 +++ 1 file changed, 7 insertions(+) diff --git a/arch/arm/boot/dts/s500-guitar-bb-rev-b.dts

[PATCH v3 18/25] ARM: dts: s500-guitar-bb-rev-b: Add fake uart3 clock

Add a fixed-clock for baudrate 115200. Signed-off-by: Andreas Färber --- v2 -> v3: unchanged v2: new arch/arm/boot/dts/s500-guitar-bb-rev-b.dts | 7 +++ 1 file changed, 7 insertions(+) diff --git a/arch/arm/boot/dts/s500-guitar-bb-rev-b.dts

Re: [PATCH V11 10/10] arm/arm64: KVM: add guest SEA support

Hi James, On 2017/2/27 21:58, James Morse wrote: > Hi Wang Xiongfeng, > > On 25/02/17 07:15, Xiongfeng Wang wrote: >> On 2017/2/22 5:22, Tyler Baicar wrote: >>> Currently external aborts are unsupported by the guest abort >>> handling. Add handling for SEAs so that the host kernel reports >>>

Re: [PATCH V11 10/10] arm/arm64: KVM: add guest SEA support

Hi James, On 2017/2/27 21:58, James Morse wrote: > Hi Wang Xiongfeng, > > On 25/02/17 07:15, Xiongfeng Wang wrote: >> On 2017/2/22 5:22, Tyler Baicar wrote: >>> Currently external aborts are unsupported by the guest abort >>> handling. Add handling for SEAs so that the host kernel reports >>>

NVME M2 devices on RAID configured controllers

More and more system are coming with M2 devices on RAID configured controllers which Linux does not support. Switching to AHCI mode instead of RAID mode allows it to see the drives but that is not a fix when you want it in RAID mode and want to use Windows as well. The question I have is this

NVME M2 devices on RAID configured controllers

More and more system are coming with M2 devices on RAID configured controllers which Linux does not support. Switching to AHCI mode instead of RAID mode allows it to see the drives but that is not a fix when you want it in RAID mode and want to use Windows as well. The question I have is this

Re: [RFC 7/8] fpga-region: add sysfs interface

On Mon, 27 Feb 2017, Moritz Fischer wrote: Alan, On Mon, Feb 27, 2017 at 12:09 PM, Alan Tull wrote: First case: embedded FPGA. The hardware has one FPGA. The image is designed for a specific board, so there's no problem including the enumeration in the

Re: [v2] Input: pwm-beeper: support customized freq for SND_BELL

On February 27, 2017 10:13:43 PM PST, Heiko Schocher wrote: >Hello David, > >Am 28.02.2017 um 06:30 schrieb David Lechner: >> On 02/27/2017 11:19 PM, Heiko Schocher wrote: >>> Hello David, >>> >>> Am 27.02.2017 um 19:11 schrieb David Lechner: On 02/20/2017 02:37 AM, Heiko

Re: [RFC 7/8] fpga-region: add sysfs interface

On Mon, 27 Feb 2017, Moritz Fischer wrote: Alan, On Mon, Feb 27, 2017 at 12:09 PM, Alan Tull wrote: First case: embedded FPGA. The hardware has one FPGA. The image is designed for a specific board, so there's no problem including the enumeration in the image. Agreed. Second case:

Re: [v2] Input: pwm-beeper: support customized freq for SND_BELL

On February 27, 2017 10:13:43 PM PST, Heiko Schocher wrote: >Hello David, > >Am 28.02.2017 um 06:30 schrieb David Lechner: >> On 02/27/2017 11:19 PM, Heiko Schocher wrote: >>> Hello David, >>> >>> Am 27.02.2017 um 19:11 schrieb David Lechner: On 02/20/2017 02:37 AM, Heiko Schocher wrote:

Re: [RFC][PATCH 1/2] drm/probe-helper: Add mode_valid check to drm_crtc_helper_funcs

On Mon, Feb 20, 2017 at 2:32 PM, Daniel Vetter wrote: > I thought about this some more, I think what we need to fix this mess > properly is: > - mode_valid helper callbacks for crtc, encoder, bridges, with the > same interface as for connectors. > - calling all these new

Re: [RFC][PATCH 1/2] drm/probe-helper: Add mode_valid check to drm_crtc_helper_funcs

On Mon, Feb 20, 2017 at 2:32 PM, Daniel Vetter wrote: > I thought about this some more, I think what we need to fix this mess > properly is: > - mode_valid helper callbacks for crtc, encoder, bridges, with the > same interface as for connectors. > - calling all these new mode_valid hooks from the

Re: [PATCH v2] scsi: ufs: Factor out ufshcd_read_desc_param

> "Michal" == Potomski, MichalX writes: Michal> Since in UFS 2.1 specification some of the descriptor lengths Michal> differs from 2.0 specification and some devices, which are Michal> reporting spec version 2.0 have different descriptor lengths we Michal> can not

Re: [PATCH v2] scsi: ufs: Factor out ufshcd_read_desc_param

> "Michal" == Potomski, MichalX writes: Michal> Since in UFS 2.1 specification some of the descriptor lengths Michal> differs from 2.0 specification and some devices, which are Michal> reporting spec version 2.0 have different descriptor lengths we Michal> can not rely on hardcoded values

[PATCH] fix pinctrl setup for i.IMX6

Hi! Recent pulls for mainline pre 4.11 introduced pinctrl setup changes and moved pinctrl-imx to use generic helpers. Net effect was that hog group could not be resolved. I made it work for myself with a two stage setup with create and start separated, and dt probe in between them.

[PATCH] fix pinctrl setup for i.IMX6

Hi! Recent pulls for mainline pre 4.11 introduced pinctrl setup changes and moved pinctrl-imx to use generic helpers. Net effect was that hog group could not be resolved. I made it work for myself with a two stage setup with create and start separated, and dt probe in between them.

Re: [PATCH v5] staging: xgifb: correct the multiple line dereference

On Tue, 2017-02-28 at 07:55 +0530, Arushi Singhal wrote: > Error reported by checkpatch.pl as "avoid multiple line dereference". > Addition of new variables to make the code more readable and also to > correct about mentioned error as by itroducing new variables line is > not exceeding 80

Re: [PATCH v5] staging: xgifb: correct the multiple line dereference

On Tue, 2017-02-28 at 07:55 +0530, Arushi Singhal wrote: > Error reported by checkpatch.pl as "avoid multiple line dereference". > Addition of new variables to make the code more readable and also to > correct about mentioned error as by itroducing new variables line is > not exceeding 80

[PATCH v5 3/5] staging: ks7010: fix coding style issue of using pr_notice instead of printk

Signed-off-by: Chetan Sethi --- v2: - split multiple changes across different patches v3: - mentioned patch revision in subject v4: - modified description to exclude mention of patch number from changelog - updated subject to include driver name v5: - updated series for

[PATCH v5 3/5] staging: ks7010: fix coding style issue of using pr_notice instead of printk

Signed-off-by: Chetan Sethi --- v2: - split multiple changes across different patches v3: - mentioned patch revision in subject v4: - modified description to exclude mention of patch number from changelog - updated subject to include driver name v5: - updated series for removing additional

Re: Still OOM problems with 4.9er/4.10er kernels

On 27.02.2017 09:27, Michal Hocko wrote: On Sun 26-02-17 09:40:42, Gerhard Wiesinger wrote: On 04.01.2017 10:11, Michal Hocko wrote: The VM stops working (e.g. not pingable) after around 8h (will be restarted automatically), happened serveral times. Had also further OOMs which I sent to

Re: Still OOM problems with 4.9er/4.10er kernels

On 27.02.2017 09:27, Michal Hocko wrote: On Sun 26-02-17 09:40:42, Gerhard Wiesinger wrote: On 04.01.2017 10:11, Michal Hocko wrote: The VM stops working (e.g. not pingable) after around 8h (will be restarted automatically), happened serveral times. Had also further OOMs which I sent to

Re: [PATCH v6] staging: xgifb: correct the multiple line dereference

On Tue, Feb 28, 2017 at 10:35:30AM +0530, Arushi Singhal wrote: > Error reported by checkpatch.pl as "avoid multiple line dereference". > Addition of new variables to make the code more readable and also to > correct about mentioned error as by itroducing new variables line is > not exceeding 80

Re: [PATCH v6] staging: xgifb: correct the multiple line dereference

On Tue, Feb 28, 2017 at 10:35:30AM +0530, Arushi Singhal wrote: > Error reported by checkpatch.pl as "avoid multiple line dereference". > Addition of new variables to make the code more readable and also to > correct about mentioned error as by itroducing new variables line is > not exceeding 80

Re: [PATCH v3 2/2] perf/sdt: Directly record SDT events with 'perf record'

On Fri, 24 Feb 2017 13:13:25 +0530 Ravi Bangoria wrote: > From: Hemant Kumar > > Add support for directly recording SDT events which are present in > the probe cache. Without this patch, we could probe into SDT events > using 'perf

Re: [PATCH v3 2/2] perf/sdt: Directly record SDT events with 'perf record'

On Fri, 24 Feb 2017 13:13:25 +0530 Ravi Bangoria wrote: > From: Hemant Kumar > > Add support for directly recording SDT events which are present in > the probe cache. Without this patch, we could probe into SDT events > using 'perf probe' and 'perf record'. With this patch, we can probe > the

[PATCH] x86/acpi: Fix a warning message in logical CPU IDs allocation

Current warning message regarded the "nr_cpu_ids - 1" as the limit number of the CPUs. It may be confused us, for example: we have two CPUs, nr_cpu_ids = 2, but the warning message may indicate that we just have 1 CPU, which likes that: Only 1 processors supported.Processor 2/0x2 and the rest

[PATCH] x86/acpi: Fix a warning message in logical CPU IDs allocation

Current warning message regarded the "nr_cpu_ids - 1" as the limit number of the CPUs. It may be confused us, for example: we have two CPUs, nr_cpu_ids = 2, but the warning message may indicate that we just have 1 CPU, which likes that: Only 1 processors supported.Processor 2/0x2 and the rest

Re: Still OOM problems with 4.9er/4.10er kernels

On Mon, Feb 27, 2017 at 10:44:49AM +0100, Michal Hocko wrote: > On Mon 27-02-17 18:02:36, Minchan Kim wrote: > [...] > > >From 9779a1c5d32e2edb64da5cdfcd6f9737b94a247a Mon Sep 17 00:00:00 2001 > > From: Minchan Kim > > Date: Mon, 27 Feb 2017 17:39:06 +0900 > > Subject: [PATCH]

Re: Still OOM problems with 4.9er/4.10er kernels

On Mon, Feb 27, 2017 at 10:44:49AM +0100, Michal Hocko wrote: > On Mon 27-02-17 18:02:36, Minchan Kim wrote: > [...] > > >From 9779a1c5d32e2edb64da5cdfcd6f9737b94a247a Mon Sep 17 00:00:00 2001 > > From: Minchan Kim > > Date: Mon, 27 Feb 2017 17:39:06 +0900 > > Subject: [PATCH] mm: use up

Re: [PATCH V5 4/6] mm: reclaim MADV_FREE pages

On Mon, Feb 27, 2017 at 08:19:08AM -0800, Shaohua Li wrote: > On Mon, Feb 27, 2017 at 03:33:15PM +0900, Minchan Kim wrote: > > Hi Shaohua, > > > > On Fri, Feb 24, 2017 at 01:31:47PM -0800, Shaohua Li wrote: > > > When memory pressure is high, we free MADV_FREE pages. If the pages are > > > not

Re: [PATCH V5 4/6] mm: reclaim MADV_FREE pages

On Mon, Feb 27, 2017 at 08:19:08AM -0800, Shaohua Li wrote: > On Mon, Feb 27, 2017 at 03:33:15PM +0900, Minchan Kim wrote: > > Hi Shaohua, > > > > On Fri, Feb 24, 2017 at 01:31:47PM -0800, Shaohua Li wrote: > > > When memory pressure is high, we free MADV_FREE pages. If the pages are > > > not

[PATCH] IB/qib: fix false-postive maybe-uninitialized warning

aarch64-linux-gcc-7 complains about code it doesn't fully understand: drivers/infiniband/hw/qib/qib_iba7322.c: In function 'qib_7322_txchk_change': include/asm-generic/bitops/non-atomic.h:105:35: error: 'shadow' may be used uninitialized in this function [-Werror=maybe-uninitialized] The code

[PATCH] IB/qib: fix false-postive maybe-uninitialized warning

aarch64-linux-gcc-7 complains about code it doesn't fully understand: drivers/infiniband/hw/qib/qib_iba7322.c: In function 'qib_7322_txchk_change': include/asm-generic/bitops/non-atomic.h:105:35: error: 'shadow' may be used uninitialized in this function [-Werror=maybe-uninitialized] The code

[PATCH V2 5/9] Staging: rtl8712: rtl871x_mp_ioctl.h - style fix

Fixed style of block comments Found using checkpatch Signed-off-by: Derek Robson --- Version #1 introduced lines over 80. This version moves comments to be above the line of code. drivers/staging/rtl8712/rtl871x_mp_ioctl.h | 173 - 1 file

[PATCH V2 5/9] Staging: rtl8712: rtl871x_mp_ioctl.h - style fix

Fixed style of block comments Found using checkpatch Signed-off-by: Derek Robson --- Version #1 introduced lines over 80. This version moves comments to be above the line of code. drivers/staging/rtl8712/rtl871x_mp_ioctl.h | 173 - 1 file changed, 98 insertions(+),

Re: [PATCH V3 1/7] PM / Domains: Introduce "performance-states" binding

On 27-02-17, 18:31, Rob Herring wrote: > On Fri, Feb 24, 2017 at 02:36:33PM +0530, Viresh Kumar wrote: > > Some platforms have the capability to configure the performance state of > > their power domains. The process of configuring the performance state is > > pretty much platform dependent and we

Re: [PATCH V3 1/7] PM / Domains: Introduce "performance-states" binding

On 27-02-17, 18:31, Rob Herring wrote: > On Fri, Feb 24, 2017 at 02:36:33PM +0530, Viresh Kumar wrote: > > Some platforms have the capability to configure the performance state of > > their power domains. The process of configuring the performance state is > > pretty much platform dependent and we

Re: [PATCH v2 3/3] media: dt-bindings: vpif: new optional property

On Tuesday 28 February 2017 04:22 AM, Rob Herring wrote: > On Wed, Feb 22, 2017 at 02:43:47PM +0100, Bartosz Golaszewski wrote: >> Add an optional property - enable-gpios - which can be used to specify >> the GPIOs that must be requested to select the vpif functionality. >> >> Signed-off-by:

Re: [PATCH v2 3/3] media: dt-bindings: vpif: new optional property

On Tuesday 28 February 2017 04:22 AM, Rob Herring wrote: > On Wed, Feb 22, 2017 at 02:43:47PM +0100, Bartosz Golaszewski wrote: >> Add an optional property - enable-gpios - which can be used to specify >> the GPIOs that must be requested to select the vpif functionality. >> >> Signed-off-by:

Re: [f2fs-dev] [PATCH 2/3 v2] f2fs: add bitmaps for empty or full NAT blocks

On 02/28, Chao Yu wrote: > On 2017/2/24 6:58, Jaegeuk Kim wrote: > > @@ -2326,7 +2431,8 @@ void flush_nat_entries(struct f2fs_sb_info *sbi) > > * entries, remove all entries from journal and merge them > > * into nat entry set. > > */ > > - if (!__has_cursum_space(journal,

Re: [f2fs-dev] [PATCH 2/3 v2] f2fs: add bitmaps for empty or full NAT blocks

On 02/28, Chao Yu wrote: > On 2017/2/24 6:58, Jaegeuk Kim wrote: > > @@ -2326,7 +2431,8 @@ void flush_nat_entries(struct f2fs_sb_info *sbi) > > * entries, remove all entries from journal and merge them > > * into nat entry set. > > */ > > - if (!__has_cursum_space(journal,

Re: [LKP] [usb] bea5b158ff WARNING: CPU: 0 PID: 25 at drivers/usb/core/urb.c:338 usb_submit_urb

On 02/28, Ye Xiaolong wrote: >On 02/27, Peter Chen wrote: >>On Sun, Feb 26, 2017 at 06:19:59PM +0800, Fengguang Wu wrote: >>> [Sorry, resend to correct Felipe's email address] >>> >>> Greetings, >>> >>> This debug patch possibly discloses some USB/I2C bugs. Since the USB >>> warning shows up

Re: [LKP] [usb] bea5b158ff WARNING: CPU: 0 PID: 25 at drivers/usb/core/urb.c:338 usb_submit_urb

On 02/28, Ye Xiaolong wrote: >On 02/27, Peter Chen wrote: >>On Sun, Feb 26, 2017 at 06:19:59PM +0800, Fengguang Wu wrote: >>> [Sorry, resend to correct Felipe's email address] >>> >>> Greetings, >>> >>> This debug patch possibly discloses some USB/I2C bugs. Since the USB >>> warning shows up

[PATCH] blkcg: allocate struct blkcg_gq outside request queue spinlock

blkg_conf_prep() currently calls blkg_lookup_create() while holding request queue spinlock. This means allocating memory for struct blkcg_gq has to be made non-blocking. This causes occasional -ENOMEM failures in call paths like below: pcpu_alloc+0x68f/0x710 __alloc_percpu_gfp+0xd/0x10

[PATCH] blkcg: allocate struct blkcg_gq outside request queue spinlock

blkg_conf_prep() currently calls blkg_lookup_create() while holding request queue spinlock. This means allocating memory for struct blkcg_gq has to be made non-blocking. This causes occasional -ENOMEM failures in call paths like below: pcpu_alloc+0x68f/0x710 __alloc_percpu_gfp+0xd/0x10

Re: [v2] Input: pwm-beeper: support customized freq for SND_BELL

On 02/27/2017 11:19 PM, Heiko Schocher wrote: Hello David, Am 27.02.2017 um 19:11 schrieb David Lechner: On 02/20/2017 02:37 AM, Heiko Schocher wrote: From: Guan Ben extend the pwm-beeper driver to support customized frequency for SND_BELL from device tree.

Re: [v2] Input: pwm-beeper: support customized freq for SND_BELL

On 02/27/2017 11:19 PM, Heiko Schocher wrote: Hello David, Am 27.02.2017 um 19:11 schrieb David Lechner: On 02/20/2017 02:37 AM, Heiko Schocher wrote: From: Guan Ben extend the pwm-beeper driver to support customized frequency for SND_BELL from device tree. Signed-off-by: Guan Ben

Re: [PATCH v2] Input: pwm-beeper: support customized freq for SND_BELL

Hello Rob, Am 27.02.2017 um 20:10 schrieb Rob Herring: On Mon, Feb 20, 2017 at 09:37:43AM +0100, Heiko Schocher wrote: From: Guan Ben extend the pwm-beeper driver to support customized frequency for SND_BELL from device tree. Signed-off-by: Guan Ben

Re: [PATCH v2] Input: pwm-beeper: support customized freq for SND_BELL

Hello Rob, Am 27.02.2017 um 20:10 schrieb Rob Herring: On Mon, Feb 20, 2017 at 09:37:43AM +0100, Heiko Schocher wrote: From: Guan Ben extend the pwm-beeper driver to support customized frequency for SND_BELL from device tree. Signed-off-by: Guan Ben Signed-off-by: Mark Jonas

Re: [PATCH v2 14/22] dt-bindings: PCI: dra7xx: Add dt bindings to enable legacy mode

On Monday 27 February 2017 10:10 PM, Rob Herring wrote: > On Fri, Feb 17, 2017 at 03:20:34PM +0530, Kishon Vijay Abraham I wrote: >> Update device tree binding documentation of TI's dra7xx PCI >> controller to include property for enabling legacy mode. >> >> Signed-off-by: Kishon Vijay Abraham I

Re: [v2] Input: pwm-beeper: support customized freq for SND_BELL

Hello David, Am 27.02.2017 um 19:11 schrieb David Lechner: On 02/20/2017 02:37 AM, Heiko Schocher wrote: From: Guan Ben extend the pwm-beeper driver to support customized frequency for SND_BELL from device tree. Signed-off-by: Guan Ben

Re: [v2] Input: pwm-beeper: support customized freq for SND_BELL

Hello David, Am 27.02.2017 um 19:11 schrieb David Lechner: On 02/20/2017 02:37 AM, Heiko Schocher wrote: From: Guan Ben extend the pwm-beeper driver to support customized frequency for SND_BELL from device tree. Signed-off-by: Guan Ben Signed-off-by: Mark Jonas [h...@denx.de: adapted to

Re: [PATCH v2 14/22] dt-bindings: PCI: dra7xx: Add dt bindings to enable legacy mode

On Monday 27 February 2017 10:10 PM, Rob Herring wrote: > On Fri, Feb 17, 2017 at 03:20:34PM +0530, Kishon Vijay Abraham I wrote: >> Update device tree binding documentation of TI's dra7xx PCI >> controller to include property for enabling legacy mode. >> >> Signed-off-by: Kishon Vijay Abraham I

Re: Ext4 new shutdown ioctl fails generic/04{4,5,6}

On Tue, Feb 28, 2017 at 11:25:56AM +0800, Xiong Zhou wrote: > > On latest Linus tree, xfstests generic/04{4,5,6} fails. Yes, that's known issue. generic/04[456] were originally XFS specific tests, and they have have assumptions about the implementation of the underlying file system. We have a

Re: Ext4 new shutdown ioctl fails generic/04{4,5,6}

On Tue, Feb 28, 2017 at 11:25:56AM +0800, Xiong Zhou wrote: > > On latest Linus tree, xfstests generic/04{4,5,6} fails. Yes, that's known issue. generic/04[456] were originally XFS specific tests, and they have have assumptions about the implementation of the underlying file system. We have a

[PATCH v6] staging: xgifb: correct the multiple line dereference

Error reported by checkpatch.pl as "avoid multiple line dereference". Addition of new variables to make the code more readable and also to correct about mentioned error as by itroducing new variables line is not exceeding 80 characters. Signed-off-by: Arushi Singhal

[PATCH v6] staging: xgifb: correct the multiple line dereference

Error reported by checkpatch.pl as "avoid multiple line dereference". Addition of new variables to make the code more readable and also to correct about mentioned error as by itroducing new variables line is not exceeding 80 characters. Signed-off-by: Arushi Singhal --- changes in v6 - changes

Re: [PATCH V5 5/6] mm: enable MADV_FREE for swapless system

On Fri, Feb 24, 2017 at 01:31:48PM -0800, Shaohua Li wrote: > Now MADV_FREE pages can be easily reclaimed even for swapless system. We > can safely enable MADV_FREE for all systems. > > Cc: Michal Hocko > Cc: Minchan Kim > Cc: Hugh Dickins

Re: [PATCH V5 5/6] mm: enable MADV_FREE for swapless system

On Fri, Feb 24, 2017 at 01:31:48PM -0800, Shaohua Li wrote: > Now MADV_FREE pages can be easily reclaimed even for swapless system. We > can safely enable MADV_FREE for all systems. > > Cc: Michal Hocko > Cc: Minchan Kim > Cc: Hugh Dickins > Cc: Rik van Riel > Cc: Mel Gorman > Cc: Andrew

[PATCH v5 5/5] staging: ks7010: fix coding style issue of aligning comments properly

This patch fixes coding style issue of having block comments using a trailing */ on a separate line, warning as issued by checkpatch Signed-off-by: Chetan Sethi --- v2: - split multiple changes across different patches v3: - mentioned patch revision in subject v4: -

Re: [PATCH] jump_label: align jump_entry table to at least 4-bytes

972 Comm: modprobe Not tainted 4.10.0-next-20170227 #4 [ 11.731930] task: c0077b284a00 task.stack: c0077b8b8000 [ 11.731933] NIP: c17bf84c LR: c17bfcbc CTR: [ 11.731937] REGS: c0077b8bb800 TRAP: 0700 Not tainted (4.10.0-next-20170227)

[PATCH v5 5/5] staging: ks7010: fix coding style issue of aligning comments properly

This patch fixes coding style issue of having block comments using a trailing */ on a separate line, warning as issued by checkpatch Signed-off-by: Chetan Sethi --- v2: - split multiple changes across different patches v3: - mentioned patch revision in subject v4: - modified description to

Re: [PATCH] jump_label: align jump_entry table to at least 4-bytes

972 Comm: modprobe Not tainted 4.10.0-next-20170227 #4 [ 11.731930] task: c0077b284a00 task.stack: c0077b8b8000 [ 11.731933] NIP: c17bf84c LR: c17bfcbc CTR: [ 11.731937] REGS: c0077b8bb800 TRAP: 0700 Not tainted (4.10.0-next-20170227)

Re: [LKP] [usb] bea5b158ff WARNING: CPU: 0 PID: 25 at drivers/usb/core/urb.c:338 usb_submit_urb

The dummy_udc WARN is gone with this patch for 100+ times of boot tests. Tested-by: Xiaolong Ye Thanks, Xiaolong Thanks, Xiaolong. I will submit a patch for it. Thank you Peter! We've been noised by this warning for quite some time. Fengguang

Re: [LKP] [usb] bea5b158ff WARNING: CPU: 0 PID: 25 at drivers/usb/core/urb.c:338 usb_submit_urb

The dummy_udc WARN is gone with this patch for 100+ times of boot tests. Tested-by: Xiaolong Ye Thanks, Xiaolong Thanks, Xiaolong. I will submit a patch for it. Thank you Peter! We've been noised by this warning for quite some time. Fengguang

[PATCH v5 1/5] staging: ks7010: fixed warning of avoiding line over 80 characters

This patch fixes warning of line over 80 characters, as issued by checkpatch.pl Signed-off-by: Chetan Sethi --- v2: - split multiple changes across different patches v3: - mentioned patch revision in subject v4: - modified description to exclude mention of patch number

[PATCH v5 1/5] staging: ks7010: fixed warning of avoiding line over 80 characters

This patch fixes warning of line over 80 characters, as issued by checkpatch.pl Signed-off-by: Chetan Sethi --- v2: - split multiple changes across different patches v3: - mentioned patch revision in subject v4: - modified description to exclude mention of patch number from changelog v5: -

Re: [LKP] [usb] bea5b158ff WARNING: CPU: 0 PID: 25 at drivers/usb/core/urb.c:338 usb_submit_urb

On Tue, Feb 28, 2017 at 12:32:55PM +0800, Ye Xiaolong wrote: > On 02/28, Ye Xiaolong wrote: > >On 02/27, Peter Chen wrote: > >>On Sun, Feb 26, 2017 at 06:19:59PM +0800, Fengguang Wu wrote: > >>> [Sorry, resend to correct Felipe's email address] > >>> > >>> Greetings, > >>> > >>> This debug patch

Re: [LKP] [usb] bea5b158ff WARNING: CPU: 0 PID: 25 at drivers/usb/core/urb.c:338 usb_submit_urb

On Tue, Feb 28, 2017 at 12:32:55PM +0800, Ye Xiaolong wrote: > On 02/28, Ye Xiaolong wrote: > >On 02/27, Peter Chen wrote: > >>On Sun, Feb 26, 2017 at 06:19:59PM +0800, Fengguang Wu wrote: > >>> [Sorry, resend to correct Felipe's email address] > >>> > >>> Greetings, > >>> > >>> This debug patch

[PATCH] i2c: copy device properties when using i2c_register_board_info()

This will allow marking device property lists as __initdata, the same as board info structures themselves. Signed-off-by: Dmitry Torokhov --- drivers/i2c/i2c-boardinfo.c | 7 +++ 1 file changed, 7 insertions(+) diff --git a/drivers/i2c/i2c-boardinfo.c

[PATCH] char: misc: minor code cleanup

Fix a couple of minor issues found by checkpatch.pl: Add/remove spaces where required. Move EXPORT_SYMBOL() to the end of the function it refers to. Set the access mode for the proc entry explicity. Use pr_warn() instead of printk() without loglevel. Signed-off-by: Martin Kaiser

[PATCH] i2c: copy device properties when using i2c_register_board_info()

This will allow marking device property lists as __initdata, the same as board info structures themselves. Signed-off-by: Dmitry Torokhov --- drivers/i2c/i2c-boardinfo.c | 7 +++ 1 file changed, 7 insertions(+) diff --git a/drivers/i2c/i2c-boardinfo.c b/drivers/i2c/i2c-boardinfo.c index

[PATCH] char: misc: minor code cleanup

Fix a couple of minor issues found by checkpatch.pl: Add/remove spaces where required. Move EXPORT_SYMBOL() to the end of the function it refers to. Set the access mode for the proc entry explicity. Use pr_warn() instead of printk() without loglevel. Signed-off-by: Martin Kaiser ---

[PATCH v5] staging: xgifb: correct the multiple line dereference

Error reported by checkpatch.pl as "avoid multiple line dereference". Addition of new variables to make the code more readable and also to correct about mentioned error as by itroducing new variables line is not exceeding 80 characters. Signed-off-by: Arushi Singhal

[PATCH v5] staging: xgifb: correct the multiple line dereference

Error reported by checkpatch.pl as "avoid multiple line dereference". Addition of new variables to make the code more readable and also to correct about mentioned error as by itroducing new variables line is not exceeding 80 characters. Signed-off-by: Arushi Singhal --- changes in v5 - changes

[PATCH v5 4/4] iio: accel: adxl345: Add SPI support

Add SPI driver that initializes SPI regmap for the adxl345 core driver. The driver supports the same functionality as I2C namely the x, y, z and scale readings. Signed-off-by: Eva Rachel Retuya Reviewed-by: Andy Shevchenko --- Changes from v4: *

[PATCH v5 4/4] iio: accel: adxl345: Add SPI support

Add SPI driver that initializes SPI regmap for the adxl345 core driver. The driver supports the same functionality as I2C namely the x, y, z and scale readings. Signed-off-by: Eva Rachel Retuya Reviewed-by: Andy Shevchenko --- Changes from v4: * Add Andy's Reviewed-by tag Changes from v3: *

[PATCH] serial: 8250_dw: Honor clk_round_rate errors in dw8250_set_termios

clk_round_rate returns a signed long and may possibly return errors in it, for example if there is no possible rate. Till now dw8250_set_termios ignored any error, the signednes and would just use the value as input to clk_set_rate. This of course falls apart if there is an actual error, so check

[PATCH] serial: 8250_dw: Honor clk_round_rate errors in dw8250_set_termios

clk_round_rate returns a signed long and may possibly return errors in it, for example if there is no possible rate. Till now dw8250_set_termios ignored any error, the signednes and would just use the value as input to clk_set_rate. This of course falls apart if there is an actual error, so check

Re: 289b7bfd48 BUG: KASAN: slab-out-of-bounds in of_device_uevent at addr ffff880012049289

On Tue, Feb 28, 2017 at 12:24:03PM +0800, Fengguang Wu wrote: Hi Linus Walleij, I'm not sure if this is a good bisect since the merged gpio branch suffers from another early hang problem which could hide the KASAN BUG. So also OF people are also included in the loop. The attached reproduce-*

Re: 289b7bfd48 BUG: KASAN: slab-out-of-bounds in of_device_uevent at addr ffff880012049289

On Tue, Feb 28, 2017 at 12:24:03PM +0800, Fengguang Wu wrote: Hi Linus Walleij, I'm not sure if this is a good bisect since the merged gpio branch suffers from another early hang problem which could hide the KASAN BUG. So also OF people are also included in the loop. The attached reproduce-*

[PATCH] objtool: enclose contents of unreachable() macro in a block

Guenter Roeck reported a boot failure in mips64. It was bisected to the following commit: d1091c7fa3d5 ("objtool: Improve detection of BUG() and other dead ends") The unreachable() macro was formerly only composed of a single statement. The above commit added a second statement, but

Re: CPU: 0 PID: 0 at arch/x86/kernel/apic/apic.c:2066

Hi Marco, After Linux-4.9, we also mapped the logical CPU IDs for the disabled CPUs. The reason of the warning maybe that: The max number of the CPU in "dl360g5" is 2 (NR_CPUS:2), but, the kernel mapped one of the number to a disabled CPUs, so one of the enable CPUs will never have a cpu_id,

[PATCH] objtool: enclose contents of unreachable() macro in a block

Guenter Roeck reported a boot failure in mips64. It was bisected to the following commit: d1091c7fa3d5 ("objtool: Improve detection of BUG() and other dead ends") The unreachable() macro was formerly only composed of a single statement. The above commit added a second statement, but

Re: CPU: 0 PID: 0 at arch/x86/kernel/apic/apic.c:2066

Hi Marco, After Linux-4.9, we also mapped the logical CPU IDs for the disabled CPUs. The reason of the warning maybe that: The max number of the CPU in "dl360g5" is 2 (NR_CPUS:2), but, the kernel mapped one of the number to a disabled CPUs, so one of the enable CPUs will never have a cpu_id,

Re: [PATCH] mmc: meson-gx: fix error path when driver initialization fails before enabling clocks

Michał Zegan writes: > This patch fixes the case where meson_mmc_probe function fails before > core_clk is enabled. > Originally, that would result in a try to disable the core clock, and if > it was not already enabled, it would result in a kernel warning. > This issue is

Re: [PATCH] mmc: meson-gx: fix error path when driver initialization fails before enabling clocks

Michał Zegan writes: > This patch fixes the case where meson_mmc_probe function fails before > core_clk is enabled. > Originally, that would result in a try to disable the core clock, and if > it was not already enabled, it would result in a kernel warning. > This issue is similar to the one

[PATCH v2 1/3] spi: allow attaching device properties to SPI board info

Generic device properties support statically defined property sets. For them to be usable, we need to attach these property sets before devices are registered and probed. Allowing to attach property list to spi_board_info structure will allow non-ACPI non-DT boards switch to using generic

[PATCH v2 0/3] Allow specifying properties with spi_register_board_info

I am trying to convert some input drivers to use only generic device properties, and get rid of legacy platform data. For that I need to be able to attach property lists to devices before they are registered, and quite a few boards use spi_register_board_info() to create their devices. v2: change

[PATCH v2 1/3] spi: allow attaching device properties to SPI board info

Generic device properties support statically defined property sets. For them to be usable, we need to attach these property sets before devices are registered and probed. Allowing to attach property list to spi_board_info structure will allow non-ACPI non-DT boards switch to using generic

[PATCH v2 0/3] Allow specifying properties with spi_register_board_info

I am trying to convert some input drivers to use only generic device properties, and get rid of legacy platform data. For that I need to be able to attach property lists to devices before they are registered, and quite a few boards use spi_register_board_info() to create their devices. v2: change

[PATCH v2 2/3] spi: allocate spi_board_info entries one by one

Lists of spi_board_info entries registered with spi_register_board_info() can be quite long; instead of forcing memory allocator find contagious chunk of memory, let;s allocate them one-by-one, so they can be packed as needed. Signed-off-by: Dmitry Torokhov ---

[PATCH v2 3/3] spi: allow registering empty spi_board_info lists

Many boards form list of spi_board_info entries depending on config, and it is possible to end up with empty list. Do not report error in such cases. Signed-off-by: Dmitry Torokhov --- drivers/spi/spi.c | 3 --- 1 file changed, 3 deletions(-) diff --git

[PATCH v2 2/3] spi: allocate spi_board_info entries one by one

Lists of spi_board_info entries registered with spi_register_board_info() can be quite long; instead of forcing memory allocator find contagious chunk of memory, let;s allocate them one-by-one, so they can be packed as needed. Signed-off-by: Dmitry Torokhov --- drivers/spi/spi.c | 12

[PATCH v2 3/3] spi: allow registering empty spi_board_info lists

Many boards form list of spi_board_info entries depending on config, and it is possible to end up with empty list. Do not report error in such cases. Signed-off-by: Dmitry Torokhov --- drivers/spi/spi.c | 3 --- 1 file changed, 3 deletions(-) diff --git a/drivers/spi/spi.c b/drivers/spi/spi.c

[PATCH 2/3] spi: allocate spi_board_info entries one by one

Lists of spi_board_info entries registered with spi_register_board_info() can be quite long; instead of forcing memory allocator find contagious chunk of memory, let;s allocate them one-by-one, so they can be packed as needed. Signed-off-by: Dmitry Torokhov ---

[PATCH 2/3] spi: allocate spi_board_info entries one by one

Lists of spi_board_info entries registered with spi_register_board_info() can be quite long; instead of forcing memory allocator find contagious chunk of memory, let;s allocate them one-by-one, so they can be packed as needed. Signed-off-by: Dmitry Torokhov --- drivers/spi/spi.c | 11

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