Re: linux-next: manual merge of the staging tree with the tip tree

On Wed, 2 Mar 2016, Stephen Rothwell wrote: > Hi Greg, > > Today's linux-next merge of the staging tree got a conflict in: > > include/linux/irqdomain.h > > between commit: > > 29d5c8db26ad ("genirq: Add DOMAIN_BUS_IPI") > > from the tip tree and commit: > > 9b1b282ccd81 ("irqdomain:

Re: linux-next: manual merge of the staging tree with the tip tree

On Wed, 2 Mar 2016, Stephen Rothwell wrote: > Hi Greg, > > Today's linux-next merge of the staging tree got a conflict in: > > include/linux/irqdomain.h > > between commit: > > 29d5c8db26ad ("genirq: Add DOMAIN_BUS_IPI") > > from the tip tree and commit: > > 9b1b282ccd81 ("irqdomain:

Re: Re: [PATCH v3] staging/android/ion : fix a race condition in the ion driver

> From: Laura Abbott [mailto:labb...@redhat.com] > Sent: Friday, February 26, 2016 7:12 AM > To: eun.taik@samsung.com; gre...@linuxfoundation.org; a...@android.com; > riandr...@android.com; sumit.sem...@linaro.org; dan.carpen...@oracle.com; > Rohit Kumar ;

Re: Re: [PATCH v3] staging/android/ion : fix a race condition in the ion driver

> From: Laura Abbott [mailto:labb...@redhat.com] > Sent: Friday, February 26, 2016 7:12 AM > To: eun.taik@samsung.com; gre...@linuxfoundation.org; a...@android.com; > riandr...@android.com; sumit.sem...@linaro.org; dan.carpen...@oracle.com; > Rohit Kumar ; sri...@marirs.net.in; shawn.lin@rock-

Re: [RFCv7 PATCH 03/10] sched: scheduler-driven cpu frequency selection

Hi, I'm still catching up on the plurality of scheduler/cpufreq threads but I thought I would chime in with some historical reasons for why cpufreq_sched.c looks the way it does today. Quoting Steve Muckle (2016-02-25 16:34:23) > On 02/24/2016 07:55 PM, Rafael J. Wysocki wrote: > > On Monday,

Re: [RFCv7 PATCH 03/10] sched: scheduler-driven cpu frequency selection

Hi, I'm still catching up on the plurality of scheduler/cpufreq threads but I thought I would chime in with some historical reasons for why cpufreq_sched.c looks the way it does today. Quoting Steve Muckle (2016-02-25 16:34:23) > On 02/24/2016 07:55 PM, Rafael J. Wysocki wrote: > > On Monday,

Re: [PATCH] thermal: tegra_soctherm: fix sign bit of temperature

Hi, Rui & Thierry & Matt Could you please take a look on this patch. It's a bug on the temperature's sign bit, it can't show the negative temperature, although it will not cause problems for now. Thanks. Wei. On 2016年02月29日 17:51, Wei Ni wrote: > The sign bit of temperature readback is bit 0,

Re: [PATCH] thermal: tegra_soctherm: fix sign bit of temperature

Hi, Rui & Thierry & Matt Could you please take a look on this patch. It's a bug on the temperature's sign bit, it can't show the negative temperature, although it will not cause problems for now. Thanks. Wei. On 2016年02月29日 17:51, Wei Ni wrote: > The sign bit of temperature readback is bit 0,

Re: [PATCH V4 1/4] mfd: f81504-core: Add Fintek F81504/508/512 PCIE-to-UART/GPIO core support

Hi Andy, Andy Shevchenko 於 2016/2/23 下午 07:05 寫道: On Tue, 2016-02-23 at 14:30 +0800, Peter Hung wrote: +config MFD_FINTEK_F81504_CORE +tristate "Fintek F81504/508/512 PCIE-to-UART/GPIO MFD support" +depends on PCI +select MFD_CORE +default SERIAL_8250

Re: [PATCH V4 1/4] mfd: f81504-core: Add Fintek F81504/508/512 PCIE-to-UART/GPIO core support

Hi Andy, Andy Shevchenko 於 2016/2/23 下午 07:05 寫道: On Tue, 2016-02-23 at 14:30 +0800, Peter Hung wrote: +config MFD_FINTEK_F81504_CORE +tristate "Fintek F81504/508/512 PCIE-to-UART/GPIO MFD support" +depends on PCI +select MFD_CORE +default SERIAL_8250

Re: [PATCH] perf script: fix double free on command_line

On Tue, Mar 01, 2016 at 11:46:20PM +, Colin King wrote: > From: Colin Ian King > > command_line is free'd twice if db_export__branch_types fails. To > avoid this, defer the free'ing of command_line to after this call > so that the error return path will just free

Re: [PATCH] perf script: fix double free on command_line

On Tue, Mar 01, 2016 at 11:46:20PM +, Colin King wrote: > From: Colin Ian King > > command_line is free'd twice if db_export__branch_types fails. To > avoid this, defer the free'ing of command_line to after this call > so that the error return path will just free command_line once. >

[lkp] [lz4c] d327806d6e: -- System halted

-r0-201609-d327806d6ec53b7dfa578112dcd4874704a0d32a-20160301-23742-1sncyj7-0.yaml ARCH=i386 kconfig=i386-randconfig-r0-201609 branch=linux-devel/devel-spot-201603010408 commit=d327806d6ec53b7dfa578112dcd4874704a0d32a BOOT_IMAGE=/pkg/linux/i386-randconfig-r0-201609/gcc-5/d327806d6ec53b7dfa578112dcd4874704a0d32a/vml

[lkp] [lz4c] d327806d6e: -- System halted

-r0-201609-d327806d6ec53b7dfa578112dcd4874704a0d32a-20160301-23742-1sncyj7-0.yaml ARCH=i386 kconfig=i386-randconfig-r0-201609 branch=linux-devel/devel-spot-201603010408 commit=d327806d6ec53b7dfa578112dcd4874704a0d32a BOOT_IMAGE=/pkg/linux/i386-randconfig-r0-201609/gcc-5/d327806d6ec53b7dfa578112dcd4874704a0d32a/vml

[PATCH V2 2/4] regulator: core: Add support for active-discharge configuration

Add support to enable/disable active discharge of regulator via machine constraints. This configuration is done when setting machine constraint during regulator register and if regulator driver implemented the callback ops. Signed-off-by: Laxman Dewangan --- Changes from

[PATCH V2 2/4] regulator: core: Add support for active-discharge configuration

Add support to enable/disable active discharge of regulator via machine constraints. This configuration is done when setting machine constraint during regulator register and if regulator driver implemented the callback ops. Signed-off-by: Laxman Dewangan --- Changes from V1: Make the interface

Re: [PATCH] futex: replace bare barrier() with a READ_ONCE()

On Wed, Mar 2, 2016 at 2:39 PM, Darren Hart wrote: > I believe you are correct with respect to the retry and while condition being > an > appropriate place for the application of READ_ONCE. The question is why is > this > preferred to the existing barrier()? I suggest: > >

Re: [PATCH] futex: replace bare barrier() with a READ_ONCE()

On Wed, Mar 2, 2016 at 2:39 PM, Darren Hart wrote: > I believe you are correct with respect to the retry and while condition being > an > appropriate place for the application of READ_ONCE. The question is why is > this > preferred to the existing barrier()? I suggest: > > While barrier() is a

[PATCH 2/4] regulator: core: Add support for active-discharge configuration

Add support to enable/disable active discharge of regulator via machine constraints. This configuration is done when setting machine constraint during regulator register and if regulator driver implemented the callback ops. Signed-off-by: Laxman Dewangan --- Changes from

[PATCH V2 4/4] regulator: max77620: Add support to configure active-discharge

Add regulator ops callback for configuration of active-discharge and provide necessarily information via regulator descriptor. Signed-off-by: Laxman Dewangan --- Changes from V1: None drivers/regulator/max77620-regulator.c | 9 + 1 file changed, 9 insertions(+)

[PATCH 2/4] regulator: core: Add support for active-discharge configuration

Add support to enable/disable active discharge of regulator via machine constraints. This configuration is done when setting machine constraint during regulator register and if regulator driver implemented the callback ops. Signed-off-by: Laxman Dewangan --- Changes from V1: Make the interface

[PATCH V2 4/4] regulator: max77620: Add support to configure active-discharge

Add regulator ops callback for configuration of active-discharge and provide necessarily information via regulator descriptor. Signed-off-by: Laxman Dewangan --- Changes from V1: None drivers/regulator/max77620-regulator.c | 9 + 1 file changed, 9 insertions(+) diff --git

[PATCH V2 3/4] regulator: helper: Add helper to configure active-discharge using regmap

Add helper function to set the state of active-discharge of regulator using regmap. The HW regulator driver can directly use this by providing the necessary information in the regulator descriptor. Signed-off-by: Laxman Dewangan --- Changes from V1: None

[PATCH V2 0/4] regulator: Add support for configuration of active-discharge

This series add the common regulator DT property for configuration of active discharge and implementing this in regulator core. Also implementing the regulator ops for MAX77620 to configure active discharge. This is based on discussion on patch and comment from Mark Brown: [PATCH V6 7/8] DT:

[PATCH V2 0/4] regulator: Add support for configuration of active-discharge

This series add the common regulator DT property for configuration of active discharge and implementing this in regulator core. Also implementing the regulator ops for MAX77620 to configure active discharge. This is based on discussion on patch and comment from Mark Brown: [PATCH V6 7/8] DT:

[PATCH V2 3/4] regulator: helper: Add helper to configure active-discharge using regmap

Add helper function to set the state of active-discharge of regulator using regmap. The HW regulator driver can directly use this by providing the necessary information in the regulator descriptor. Signed-off-by: Laxman Dewangan --- Changes from V1: None drivers/regulator/helpers.c | 23

[PATCH V2 1/4] regulator: DT: Add DT property for active-discharge configuration

Add common DT property for regulator node to support of active discharge enable/disable configuration of regulator. Signed-off-by: Laxman Dewangan --- Changes from V1: None Documentation/devicetree/bindings/regulator/regulator.txt | 5 + 1 file changed, 5

[PATCH V2 1/4] regulator: DT: Add DT property for active-discharge configuration

Add common DT property for regulator node to support of active discharge enable/disable configuration of regulator. Signed-off-by: Laxman Dewangan --- Changes from V1: None Documentation/devicetree/bindings/regulator/regulator.txt | 5 + 1 file changed, 5 insertions(+) diff --git

[PATCH] ARM: dts: ls102xa: Use new clock binding

According to the current clock driver for Freescale QorIQ platform, new clock binding will be used for LS1021A. Signed-off-by: Alison Wang --- arch/arm/boot/dts/ls1021a.dtsi | 97 +- 1 file changed, 40 insertions(+), 57 deletions(-)

[PATCH] ARM: dts: ls102xa: Use new clock binding

According to the current clock driver for Freescale QorIQ platform, new clock binding will be used for LS1021A. Signed-off-by: Alison Wang --- arch/arm/boot/dts/ls1021a.dtsi | 97 +- 1 file changed, 40 insertions(+), 57 deletions(-) diff --git

Re: [PATCH] eata: Convert eata driver as normal PCI and platform device drivers

Jiang Liu wrote on 02/03/16 13:50: I spoke too soon, without removing and re-inserting the eata module before any filesystems on disks attached to the DPT controller were mounted, I'd get the following messages, similar to ones previously reported: sd 0:0:6:0: tag#0 abort, mbox 1. EATA0:

Re: [PATCH] eata: Convert eata driver as normal PCI and platform device drivers

Jiang Liu wrote on 02/03/16 13:50: I spoke too soon, without removing and re-inserting the eata module before any filesystems on disks attached to the DPT controller were mounted, I'd get the following messages, similar to ones previously reported: sd 0:0:6:0: tag#0 abort, mbox 1. EATA0:

linux-next: Tree for Mar 2

Hi all, Changes since 20160301: New tree: keys The samsung-krzk tree gained a conflict against the arm-soc tree. The tip tree still had its build failure so I applied a supplied patch. The kvm-ppc-paulus tree gained a conflict against the kvm-arm tree. The staging tree gained conflicts

linux-next: Tree for Mar 2

Hi all, Changes since 20160301: New tree: keys The samsung-krzk tree gained a conflict against the arm-soc tree. The tip tree still had its build failure so I applied a supplied patch. The kvm-ppc-paulus tree gained a conflict against the kvm-arm tree. The staging tree gained conflicts

Re: [PATCH] pcmcia: db1xxx: use correct irq_to_gpio helper

Hi Arnd, On Tue, Mar 1, 2016 at 11:12 PM, Arnd Bergmann wrote: > After the removal of asm/gpio.h and asm/mach-au1x00/gpio.h, the db1xxx_ss > pcmcia driver picked up the wrong irq_to_gpio function from the generic > headers. > > This restores the old __au_irq_to_gpio()

Re: [PATCH] pcmcia: db1xxx: use correct irq_to_gpio helper

Hi Arnd, On Tue, Mar 1, 2016 at 11:12 PM, Arnd Bergmann wrote: > After the removal of asm/gpio.h and asm/mach-au1x00/gpio.h, the db1xxx_ss > pcmcia driver picked up the wrong irq_to_gpio function from the generic > headers. > > This restores the old __au_irq_to_gpio() implementation, but keeps

RE: [PATCH v3] Bluetooth: hci_uart: Support firmware download for Marvell

Hi Alan, > From: One Thousand Gnomes [mailto:gno...@lxorguk.ukuu.org.uk] > Sent: Wednesday, March 02, 2016 3:29 AM > To: Amitkumar Karwar > Cc: linux-blueto...@vger.kernel.org; Cathy Luo; linux- > ker...@vger.kernel.org; Nishant Sarmukadam; Ganapathi Bhat > Subject: Re: [PATCH v3] Bluetooth:

RE: [PATCH v3] Bluetooth: hci_uart: Support firmware download for Marvell

Hi Alan, > From: One Thousand Gnomes [mailto:gno...@lxorguk.ukuu.org.uk] > Sent: Wednesday, March 02, 2016 3:29 AM > To: Amitkumar Karwar > Cc: linux-blueto...@vger.kernel.org; Cathy Luo; linux- > ker...@vger.kernel.org; Nishant Sarmukadam; Ganapathi Bhat > Subject: Re: [PATCH v3] Bluetooth:

Re: [RFC PATCH] kvm: Make KVM DF intercept configurable

On 2016-03-01 23:41, Borislav Petkov wrote: > On Tue, Mar 01, 2016 at 10:11:57PM +0100, Paolo Bonzini wrote: >> I just use QEMU's binary translation mode to debug this kind of code (-d >> in_asm is useful and relatively compact (because it only shows loops >> once), > > Ha, I had forgotten about

Re: [RFC PATCH] kvm: Make KVM DF intercept configurable

On 2016-03-01 23:41, Borislav Petkov wrote: > On Tue, Mar 01, 2016 at 10:11:57PM +0100, Paolo Bonzini wrote: >> I just use QEMU's binary translation mode to debug this kind of code (-d >> in_asm is useful and relatively compact (because it only shows loops >> once), > > Ha, I had forgotten about

ext2/3 using ext4 module mkdir IO error on pmem DAX mount

Hi, mkdir failed IO error on pmem DAX ext2/3 fs mount using ext4 module. This happends only on -next tree, not on Linus' tree, at least from 4.5.0-rc5-next-20160224. .config attached. sh-4.2# uname -r 4.5.0-rc6-next-20160301 sh-4.2# sh -x extmod.sh + testmkdir ext2 /dev/pmem0 /daxmnt ext4

ext2/3 using ext4 module mkdir IO error on pmem DAX mount

Hi, mkdir failed IO error on pmem DAX ext2/3 fs mount using ext4 module. This happends only on -next tree, not on Linus' tree, at least from 4.5.0-rc5-next-20160224. .config attached. sh-4.2# uname -r 4.5.0-rc6-next-20160301 sh-4.2# sh -x extmod.sh + testmkdir ext2 /dev/pmem0 /daxmnt ext4

Re: [PATCH] futex: replace bare barrier() with a READ_ONCE()

On Wed, Mar 02, 2016 at 10:31:18AM +0800, Jianyu Zhan wrote: > On Wed, Mar 2, 2016 at 9:37 AM, Darren Hart wrote: > > read_once will use a *volatile assignment instead of calling barrier() > > directly for a word size argument. > > > > With weak statements like "apparently"

Re: [PATCH] futex: replace bare barrier() with a READ_ONCE()

On Wed, Mar 02, 2016 at 10:31:18AM +0800, Jianyu Zhan wrote: > On Wed, Mar 2, 2016 at 9:37 AM, Darren Hart wrote: > > read_once will use a *volatile assignment instead of calling barrier() > > directly for a word size argument. > > > > With weak statements like "apparently" (above) and "could be"

Re: [RFC v2 0/6] Track RCU dereferences in RCU read-side critical sections

On Tue, Mar 01, 2016 at 11:01:34AM +0100, Peter Zijlstra wrote: > On Tue, Mar 01, 2016 at 10:57:07AM +0100, Peter Zijlstra wrote: > > On Tue, Mar 01, 2016 at 05:32:42PM +0800, Boqun Feng wrote: > > > > One could for example allow something like: > > > > > > > > rcu_read_lock(); > > > >

Re: [RFC v2 0/6] Track RCU dereferences in RCU read-side critical sections

On Tue, Mar 01, 2016 at 11:01:34AM +0100, Peter Zijlstra wrote: > On Tue, Mar 01, 2016 at 10:57:07AM +0100, Peter Zijlstra wrote: > > On Tue, Mar 01, 2016 at 05:32:42PM +0800, Boqun Feng wrote: > > > > One could for example allow something like: > > > > > > > > rcu_read_lock(); > > > >

Re: [PATCH] perf, tools, stat: Avoid crash with --per-thread

On Tue, Mar 01, 2016 at 03:32:37PM -0800, Andi Kleen wrote: > From: Andi Kleen > > Bug fix: > > The earlier metrics changes broke --per-thread causing a segfault. > Handle this case correctly. We actually don't print metrics > in per thread mode, so using a 0 shadow CPU is

Re: [PATCH] perf, tools, stat: Avoid crash with --per-thread

On Tue, Mar 01, 2016 at 03:32:37PM -0800, Andi Kleen wrote: > From: Andi Kleen > > Bug fix: > > The earlier metrics changes broke --per-thread causing a segfault. > Handle this case correctly. We actually don't print metrics > in per thread mode, so using a 0 shadow CPU is fine. right, so

Re: [PATCH] usbhid: Fix lockdep unannotated irqs-off warning

On 3/1/16, Alan Stern wrote: > On Tue, 1 Mar 2016, Sedat Dilek wrote: > >> On Tue, Oct 13, 2015 at 2:57 AM, Steven Rostedt >> wrote: >> > On Sat, 3 Oct 2015 12:05:42 +0200 >> > Sedat Dilek wrote: >> > >> >> So, at the

Re: [PATCH] usbhid: Fix lockdep unannotated irqs-off warning

On 3/1/16, Alan Stern wrote: > On Tue, 1 Mar 2016, Sedat Dilek wrote: > >> On Tue, Oct 13, 2015 at 2:57 AM, Steven Rostedt >> wrote: >> > On Sat, 3 Oct 2015 12:05:42 +0200 >> > Sedat Dilek wrote: >> > >> >> So, at the beginning... dunno WTF is causing the problems - no >> >> workaround for

[PATCH] dts/ls1043a-rdb: add the DTS for DSPI support

This patch adds dts nodes for DSPI on LS1043A-RDB. Signed-off-by: Yunhui Cui Signed-off-by: Yuan Yao --- arch/arm64/boot/dts/freescale/fsl-ls1043a-rdb.dts | 13 + 1 file changed, 13 insertions(+) diff --git

[PATCH] dts/ls1043a-rdb: add the DTS for DSPI support

This patch adds dts nodes for DSPI on LS1043A-RDB. Signed-off-by: Yunhui Cui Signed-off-by: Yuan Yao --- arch/arm64/boot/dts/freescale/fsl-ls1043a-rdb.dts | 13 + 1 file changed, 13 insertions(+) diff --git a/arch/arm64/boot/dts/freescale/fsl-ls1043a-rdb.dts

Re: [PATCH] Change the spin_lock/unlock_irq interface in proc_alloc_inum() function

在 2016/3/2 11:09, Al Viro 写道: > On Wed, Mar 02, 2016 at 10:47:59AM +0800, MaJun wrote: >> From: Ma Jun >> >> The spin_lock/unlock_irq interface is not safe when this function is called >> at some case which need irq disabled. > >> For example: >> spin_lock_irqsave()

Re: [PATCH v2 4/5] mm, kswapd: replace kswapd compaction with waking up kcompactd

On Mon, Feb 08, 2016 at 02:38:10PM +0100, Vlastimil Babka wrote: > Similarly to direct reclaim/compaction, kswapd attempts to combine reclaim and > compaction to attempt making memory allocation of given order available. The > details differ from direct reclaim e.g. in having high watermark as a

Re: [PATCH] Change the spin_lock/unlock_irq interface in proc_alloc_inum() function

在 2016/3/2 11:09, Al Viro 写道: > On Wed, Mar 02, 2016 at 10:47:59AM +0800, MaJun wrote: >> From: Ma Jun >> >> The spin_lock/unlock_irq interface is not safe when this function is called >> at some case which need irq disabled. > >> For example: >> spin_lock_irqsave() >> | >>

Re: [PATCH v2 4/5] mm, kswapd: replace kswapd compaction with waking up kcompactd

On Mon, Feb 08, 2016 at 02:38:10PM +0100, Vlastimil Babka wrote: > Similarly to direct reclaim/compaction, kswapd attempts to combine reclaim and > compaction to attempt making memory allocation of given order available. The > details differ from direct reclaim e.g. in having high watermark as a

Re: [PATCH] ASoC: intel: remove unused variable

On Wed, Mar 02, 2016 at 10:02:23AM +0900, Mark Brown wrote: > On Tue, Mar 01, 2016 at 11:19:27AM +0530, Sudip Mukherjee wrote: > > > Can i not keep using my gmail as my From: ? > > The advantage of using gmail as my From: is that the discussion and all > > threads related to my patches will be in

Re: [PATCH] ASoC: intel: remove unused variable

On Wed, Mar 02, 2016 at 10:02:23AM +0900, Mark Brown wrote: > On Tue, Mar 01, 2016 at 11:19:27AM +0530, Sudip Mukherjee wrote: > > > Can i not keep using my gmail as my From: ? > > The advantage of using gmail as my From: is that the discussion and all > > threads related to my patches will be in

Re: [PATCH] usbhid: Fix lockdep unannotated irqs-off warning

On 3/1/16, Alan Stern wrote: > On Tue, 1 Mar 2016, Sedat Dilek wrote: > >> On Tue, Oct 13, 2015 at 2:57 AM, Steven Rostedt >> wrote: >> > On Sat, 3 Oct 2015 12:05:42 +0200 >> > Sedat Dilek wrote: >> > >> >> So, at the

Re: [PATCH] usbhid: Fix lockdep unannotated irqs-off warning

On 3/1/16, Alan Stern wrote: > On Tue, 1 Mar 2016, Sedat Dilek wrote: > >> On Tue, Oct 13, 2015 at 2:57 AM, Steven Rostedt >> wrote: >> > On Sat, 3 Oct 2015 12:05:42 +0200 >> > Sedat Dilek wrote: >> > >> >> So, at the beginning... dunno WTF is causing the problems - no >> >> workaround for

Re: [PATCH 1/2] regulator: DT: Add support to scale ramp delay based on platform behavior

On Wednesday 02 March 2016 10:05 AM, Mark Brown wrote: * PGP Signed by an unknown key On Wed, Mar 02, 2016 at 09:05:26AM +0530, Laxman Dewangan wrote: On Wednesday 02 March 2016 09:08 AM, Mark Brown wrote: You're not trying to scale the value here, you're trying to replace the value because

[PATCH] vTPM: fix missing error handling for suspend operation

ibmvtpm_send_crq in tpm_ibmvtpm_suspend returns errors in a more granular level than what the existing code does. This patch adds the missing CRQ transport event code checks to ensure appropriate action taken, in the case that ibmvtpm_send_crq returns H_CLOSED. Signed-off-by: Hon Ching(Vicky) Lo

Re: [PATCH 1/2] regulator: DT: Add support to scale ramp delay based on platform behavior

On Wednesday 02 March 2016 10:05 AM, Mark Brown wrote: * PGP Signed by an unknown key On Wed, Mar 02, 2016 at 09:05:26AM +0530, Laxman Dewangan wrote: On Wednesday 02 March 2016 09:08 AM, Mark Brown wrote: You're not trying to scale the value here, you're trying to replace the value because

[PATCH] vTPM: fix missing error handling for suspend operation

ibmvtpm_send_crq in tpm_ibmvtpm_suspend returns errors in a more granular level than what the existing code does. This patch adds the missing CRQ transport event code checks to ensure appropriate action taken, in the case that ibmvtpm_send_crq returns H_CLOSED. Signed-off-by: Hon Ching(Vicky) Lo

[PATCH 1/2] ACPI / OSL: Cleanup initrd table override code

This patch cleans up initrd table override code, merging redundant logics and re-ordering code blocks. No functional changes. Signed-off-by: Lv Zheng --- drivers/acpi/osl.c | 114 1 file changed, 52 insertions(+), 62

[PATCH 1/2] ACPI / OSL: Cleanup initrd table override code

This patch cleans up initrd table override code, merging redundant logics and re-ordering code blocks. No functional changes. Signed-off-by: Lv Zheng --- drivers/acpi/osl.c | 114 1 file changed, 52 insertions(+), 62 deletions(-) diff --git

[PATCH 0/2] ACPI / OSL: Improve initrd override mechanism

This patchset improves initrd override mechanism. Lv Zheng (2): ACPI / OSL: Cleanup initrd table override code ACPI / OSL: Add support to install tables via initrd drivers/acpi/internal.h |1 + drivers/acpi/osl.c | 158 +--

[PATCH 2/2] ACPI / OSL: Add support to install tables via initrd

This patch adds support to install tables from initrd. If a table in the initrd wasn't used by the override mechanism, the table would be installed after initializing all RSDT/XSDT tables. Reference: https://lkml.org/lkml/2014/2/28/368 Reported-by: Thomas Renninger Signed-off-by:

[PATCH 0/2] ACPI / OSL: Improve initrd override mechanism

This patchset improves initrd override mechanism. Lv Zheng (2): ACPI / OSL: Cleanup initrd table override code ACPI / OSL: Add support to install tables via initrd drivers/acpi/internal.h |1 + drivers/acpi/osl.c | 158 +--

[PATCH 2/2] ACPI / OSL: Add support to install tables via initrd

This patch adds support to install tables from initrd. If a table in the initrd wasn't used by the override mechanism, the table would be installed after initializing all RSDT/XSDT tables. Reference: https://lkml.org/lkml/2014/2/28/368 Reported-by: Thomas Renninger Signed-off-by: Lv Zheng ---

[PATCH] pinctrl: uniphier: rename CONFIG options and file names

The current "CONFIG_PINCTRL_UNIPHIER_PH1_*" is too long. It would not hurt to drop "PH1_" because "UNIPHIER_" already well specifies the SoC family. Also, rename files for consistency. Signed-off-by: Masahiro Yamada --- drivers/pinctrl/uniphier/Kconfig

[PATCH] pinctrl: uniphier: rename CONFIG options and file names

The current "CONFIG_PINCTRL_UNIPHIER_PH1_*" is too long. It would not hurt to drop "PH1_" because "UNIPHIER_" already well specifies the SoC family. Also, rename files for consistency. Signed-off-by: Masahiro Yamada --- drivers/pinctrl/uniphier/Kconfig | 12

Re: [PATCH 1/2] rtc: max77686: Add support for MAX20024/MAX77620 RTC IP

On Wednesday 02 March 2016 09:58 AM, Krzysztof Kozlowski wrote: On 02.03.2016 13:10, Laxman Dewangan wrote: On Wednesday 02 March 2016 09:22 AM, Krzysztof Kozlowski wrote: On 02.03.2016 11:15, Laxman Dewangan wrote: (kernel_ulong_t)_drv_data, }, +{ "max77620-rtc", .driver_data =

Re: [PATCH 1/2] rtc: max77686: Add support for MAX20024/MAX77620 RTC IP

On Wednesday 02 March 2016 09:58 AM, Krzysztof Kozlowski wrote: On 02.03.2016 13:10, Laxman Dewangan wrote: On Wednesday 02 March 2016 09:22 AM, Krzysztof Kozlowski wrote: On 02.03.2016 11:15, Laxman Dewangan wrote: (kernel_ulong_t)_drv_data, }, +{ "max77620-rtc", .driver_data =

[GIT PULL] phy: for 4.6 merge window

Hi Greg, Please find the pull request for 4.6 merge window below. It adds a couple of new PHY drivers, usb-uart functionality in rockchip-usb and misc cleanups/fixes. Let me know If I have to change something. Thanks Kishon The following changes since commit

[GIT PULL] phy: for 4.6 merge window

Hi Greg, Please find the pull request for 4.6 merge window below. It adds a couple of new PHY drivers, usb-uart functionality in rockchip-usb and misc cleanups/fixes. Let me know If I have to change something. Thanks Kishon The following changes since commit

[PATCH 3/7] phy: Add driver for rockchip Display Port PHY

From: Yakir Yang Add phy driver for the Rockchip DisplayPort PHY module. This is required to get DisplayPort working in Rockchip SoCs. Signed-off-by: Yakir Yang Reviewed-by: Heiko Stuebner Signed-off-by: Kishon Vijay Abraham I

[PATCH 3/7] phy: Add driver for rockchip Display Port PHY

From: Yakir Yang Add phy driver for the Rockchip DisplayPort PHY module. This is required to get DisplayPort working in Rockchip SoCs. Signed-off-by: Yakir Yang Reviewed-by: Heiko Stuebner Signed-off-by: Kishon Vijay Abraham I --- drivers/phy/Kconfig |7 ++

[PATCH 4/7] dt-bindings: add document for rockchip dp phy

From: Yakir Yang Add dt binding documentation for rockchip display port PHY. Signed-off-by: Yakir Yang Acked-by: Rob Herring Reviewed-by: Heiko Stuebner Signed-off-by: Kishon Vijay Abraham I ---

[PATCH 4/7] dt-bindings: add document for rockchip dp phy

From: Yakir Yang Add dt binding documentation for rockchip display port PHY. Signed-off-by: Yakir Yang Acked-by: Rob Herring Reviewed-by: Heiko Stuebner Signed-off-by: Kishon Vijay Abraham I --- .../devicetree/bindings/phy/rockchip-dp-phy.txt| 22 1 file changed,

[PATCH 7/7] phy: Fix armada375 compile test build on UM

From: Krzysztof Kozlowski The phy-armada375-usb2 driver uses IOMEM functions so COMPILE_TEST && OF build failed with: drivers/built-in.o: In function `armada375_usb_phy_probe': phy-armada375-usb2.c:(.text+0x121d): undefined reference to `devm_ioremap_resource'

[PATCH 7/7] phy: Fix armada375 compile test build on UM

From: Krzysztof Kozlowski The phy-armada375-usb2 driver uses IOMEM functions so COMPILE_TEST && OF build failed with: drivers/built-in.o: In function `armada375_usb_phy_probe': phy-armada375-usb2.c:(.text+0x121d): undefined reference to `devm_ioremap_resource' Signed-off-by: Krzysztof

RE: [RFC PATCH] drivers: ata: Read Rx water mark value from device-tree

+ Michal > -Original Message- > From: Anurag Kumar Vulisha > Sent: Friday, February 26, 2016 7:18 PM > To: 'Rob Herring' > Cc: Arnd Bergmann; pawel.m...@arm.com; mark.rutl...@arm.com; > ijc+devicet...@hellion.org.uk; ga...@codeaurora.org; t...@kernel.org; > devicet...@vger.kernel.org;

RE: [RFC PATCH] drivers: ata: Read Rx water mark value from device-tree

+ Michal > -Original Message- > From: Anurag Kumar Vulisha > Sent: Friday, February 26, 2016 7:18 PM > To: 'Rob Herring' > Cc: Arnd Bergmann; pawel.m...@arm.com; mark.rutl...@arm.com; > ijc+devicet...@hellion.org.uk; ga...@codeaurora.org; t...@kernel.org; > devicet...@vger.kernel.org;

[PATCH 5/7] phy: rockchip-usb: add handler for usb-uart functionality

From: Heiko Stuebner Most newer Rockchip SoCs provide the possibility to use a usb-phy as passthrough for the debug uart (uart2), making it possible to for example get console output without needing to open the device. This patch adds an early_initcall to enable this

[PATCH 1/7] Documentation: bindings: add dt documentation for Rockchip eMMC PHY

From: Shawn Lin This patch adds a binding that describes the Rockchip eMMC PHYs found on Rockchip SoCs eMMC interface. Signed-off-by: Shawn Lin Signed-off-by: Kishon Vijay Abraham I ---

[PATCH 6/7] phy: rcar-gen3-usb2: remove HSUSB registers handling

From: Yoshihiro Shimoda Since the related driver (CPG/MSSR driver) only manages the first module clock, this driver should not handle the HSUSB registers. So, this patch removes the HSUSB registers handling. Signed-off-by: Yoshihiro Shimoda

[PATCH 2/7] phy: add a driver for the Rockchip SoC internal eMMC PHY

From: Shawn Lin This patch to add a generic PHY driver for ROCKCHIP eMMC PHY. Access the PHY via registers provided by GRF (general register files) module. Signed-off-by: Shawn Lin Signed-off-by: Kishon Vijay Abraham I ---

[PATCH 5/7] phy: rockchip-usb: add handler for usb-uart functionality

From: Heiko Stuebner Most newer Rockchip SoCs provide the possibility to use a usb-phy as passthrough for the debug uart (uart2), making it possible to for example get console output without needing to open the device. This patch adds an early_initcall to enable this functionality conditionally

[PATCH 1/7] Documentation: bindings: add dt documentation for Rockchip eMMC PHY

From: Shawn Lin This patch adds a binding that describes the Rockchip eMMC PHYs found on Rockchip SoCs eMMC interface. Signed-off-by: Shawn Lin Signed-off-by: Kishon Vijay Abraham I --- .../devicetree/bindings/phy/rockchip-emmc-phy.txt | 19 +++ 1 file changed, 19

[PATCH 6/7] phy: rcar-gen3-usb2: remove HSUSB registers handling

From: Yoshihiro Shimoda Since the related driver (CPG/MSSR driver) only manages the first module clock, this driver should not handle the HSUSB registers. So, this patch removes the HSUSB registers handling. Signed-off-by: Yoshihiro Shimoda Acked-by: Rob Herring Signed-off-by: Kishon Vijay

[PATCH 2/7] phy: add a driver for the Rockchip SoC internal eMMC PHY

From: Shawn Lin This patch to add a generic PHY driver for ROCKCHIP eMMC PHY. Access the PHY via registers provided by GRF (general register files) module. Signed-off-by: Shawn Lin Signed-off-by: Kishon Vijay Abraham I --- drivers/phy/Kconfig |7 ++ drivers/phy/Makefile

Re: [PATCH v2 2/5] mm, compaction: introduce kcompactd

On Mon, Feb 08, 2016 at 02:38:08PM +0100, Vlastimil Babka wrote: > Memory compaction can be currently performed in several contexts: > > - kswapd balancing a zone after a high-order allocation failure > - direct compaction to satisfy a high-order allocation, including THP page > fault attemps >

Re: [PATCH v2 2/5] mm, compaction: introduce kcompactd

On Mon, Feb 08, 2016 at 02:38:08PM +0100, Vlastimil Babka wrote: > Memory compaction can be currently performed in several contexts: > > - kswapd balancing a zone after a high-order allocation failure > - direct compaction to satisfy a high-order allocation, including THP page > fault attemps >

linux-next: manual merge of the akpm-current tree with the tip tree

Hi Andrew, Today's linux-next merge of the akpm-current tree got conflicts in: arch/x86/boot/Makefile arch/x86/boot/compressed/Makefile arch/x86/entry/vdso/Makefile arch/x86/kernel/Makefile arch/x86/realmode/rm/Makefile drivers/firmware/efi/libstub/Makefile between commit:

linux-next: manual merge of the akpm-current tree with the tip tree

Hi Andrew, Today's linux-next merge of the akpm-current tree got conflicts in: arch/x86/boot/Makefile arch/x86/boot/compressed/Makefile arch/x86/entry/vdso/Makefile arch/x86/kernel/Makefile arch/x86/realmode/rm/Makefile drivers/firmware/efi/libstub/Makefile between commit:

Re: Applied "regmap: Keep regmap_write_bits()" to the regmap tree

Hi Mark, On Wed, 2 Mar 2016 13:36:33 +0900 Mark Brown wrote: > > On Tue, Mar 01, 2016 at 06:11:46PM +1100, Stephen Rothwell wrote: > > > You already merged part of the regmap tree into the sound-asoc tree, > > why not do that again with the fix? > > I rebuilt the trees.

Re: Applied "regmap: Keep regmap_write_bits()" to the regmap tree

Hi Mark, On Wed, 2 Mar 2016 13:36:33 +0900 Mark Brown wrote: > > On Tue, Mar 01, 2016 at 06:11:46PM +1100, Stephen Rothwell wrote: > > > You already merged part of the regmap tree into the sound-asoc tree, > > why not do that again with the fix? > > I rebuilt the trees. OK, thanks for the

Re: [PATCH v3] net: jme: fix suspend/resume on JMC260

On Wed, 24 Feb 2016 23:58:56 -0500 (EST), David Miller wrote > From: Diego Viola > Date: Tue, 23 Feb 2016 12:04:04 -0300 > > > The JMC260 network card fails to suspend/resume because the call to > > jme_start_irq() was too early, moving the call to jme_start_irq() after >

Re: [PATCH v3] net: jme: fix suspend/resume on JMC260

On Wed, 24 Feb 2016 23:58:56 -0500 (EST), David Miller wrote > From: Diego Viola > Date: Tue, 23 Feb 2016 12:04:04 -0300 > > > The JMC260 network card fails to suspend/resume because the call to > > jme_start_irq() was too early, moving the call to jme_start_irq() after > > the call to

  1   2   3   4   5   6   7   8   9   10   >