Re: [PATCH v2 3/3] DT: leds: Add Qualcomm Light Pulse Generator binding

On 07/17/2017 06:44 AM, Bjorn Andersson wrote: > On Sun 16 Jul 11:49 PDT 2017, Jacek Anaszewski wrote: >> On 07/15/2017 12:45 AM, Bjorn Andersson wrote: >>> diff --git a/Documentation/devicetree/bindings/leds/leds-qcom-lpg.txt >>> b/Documentation/devicetree/bindings/leds/leds-qcom-lpg.txt >>> new

Re: [PATCH v2 3/3] DT: leds: Add Qualcomm Light Pulse Generator binding

On 07/17/2017 06:44 AM, Bjorn Andersson wrote: > On Sun 16 Jul 11:49 PDT 2017, Jacek Anaszewski wrote: >> On 07/15/2017 12:45 AM, Bjorn Andersson wrote: >>> diff --git a/Documentation/devicetree/bindings/leds/leds-qcom-lpg.txt >>> b/Documentation/devicetree/bindings/leds/leds-qcom-lpg.txt >>> new

[patch v2 2/3] staging: speakup: use tty_kopen instead of tty_open_by_driver

This patch replaces call to tty_open_by_driver with a tty_kopen. Signed-off-by: Okash Khawaja --- drivers/staging/speakup/spk_ttyio.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- a/drivers/staging/speakup/spk_ttyio.c +++

[patch v2 2/3] staging: speakup: use tty_kopen instead of tty_open_by_driver

This patch replaces call to tty_open_by_driver with a tty_kopen. Signed-off-by: Okash Khawaja --- drivers/staging/speakup/spk_ttyio.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- a/drivers/staging/speakup/spk_ttyio.c +++ b/drivers/staging/speakup/spk_ttyio.c @@ -158,7 +158,7

[patch v2 1/3] tty: resolve tty contention between kernel and user space

The commit 12e84c71b7d4ee (tty: export tty_open_by_driver) exports tty_open_by_device to allow tty to be opened from inside kernel which works fine except that it doesn't handle contention with user space or another kernel-space open of the same tty. For example, opening a tty from user space

[patch v2 1/3] tty: resolve tty contention between kernel and user space

The commit 12e84c71b7d4ee (tty: export tty_open_by_driver) exports tty_open_by_device to allow tty to be opened from inside kernel which works fine except that it doesn't handle contention with user space or another kernel-space open of the same tty. For example, opening a tty from user space

[patch v2 0/3] tty contention resulting from tty_open_by_driver export

Hi, I have reworked the previous patch set. These are the changes: 1. Patch 1 fixes tty->count mismatch reported by check_tty_count when a tty is kopened. 2. Patch 1 incorporates patch 4 in the previous patch set - it returns -ENODEV when tty is not configured. Thanks, Okash

[patch v2 0/3] tty contention resulting from tty_open_by_driver export

Hi, I have reworked the previous patch set. These are the changes: 1. Patch 1 fixes tty->count mismatch reported by check_tty_count when a tty is kopened. 2. Patch 1 incorporates patch 4 in the previous patch set - it returns -ENODEV when tty is not configured. Thanks, Okash

[patch v2 3/3] tty: undo export of tty_open_by_driver

Since we have tty_kopen, we no longer need to export tty_open_by_driver. This patch makes this function static. Signed-off-by: Okash Khawaja --- drivers/tty/tty_io.c |3 +-- include/linux/tty.h |5 - 2 files changed, 1 insertion(+), 7 deletions(-) ---

[patch v2 3/3] tty: undo export of tty_open_by_driver

Since we have tty_kopen, we no longer need to export tty_open_by_driver. This patch makes this function static. Signed-off-by: Okash Khawaja --- drivers/tty/tty_io.c |3 +-- include/linux/tty.h |5 - 2 files changed, 1 insertion(+), 7 deletions(-) --- a/drivers/tty/tty_io.c +++

Re: [PATCH] Documentation: dt: chosen property for kaslr-seed

On Mon, Jul 17, 2017 at 3:22 PM, Ard Biesheuvel wrote: > On 17 July 2017 at 20:54, Kees Cook wrote: >> On Mon, Jul 17, 2017 at 12:32 PM, Rob Herring wrote: >>> On Fri, Jul 14, 2017 at 05:38:36PM -0700, Kees Cook wrote:

Re: [PATCH] Documentation: dt: chosen property for kaslr-seed

On Mon, Jul 17, 2017 at 3:22 PM, Ard Biesheuvel wrote: > On 17 July 2017 at 20:54, Kees Cook wrote: >> On Mon, Jul 17, 2017 at 12:32 PM, Rob Herring wrote: >>> On Fri, Jul 14, 2017 at 05:38:36PM -0700, Kees Cook wrote: Document then /chosen/kaslr-seed property (and its interaction with the

Re: [RESEND RFC PATCH] ARM: dts: stm32: change pinctrl bindings definition

Hi Alex, On 07/17/2017 09:23 AM, Alexandre Torgue wrote: > From: Alexandre TORGUE > > Initially each pin was declared in "include/dt-bindings/stm32f429-pinfunc.h" > and each definition contained SOC names (ex: STM32F429_PA9_FUNC_USART1_TX). > Since this approach was

Re: [RESEND RFC PATCH] ARM: dts: stm32: change pinctrl bindings definition

Hi Alex, On 07/17/2017 09:23 AM, Alexandre Torgue wrote: > From: Alexandre TORGUE > > Initially each pin was declared in "include/dt-bindings/stm32f429-pinfunc.h" > and each definition contained SOC names (ex: STM32F429_PA9_FUNC_USART1_TX). > Since this approach was approved, the number of

Re: [PATCH net-next 11/12] net: dsa: mv88e6xxx: add Energy Detect ops

On Mon, Jul 17, 2017 at 01:45:49PM -0700, David Miller wrote: > From: Vivien Didelot > Date: Mon, 17 Jul 2017 15:32:52 -0400 > > > Hi Andrew, > > > > Andrew Lunn writes: > > > >> I never liked this. I think it is architecturally wrong for

Re: [PATCH net-next 11/12] net: dsa: mv88e6xxx: add Energy Detect ops

On Mon, Jul 17, 2017 at 01:45:49PM -0700, David Miller wrote: > From: Vivien Didelot > Date: Mon, 17 Jul 2017 15:32:52 -0400 > > > Hi Andrew, > > > > Andrew Lunn writes: > > > >> I never liked this. I think it is architecturally wrong for the switch > >> to be poking around in the PHY. It

Re: [PATCH v2] PM / suspend: Add suspend_target_state()

On Mon, Jul 17, 2017 at 10:16 PM, Pavel Machek wrote: > Hi! > >> Have the core suspend/resume framework store the system-wide suspend >> state (suspend_state_t) we are about to enter, and expose it to drivers >> via suspend_target_state() in order to retrieve that. The state is >>

Re: [PATCH v2] PM / suspend: Add suspend_target_state()

On Mon, Jul 17, 2017 at 10:16 PM, Pavel Machek wrote: > Hi! > >> Have the core suspend/resume framework store the system-wide suspend >> state (suspend_state_t) we are about to enter, and expose it to drivers >> via suspend_target_state() in order to retrieve that. The state is >> assigned in

[PATCH 2/7] docs: Do not include kerneldoc comments from kernel/sys.c

...because there are none there, and I cannot figure out what would ever have been of interest there. This eliminates this warning: ./kernel/sys.c:1: warning: no structured comments found from the build. Signed-off-by: Jonathan Corbet ---

[PATCH 2/7] docs: Do not include kerneldoc comments from kernel/sys.c

...because there are none there, and I cannot figure out what would ever have been of interest there. This eliminates this warning: ./kernel/sys.c:1: warning: no structured comments found from the build. Signed-off-by: Jonathan Corbet --- Documentation/driver-api/basics.rst | 3 --- 1

[PATCH 1/7] docs: Get module_init() docs from module.h

The docs build complains: ./include/linux/init.h:1: warning: no structured comments found The problem is that the comments in question were moved to module.h in commit 0fd972a7d91d (module: relocate module_init from init.h to module.h). Fix basics.rst to match. Signed-off-by: Jonathan

[PATCH 1/7] docs: Get module_init() docs from module.h

The docs build complains: ./include/linux/init.h:1: warning: no structured comments found The problem is that the comments in question were moved to module.h in commit 0fd972a7d91d (module: relocate module_init from init.h to module.h). Fix basics.rst to match. Signed-off-by: Jonathan

[PATCH 7/7] docs: Use :internal: for include/drm/drm_syncobj.h

Documentation/gpu/drm-mm.rst includes from include/drm/drm_syncobj.h with :export:, but this is a header file without export directives. That results in this warning: ./include/drm/drm_syncobj.h:1: warning: no structured comments found ...and a failure to obtain the documentation from that

[PATCH 7/7] docs: Use :internal: for include/drm/drm_syncobj.h

Documentation/gpu/drm-mm.rst includes from include/drm/drm_syncobj.h with :export:, but this is a header file without export directives. That results in this warning: ./include/drm/drm_syncobj.h:1: warning: no structured comments found ...and a failure to obtain the documentation from that

[PATCH 6/7] docs: Do not include from include/drm/drm_color_mgmt.h

Commit 8f2e045ec878 (drm/color: un-inline drm_color_lut_extract()) moved the only kerneldoc comment out of include/drm/drm_color_mgmt.h, leading to this warning: ./include/drm/drm_color_mgmt.h:1: warning: no structured comments found That comment is already picked up in drm_color_mgmt.c, so

[PATCH 4/7] docs: Get the struct cmbdata kernel doc from the right file

Back in 2012, commit 9807f75955ea (UAPI: (Scripted) Disintegrate arch/s390/include/asm) moved struct cmbdata (and its kerneldoc comments) to another file, but did not update the docs to match. The result is this warning: ./arch/s390/include/asm/cmb.h:1: warning: no structured comments found

[PATCH 6/7] docs: Do not include from include/drm/drm_color_mgmt.h

Commit 8f2e045ec878 (drm/color: un-inline drm_color_lut_extract()) moved the only kerneldoc comment out of include/drm/drm_color_mgmt.h, leading to this warning: ./include/drm/drm_color_mgmt.h:1: warning: no structured comments found That comment is already picked up in drm_color_mgmt.c, so

[PATCH 4/7] docs: Get the struct cmbdata kernel doc from the right file

Back in 2012, commit 9807f75955ea (UAPI: (Scripted) Disintegrate arch/s390/include/asm) moved struct cmbdata (and its kerneldoc comments) to another file, but did not update the docs to match. The result is this warning: ./arch/s390/include/asm/cmb.h:1: warning: no structured comments found

[PATCH 0/7] Documentation warning reduction

I've come to the conclusion that we really need to make the docs build quieter. Here's a small step in that direction: getting rid of all of the "no structured comments found" warnings. Such warnings are usually the result of kerneldoc comments being moved elsewhere, so this took a bit of git

[PATCH 0/7] Documentation warning reduction

I've come to the conclusion that we really need to make the docs build quieter. Here's a small step in that direction: getting rid of all of the "no structured comments found" warnings. Such warnings are usually the result of kerneldoc comments being moved elsewhere, so this took a bit of git

[PATCH 3/7] docs: Do not include from .../seqno-fence.c

There are no kerneldoc comments in drivers/dma-buf/seqno-fence.c, and it appears there never have been. Stop looking for comments there to eliminate this warning: ./drivers/dma-buf/seqno-fence.c:1: warning: no structured comments found Signed-off-by: Jonathan Corbet ---

[PATCH 5/7] docs: Do not include from drivers/scsi/constants.c

The only function of interest in that file was scsi_print_status(). That function was removed in commit 7ac7076344d9 (scsi: remove scsi_print_status()) but the docs were not changed to match, yielding this warning: ./drivers/scsi/constants.c:1: warning: no structured comments found There's

[PATCH 3/7] docs: Do not include from .../seqno-fence.c

There are no kerneldoc comments in drivers/dma-buf/seqno-fence.c, and it appears there never have been. Stop looking for comments there to eliminate this warning: ./drivers/dma-buf/seqno-fence.c:1: warning: no structured comments found Signed-off-by: Jonathan Corbet ---

[PATCH 5/7] docs: Do not include from drivers/scsi/constants.c

The only function of interest in that file was scsi_print_status(). That function was removed in commit 7ac7076344d9 (scsi: remove scsi_print_status()) but the docs were not changed to match, yielding this warning: ./drivers/scsi/constants.c:1: warning: no structured comments found There's

Re: [Intel-gfx] [PATCH] drm/i915: Return correct EDP voltage swing table for 0.85V

On Mon, 2017-07-17 at 18:55 +, Pandiyan, Dhinakaran wrote: > Looks like a typo in > > cf54ca8 ("drm/i915/cnl: Implement voltage swing sequence.") > > but Cc'ing Rodrigo, Clint to make sure this wasn't a workaround. > > -DK Checked with Clint, this wasn't a workaround, a typo indeed.

Re: [Intel-gfx] [PATCH] drm/i915: Return correct EDP voltage swing table for 0.85V

On Mon, 2017-07-17 at 18:55 +, Pandiyan, Dhinakaran wrote: > Looks like a typo in > > cf54ca8 ("drm/i915/cnl: Implement voltage swing sequence.") > > but Cc'ing Rodrigo, Clint to make sure this wasn't a workaround. > > -DK Checked with Clint, this wasn't a workaround, a typo indeed.

[GIT] Sparc

Please pull to get these two sparc fixes: 1) Fix DMA regression in 4.13 merge window, only certain chips can do 64-bit DMA. From Dave Dushar. 2) Correct cpu cross-call algorithm to correctly detect stalled or stuck remote cpus, from Jane Chu. Thanks! The following changes since commit

[GIT] Sparc

Please pull to get these two sparc fixes: 1) Fix DMA regression in 4.13 merge window, only certain chips can do 64-bit DMA. From Dave Dushar. 2) Correct cpu cross-call algorithm to correctly detect stalled or stuck remote cpus, from Jane Chu. Thanks! The following changes since commit

Re: [PATCH 1/6] genirq: generic chip: add generic irq_mask_ack functions

On Mon, 17 Jul 2017, Doug Berger wrote: > Seeing as Mans has acked the change to his driver should I submit a V2 > with just the function he and I are using and remove the other five > permutations, or are you willing to move forward with the patch as is? Please resubmit with the implementation

Re: [PATCH 1/6] genirq: generic chip: add generic irq_mask_ack functions

On Mon, 17 Jul 2017, Doug Berger wrote: > Seeing as Mans has acked the change to his driver should I submit a V2 > with just the function he and I are using and remove the other five > permutations, or are you willing to move forward with the patch as is? Please resubmit with the implementation

Re: [PATCH 5/6] cgroup: implement cgroup v2 thread support

On 07/17/2017 10:14 AM, Peter Zijlstra wrote: > On Sun, Jul 16, 2017 at 10:07:20PM -0400, Tejun Heo wrote: >> v4: - Updated to marking each cgroup threaded as suggested by PeterZ. >> >> +On creation, a cgroup is always a domain cgroup and can be made >> +threaded by writing "threaded" to the

Re: [PATCH 5/6] cgroup: implement cgroup v2 thread support

On 07/17/2017 10:14 AM, Peter Zijlstra wrote: > On Sun, Jul 16, 2017 at 10:07:20PM -0400, Tejun Heo wrote: >> v4: - Updated to marking each cgroup threaded as suggested by PeterZ. >> >> +On creation, a cgroup is always a domain cgroup and can be made >> +threaded by writing "threaded" to the

Re: [PATCH 1/2] iio: Documentation: Add missing documentation for power attribute

On Mon, 17 Jul 2017 01:34:09 +0200 Stefan Brüns wrote: > Commit c43a102e67db ("iio: ina2xx: add support for TI INA2xx Power Monitors") > introduced the in_powerY_raw attribute, but omitted the corresponding > documentation. > > The description is correct for the

Re: [PATCH 1/2] iio: Documentation: Add missing documentation for power attribute

On Mon, 17 Jul 2017 01:34:09 +0200 Stefan Brüns wrote: > Commit c43a102e67db ("iio: ina2xx: add support for TI INA2xx Power Monitors") > introduced the in_powerY_raw attribute, but omitted the corresponding > documentation. > > The description is correct for the INA2xx and the MAX9611 IIO

Re: [PATCH 2/2] iio: Documentation: Add ina2xx shunt_resistor attribute documentation

On Mon, 17 Jul 2017 01:34:10 +0200 Stefan Brüns wrote: > The ina2xx driver appeared in the Linux kernel version 4.5, but provided > no documentation. Contrary to other uses of resistance in IIO, ina2xx uses > microohms instead of ohms in the sysfs attribute. > >

Re: [PATCH 2/2] iio: Documentation: Add ina2xx shunt_resistor attribute documentation

On Mon, 17 Jul 2017 01:34:10 +0200 Stefan Brüns wrote: > The ina2xx driver appeared in the Linux kernel version 4.5, but provided > no documentation. Contrary to other uses of resistance in IIO, ina2xx uses > microohms instead of ohms in the sysfs attribute. > > Signed-off-by: Stefan Brüns

[PATCH] Stagung: rtl8188eu: core: fixd comment coding style issue in rtw_xmit.c

From: Armin Schoenlieb This is a patch to the rtw_xmit.c file that fixes up a comment/80 character warning found by the checkpatch.pl tool Signed-off-by: Armin Schoenlieb --- drivers/staging/rtl8188eu/core/rtw_xmit.c | 6 -- 1 file changed, 4

[PATCH] Stagung: rtl8188eu: core: fixd comment coding style issue in rtw_xmit.c

From: Armin Schoenlieb This is a patch to the rtw_xmit.c file that fixes up a comment/80 character warning found by the checkpatch.pl tool Signed-off-by: Armin Schoenlieb --- drivers/staging/rtl8188eu/core/rtw_xmit.c | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git

Re: [PATCH v2] xattr: Enable security.capability in user namespaces

On 07/17/2017 02:58 PM, Vivek Goyal wrote: On Tue, Jul 11, 2017 at 11:05:11AM -0400, Stefan Berger wrote: [..] +/* + * xattr_list_userns_rewrite - Rewrite list of xattr names for user namespaces + * or determine needed size for attribute list + *

Re: [PATCH v2] xattr: Enable security.capability in user namespaces

On 07/17/2017 02:58 PM, Vivek Goyal wrote: On Tue, Jul 11, 2017 at 11:05:11AM -0400, Stefan Berger wrote: [..] +/* + * xattr_list_userns_rewrite - Rewrite list of xattr names for user namespaces + * or determine needed size for attribute list + *

Re: [PATCH 2/1] docs: disable KASLR when debugging kernel

On Fri, 7 Jul 2017 15:11:46 +0800 Zhouyi Zhou wrote: > commit 6807c84652b0 ("x86: Enable KASLR by default") enables KASLR > by default on x86. While KASLR will confuse gdb which resolve kernel > symbol address from symbol table of vmlinux. We should turn off KASLR for >

Re: [PATCH 2/1] docs: disable KASLR when debugging kernel

On Fri, 7 Jul 2017 15:11:46 +0800 Zhouyi Zhou wrote: > commit 6807c84652b0 ("x86: Enable KASLR by default") enables KASLR > by default on x86. While KASLR will confuse gdb which resolve kernel > symbol address from symbol table of vmlinux. We should turn off KASLR for > kernel debugging.

Re: [PATCH v2] KVM: arm/arm64: Handle hva aging while destroying the vm

On 17.07.17 20:23, Christoffer Dall wrote: On Mon, Jul 17, 2017 at 05:16:17PM +0200, Andrea Arcangeli wrote: On Mon, Jul 17, 2017 at 04:45:10PM +0200, Christoffer Dall wrote: I would also very much like to get to the bottom of this, and at the very least try to get a valid explanation as to

Re: [PATCH v2] KVM: arm/arm64: Handle hva aging while destroying the vm

On 17.07.17 20:23, Christoffer Dall wrote: On Mon, Jul 17, 2017 at 05:16:17PM +0200, Andrea Arcangeli wrote: On Mon, Jul 17, 2017 at 04:45:10PM +0200, Christoffer Dall wrote: I would also very much like to get to the bottom of this, and at the very least try to get a valid explanation as to

Re: [PATCH] mtd: spear_smi: add NULL check on devm_kzalloc() return value

Le Thu, 6 Jul 2017 17:25:50 -0500, "Gustavo A. R. Silva" a écrit : > Check return value from call to devm_kzalloc() > in order to prevent a NULL pointer dereference. > > This issue was detected using Coccinelle and the following semantic patch: > > @@ > expression x; >

Re: [PATCH] mtd: spear_smi: add NULL check on devm_kzalloc() return value

Le Thu, 6 Jul 2017 17:25:50 -0500, "Gustavo A. R. Silva" a écrit : > Check return value from call to devm_kzalloc() > in order to prevent a NULL pointer dereference. > > This issue was detected using Coccinelle and the following semantic patch: > > @@ > expression x; > identifier fld; > @@ >

Re: [PATCH] mtd: nand: vf610_nfc: add NULL check on of_match_device() return value

On 07/17/2017 10:46 PM, Boris Brezillon wrote: > Le Fri, 7 Jul 2017 01:59:26 -0500, > "Gustavo A. R. Silva" a écrit : > >> Check return value from call to of_match_device() >> in order to prevent a NULL pointer dereference. >> >> In case of NULL print error message and

Re: [PATCH] mtd: nand: vf610_nfc: add NULL check on of_match_device() return value

On 07/17/2017 10:46 PM, Boris Brezillon wrote: > Le Fri, 7 Jul 2017 01:59:26 -0500, > "Gustavo A. R. Silva" a écrit : > >> Check return value from call to of_match_device() >> in order to prevent a NULL pointer dereference. >> >> In case of NULL print error message and return -ENODEV >> >>

[tip:timers/urgent] clocksource/drivers/timer-of: Handle of_irq_get_byname() result correctly

Commit-ID: 32f2fea6e77e64cd4045ec2d5deb879aada3b476 Gitweb: http://git.kernel.org/tip/32f2fea6e77e64cd4045ec2d5deb879aada3b476 Author: Sergei Shtylyov AuthorDate: Mon, 17 Jul 2017 21:00:44 +0300 Committer: Thomas Gleixner

[tip:timers/urgent] clocksource/drivers/timer-of: Handle of_irq_get_byname() result correctly

Commit-ID: 32f2fea6e77e64cd4045ec2d5deb879aada3b476 Gitweb: http://git.kernel.org/tip/32f2fea6e77e64cd4045ec2d5deb879aada3b476 Author: Sergei Shtylyov AuthorDate: Mon, 17 Jul 2017 21:00:44 +0300 Committer: Thomas Gleixner CommitDate: Mon, 17 Jul 2017 22:43:00 +0200

Re: [PATCH] mtd: nand: vf610_nfc: add NULL check on of_match_device() return value

Le Fri, 7 Jul 2017 01:59:26 -0500, "Gustavo A. R. Silva" a écrit : > Check return value from call to of_match_device() > in order to prevent a NULL pointer dereference. > > In case of NULL print error message and return -ENODEV > > Signed-off-by: Gustavo A. R. Silva

Re: [PATCH] mtd: nand: vf610_nfc: add NULL check on of_match_device() return value

Le Fri, 7 Jul 2017 01:59:26 -0500, "Gustavo A. R. Silva" a écrit : > Check return value from call to of_match_device() > in order to prevent a NULL pointer dereference. > > In case of NULL print error message and return -ENODEV > > Signed-off-by: Gustavo A. R. Silva > --- >

Re: [PATCH V3 2/2] mfd: Add ROHM BD9571MWV-M MFD PMIC driver

On 07/10/2017 05:33 PM, Geert Uytterhoeven wrote: > Hi Marek, > > On Tue, May 2, 2017 at 2:18 PM, Marek Vasut wrote: >> Add the MFD part of the ROHM BD9571MWV-M PMIC driver and MAINTAINERS >> entry. The MFD part only specifies the regmap bits for the PMIC and >> binds the

Re: [PATCH V3 2/2] mfd: Add ROHM BD9571MWV-M MFD PMIC driver

On 07/10/2017 05:33 PM, Geert Uytterhoeven wrote: > Hi Marek, > > On Tue, May 2, 2017 at 2:18 PM, Marek Vasut wrote: >> Add the MFD part of the ROHM BD9571MWV-M PMIC driver and MAINTAINERS >> entry. The MFD part only specifies the regmap bits for the PMIC and >> binds the subdevs together. >> >>

[PATCH V4 2/2] mfd: Add ROHM BD9571MWV-M MFD PMIC driver

Add the MFD part of the ROHM BD9571MWV-M PMIC driver and MAINTAINERS entry. The MFD part only specifies the regmap bits for the PMIC and binds the subdevs together. Signed-off-by: Marek Vasut Cc: linux-kernel@vger.kernel.org Cc: Geert Uytterhoeven

[PATCH V4 2/2] mfd: Add ROHM BD9571MWV-M MFD PMIC driver

Add the MFD part of the ROHM BD9571MWV-M PMIC driver and MAINTAINERS entry. The MFD part only specifies the regmap bits for the PMIC and binds the subdevs together. Signed-off-by: Marek Vasut Cc: linux-kernel@vger.kernel.org Cc: Geert Uytterhoeven Cc: Lee Jones --- V2: - Change

Re: [PATCH net-next 11/12] net: dsa: mv88e6xxx: add Energy Detect ops

From: Vivien Didelot Date: Mon, 17 Jul 2017 15:32:52 -0400 > Hi Andrew, > > Andrew Lunn writes: > >> I never liked this. I think it is architecturally wrong for the switch >> to be poking around in the PHY. It should ask the PHY driver.

Re: [PATCH net-next 11/12] net: dsa: mv88e6xxx: add Energy Detect ops

From: Vivien Didelot Date: Mon, 17 Jul 2017 15:32:52 -0400 > Hi Andrew, > > Andrew Lunn writes: > >> I never liked this. I think it is architecturally wrong for the switch >> to be poking around in the PHY. It should ask the PHY driver. This is >> especially true for external PHYs which might

Re: [PATCH 09/11] iio: orientation: hid-sensor-rotation: Drop unnecessary static

On Sat, 15 Jul 2017 22:07:44 +0200 Julia Lawall wrote: > Drop static on a local variable, when the variable is initialized before > any possible use. Thus, the static has no benefit. > > The semantic patch that fixes this problem is as follows: >

Re: [PATCH 09/11] iio: orientation: hid-sensor-rotation: Drop unnecessary static

On Sat, 15 Jul 2017 22:07:44 +0200 Julia Lawall wrote: > Drop static on a local variable, when the variable is initialized before > any possible use. Thus, the static has no benefit. > > The semantic patch that fixes this problem is as follows: > (http://coccinelle.lip6.fr/) > > // > @bad

Re: [PATCH] drm/rockchip: cdn-dp: send audio infoframe to sink

Hi, On Mon, Jul 17, 2017 at 1:23 PM, Sean Paul wrote: >> diff --git a/drivers/gpu/drm/rockchip/cdn-dp-core.c >> b/drivers/gpu/drm/rockchip/cdn-dp-core.c >> index 9b0b058..e59ca47 100644 >> --- a/drivers/gpu/drm/rockchip/cdn-dp-core.c >> +++

Re: [PATCH] drm/rockchip: cdn-dp: send audio infoframe to sink

Hi, On Mon, Jul 17, 2017 at 1:23 PM, Sean Paul wrote: >> diff --git a/drivers/gpu/drm/rockchip/cdn-dp-core.c >> b/drivers/gpu/drm/rockchip/cdn-dp-core.c >> index 9b0b058..e59ca47 100644 >> --- a/drivers/gpu/drm/rockchip/cdn-dp-core.c >> +++ b/drivers/gpu/drm/rockchip/cdn-dp-core.c >> @@ -802,6

Re: [ANNOUNCE] Git v2.14.0-rc0

Ævar Arnfjörð Bjarmason writes: > On Thu, Jul 13 2017, Junio C. Hamano jotted: > > Proposed improvements for the release notes (is this a good way to > propose RelNotes changes?) Thanks. You could also throw a patch just like any bugfix/update to documentation, I would think.

Re: [ANNOUNCE] Git v2.14.0-rc0

Ævar Arnfjörð Bjarmason writes: > On Thu, Jul 13 2017, Junio C. Hamano jotted: > > Proposed improvements for the release notes (is this a good way to > propose RelNotes changes?) Thanks. You could also throw a patch just like any bugfix/update to documentation, I would think. > I think this

[tip:irq/urgent] genirq/PM: Properly pretend disabled state when force resuming interrupts

Commit-ID: a696712c3dd54eb58d2c5a807b4aaa27782d80d6 Gitweb: http://git.kernel.org/tip/a696712c3dd54eb58d2c5a807b4aaa27782d80d6 Author: Juergen Gross AuthorDate: Mon, 17 Jul 2017 19:47:02 +0200 Committer: Thomas Gleixner CommitDate: Mon, 17 Jul 2017

[tip:irq/urgent] genirq/PM: Properly pretend disabled state when force resuming interrupts

Commit-ID: a696712c3dd54eb58d2c5a807b4aaa27782d80d6 Gitweb: http://git.kernel.org/tip/a696712c3dd54eb58d2c5a807b4aaa27782d80d6 Author: Juergen Gross AuthorDate: Mon, 17 Jul 2017 19:47:02 +0200 Committer: Thomas Gleixner CommitDate: Mon, 17 Jul 2017 22:32:20 +0200 genirq/PM: Properly

Re: [PATCH 09/11] net: ec_bhf: constify pci_device_id.

From: Arvind Yadav Date: Mon, 17 Jul 2017 23:42:34 +0530 > pci_device_id are not supposed to change at runtime. All functions > working with pci_device_id provided by work with > const pci_device_id. So mark the non-const structs as const. > > File size before: >

Re: [PATCH 09/11] net: ec_bhf: constify pci_device_id.

From: Arvind Yadav Date: Mon, 17 Jul 2017 23:42:34 +0530 > pci_device_id are not supposed to change at runtime. All functions > working with pci_device_id provided by work with > const pci_device_id. So mark the non-const structs as const. > > File size before: >text data bss

Re: [PATCH 08/11] net: cadence: macb: constify pci_device_id.

From: Arvind Yadav Date: Mon, 17 Jul 2017 23:41:52 +0530 > pci_device_id are not supposed to change at runtime. All functions > working with pci_device_id provided by work with > const pci_device_id. So mark the non-const structs as const. > > File size before: >

Re: [PATCH 08/11] net: cadence: macb: constify pci_device_id.

From: Arvind Yadav Date: Mon, 17 Jul 2017 23:41:52 +0530 > pci_device_id are not supposed to change at runtime. All functions > working with pci_device_id provided by work with > const pci_device_id. So mark the non-const structs as const. > > File size before: >text data bss

Re: [rfc] superblock shrinker accumulating excessive deferred counts

On Mon, 17 Jul 2017, Dave Chinner wrote: > > This is a side effect of super_cache_count() returning the appropriate > > count but super_cache_scan() refusing to do anything about it and > > immediately terminating with SHRINK_STOP, mostly for GFP_NOFS allocations. > > Yup. Happens during

Re: [rfc] superblock shrinker accumulating excessive deferred counts

On Mon, 17 Jul 2017, Dave Chinner wrote: > > This is a side effect of super_cache_count() returning the appropriate > > count but super_cache_scan() refusing to do anything about it and > > immediately terminating with SHRINK_STOP, mostly for GFP_NOFS allocations. > > Yup. Happens during

Re: [PATCH] bluetooth/smp: ensure RNG is properly seeded before ECDH use

Hi Jason, > This protocol uses lots of complex cryptography that relies on securely > generated random numbers. Thus, it's important that the RNG is actually > seeded before use. Fortuantely, it appears we're always operating in > process context (there are many GFP_KERNEL allocations and other >

Re: [PATCH] bluetooth/smp: ensure RNG is properly seeded before ECDH use

Hi Jason, > This protocol uses lots of complex cryptography that relies on securely > generated random numbers. Thus, it's important that the RNG is actually > seeded before use. Fortuantely, it appears we're always operating in > process context (there are many GFP_KERNEL allocations and other >

Re: [PATCH v2 1/2] dt-bindings: sound: add bindings for TAS6424

On Mon, Jul 17, 2017 at 11:25:46AM -0500, Michael Stecklein wrote: > Add the bindings for the TAS6424 digital amplifier. > > Signed-off-by: Michael Stecklein > --- > .../devicetree/bindings/sound/ti,tas6424.txt | 31 > ++ > 1 file changed, 31

Re: [PATCH v2 1/2] dt-bindings: sound: add bindings for TAS6424

On Mon, Jul 17, 2017 at 11:25:46AM -0500, Michael Stecklein wrote: > Add the bindings for the TAS6424 digital amplifier. > > Signed-off-by: Michael Stecklein > --- > .../devicetree/bindings/sound/ti,tas6424.txt | 31 > ++ > 1 file changed, 31 insertions(+) > create

[GIT PULL] gcc-plugins updates for v4.13-rc2

Hi, Please pull these gcc-plugins changes for v4.13-rc2. Now that IPC and other trees have landed, it's sensible to pull the manual markings portion of randstruct. This is the rest of what was staged in -next for the gcc-plugins, and comes in three patches, largest first: - mark "easy" structs

[GIT PULL] gcc-plugins updates for v4.13-rc2

Hi, Please pull these gcc-plugins changes for v4.13-rc2. Now that IPC and other trees have landed, it's sensible to pull the manual markings portion of randstruct. This is the rest of what was staged in -next for the gcc-plugins, and comes in three patches, largest first: - mark "easy" structs

Re: [PATCH] drm/rockchip: cdn-dp: send audio infoframe to sink

On Sat, Jul 15, 2017 at 07:00:18PM +0800, Chris Zhong wrote: > Some DP/HDMI sink need to receive the audio infoframe to play sound, > especially some multi-channel AV receiver, they need the > channel_allocation from infoframe to config the speakers. Send the > audio infoframe via SDP will make

Re: [PATCH] drm/rockchip: cdn-dp: send audio infoframe to sink

On Sat, Jul 15, 2017 at 07:00:18PM +0800, Chris Zhong wrote: > Some DP/HDMI sink need to receive the audio infoframe to play sound, > especially some multi-channel AV receiver, they need the > channel_allocation from infoframe to config the speakers. Send the > audio infoframe via SDP will make

Re: [PATCH] Documentation: dt: chosen property for kaslr-seed

On 17 July 2017 at 20:54, Kees Cook wrote: > On Mon, Jul 17, 2017 at 12:32 PM, Rob Herring wrote: >> On Fri, Jul 14, 2017 at 05:38:36PM -0700, Kees Cook wrote: >>> Document then /chosen/kaslr-seed property (and its interaction with the >> >> s/then/the/ >>

Re: [PATCH] Documentation: dt: chosen property for kaslr-seed

On 17 July 2017 at 20:54, Kees Cook wrote: > On Mon, Jul 17, 2017 at 12:32 PM, Rob Herring wrote: >> On Fri, Jul 14, 2017 at 05:38:36PM -0700, Kees Cook wrote: >>> Document then /chosen/kaslr-seed property (and its interaction with the >> >> s/then/the/ >> >>> EFI_RNG_PROTOCOL API). >> >>

Re: [PATCH] HID: Add quirk for Lenovo Yoga 910 with ITE Chips

On Sat, 2017-07-15 at 22:05 +0200, Patrick wrote: > On Sat, Jul 15, 2017 at 07:58:10PM +0200, Bastien Nocera wrote: > > > > On Sat, 2017-07-15 at 19:52 +0200, Patrick Pedersen wrote: > > > > > > On Sat, Jul 15, 2017 at 4:29 PM, Bastien Nocera > > t> > > > wrote: > > > > > >

Re: [PATCH] HID: Add quirk for Lenovo Yoga 910 with ITE Chips

On Sat, 2017-07-15 at 22:05 +0200, Patrick wrote: > On Sat, Jul 15, 2017 at 07:58:10PM +0200, Bastien Nocera wrote: > > > > On Sat, 2017-07-15 at 19:52 +0200, Patrick Pedersen wrote: > > > > > > On Sat, Jul 15, 2017 at 4:29 PM, Bastien Nocera > > t> > > > wrote: > > > > > > > > On Sat,

Re: [PATCH] dt-bindings: regulator: pwm-regulator: fix example syntax

On Mon, Jul 17, 2017 at 03:18:23PM +0200, Martin Blumenstingl wrote: > The "Continuous Voltage" example specifies a pwm-dutycycle-range. > However, an equal sign is missing between the property name and value. > Fix this to allow copy and paste from the documentation when writing an > own .dts

Re: [PATCH] dt-bindings: regulator: pwm-regulator: fix example syntax

On Mon, Jul 17, 2017 at 03:18:23PM +0200, Martin Blumenstingl wrote: > The "Continuous Voltage" example specifies a pwm-dutycycle-range. > However, an equal sign is missing between the property name and value. > Fix this to allow copy and paste from the documentation when writing an > own .dts

Re: Help with trace-cmd/ftrace recording process ID information

On Mon, 17 Jul 2017 16:06:37 -0400 Will Hawkins wrote: > This seems to be the problem: > > On the "good" system, that file is up-to-date with cached PIDs and > comms. On the bad host, there are no cached entries from any of the > traces that I've run. > > Because these

Re: Help with trace-cmd/ftrace recording process ID information

On Mon, 17 Jul 2017 16:06:37 -0400 Will Hawkins wrote: > This seems to be the problem: > > On the "good" system, that file is up-to-date with cached PIDs and > comms. On the bad host, there are no cached entries from any of the > traces that I've run. > > Because these are running old

Re: [PATCH 6/7] dt-bindings: pci: qcom: Add support for IPQ8074

On Mon, Jul 17, 2017 at 05:34:02PM +0530, Varadarajan Narayanan wrote: > Add support for the IPQ8074 PCIe controller. IPQ8074 supports Gen 1/2, one > lane, two PCIe root complex with support for MSI and legacy interrupts, and > it conforms to PCI Express Base 2.1 specification. > >

Re: [PATCH 6/7] dt-bindings: pci: qcom: Add support for IPQ8074

On Mon, Jul 17, 2017 at 05:34:02PM +0530, Varadarajan Narayanan wrote: > Add support for the IPQ8074 PCIe controller. IPQ8074 supports Gen 1/2, one > lane, two PCIe root complex with support for MSI and legacy interrupts, and > it conforms to PCI Express Base 2.1 specification. > >

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