Re: [PATCH 1/2] staging: dgnc: fix 'line over 80 characters'

On Fri, 2016-03-25 at 14:42 +0900, DaeSeok Youn wrote: > 2016-03-25 12:19 GMT+09:00 Joe Perches : > > On Fri, 2016-03-25 at 11:44 +0900, Daeseok Youn wrote: > > > fix checkpatch.pl warning about 'line over 80 characters' > > > in dgnc_neo.c [] > > > diff --git

Re: [PATCH 1/2] staging: dgnc: fix 'line over 80 characters'

On Fri, 2016-03-25 at 14:42 +0900, DaeSeok Youn wrote: > 2016-03-25 12:19 GMT+09:00 Joe Perches : > > On Fri, 2016-03-25 at 11:44 +0900, Daeseok Youn wrote: > > > fix checkpatch.pl warning about 'line over 80 characters' > > > in dgnc_neo.c [] > > > diff --git a/drivers/staging/dgnc/dgnc_neo.c >

Re: [PATCH] ARM: dts: exynos: Fix invalid maximum voltage for buck9 supplying SD card

dts: Add dts file for Odroid XU3 board") > Signed-off-by: Krzysztof Kozlowski <k.kozlow...@samsung.com> > > --- > > The issue can be reproduced on next-20160324 with > bae4fdc88d7f7dda1 (regulator: core: Ensure we are at least in bounds for our > constraints). > -

Re: [PATCH] ARM: dts: exynos: Fix invalid maximum voltage for buck9 supplying SD card

dts: Add dts file for Odroid XU3 board") > Signed-off-by: Krzysztof Kozlowski > > --- > > The issue can be reproduced on next-20160324 with > bae4fdc88d7f7dda1 (regulator: core: Ensure we are at least in bounds for our > constraints). > --- > arch/arm/boot/dts/exynos

Re: [PATCH 1/2] staging: dgnc: fix 'line over 80 characters'

2016-03-25 12:19 GMT+09:00 Joe Perches : > On Fri, 2016-03-25 at 11:44 +0900, Daeseok Youn wrote: >> fix checkpatch.pl warning about 'line over 80 characters' >> in dgnc_neo.c > [] >> diff --git a/drivers/staging/dgnc/dgnc_neo.c >> b/drivers/staging/dgnc/dgnc_neo.c > [] >> @@

Re: [PATCH 1/2] staging: dgnc: fix 'line over 80 characters'

2016-03-25 12:19 GMT+09:00 Joe Perches : > On Fri, 2016-03-25 at 11:44 +0900, Daeseok Youn wrote: >> fix checkpatch.pl warning about 'line over 80 characters' >> in dgnc_neo.c > [] >> diff --git a/drivers/staging/dgnc/dgnc_neo.c >> b/drivers/staging/dgnc/dgnc_neo.c > [] >> @@ -77,7 +77,8 @@

Re: [PATCH RT 4/6] rt/locking: Reenable migration accross schedule

On Thu, 2016-03-24 at 12:06 +0100, Mike Galbraith wrote: > On Thu, 2016-03-24 at 11:44 +0100, Thomas Gleixner wrote: > > > > > On the bright side, with the busted migrate enable business reverted, > > > plus one dinky change from me [1], master-rt.today has completed 100 > > > iterations of

Re: [PATCH RT 4/6] rt/locking: Reenable migration accross schedule

On Thu, 2016-03-24 at 12:06 +0100, Mike Galbraith wrote: > On Thu, 2016-03-24 at 11:44 +0100, Thomas Gleixner wrote: > > > > > On the bright side, with the busted migrate enable business reverted, > > > plus one dinky change from me [1], master-rt.today has completed 100 > > > iterations of

Re: [PATCH V8 00/14] Add T210 support in Tegra soctherm

Hi, Eduardo Will you take this series, it seems no more comments. Thanks. Wei. On 2016年03月16日 16:55, Wei Ni wrote: > This patchset adds following functions for tegra_soctherm driver: > 1. add T210 support. > 2. export debugfs to show some registers. > 3. add thermtrip funciton. > 4. add

Re: [PATCH V8 00/14] Add T210 support in Tegra soctherm

Hi, Eduardo Will you take this series, it seems no more comments. Thanks. Wei. On 2016年03月16日 16:55, Wei Ni wrote: > This patchset adds following functions for tegra_soctherm driver: > 1. add T210 support. > 2. export debugfs to show some registers. > 3. add thermtrip funciton. > 4. add

[PATCH] driver: input :touchscreen : add Raydium I2C touch driver

Raydium I2C touch driver. Signed-off-by: jeffrey.lin --- drivers/input/touchscreen/Kconfig | 12 + drivers/input/touchscreen/Makefile | 1 + drivers/input/touchscreen/raydium_i2c_ts.c | 932 + 3 files changed, 945

[PATCH] driver: input :touchscreen : add Raydium I2C touch driver

Raydium I2C touch driver. Signed-off-by: jeffrey.lin --- drivers/input/touchscreen/Kconfig | 12 + drivers/input/touchscreen/Makefile | 1 + drivers/input/touchscreen/raydium_i2c_ts.c | 932 + 3 files changed, 945 insertions(+) create mode 100644

Re: [PATCH v2] cpufreq: rockchip: add driver

On 24-03-16, 23:09, Finley Xiao wrote: > --- a/arch/arm64/boot/dts/rockchip/rk3366.dtsi > +++ b/arch/arm64/boot/dts/rockchip/rk3366.dtsi > + cpufreq { > + compatible = "***,***"; > + } > > Does it create a DT node for a dummy device too ? Yes, its not allowed. --

Re: [PATCH v2] cpufreq: rockchip: add driver

On 24-03-16, 23:09, Finley Xiao wrote: > --- a/arch/arm64/boot/dts/rockchip/rk3366.dtsi > +++ b/arch/arm64/boot/dts/rockchip/rk3366.dtsi > + cpufreq { > + compatible = "***,***"; > + } > > Does it create a DT node for a dummy device too ? Yes, its not allowed. --

Re: [PATCH 1/1] usb: chipidea: add DMA mask configuration API

Hi Peter, [auto build test ERROR on v4.5-rc7] [also build test ERROR on next-20160324] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url: https://github.com/0day-ci/linux/commits/Peter-Chen/usb-chipidea-add-DMA-mask-configuration-API

Re: [PATCH 1/1] usb: chipidea: add DMA mask configuration API

Hi Peter, [auto build test ERROR on v4.5-rc7] [also build test ERROR on next-20160324] [if your patch is applied to the wrong git tree, please drop us a note to help improving the system] url: https://github.com/0day-ci/linux/commits/Peter-Chen/usb-chipidea-add-DMA-mask-configuration-API

Re: [PATCH] arm64/dma-mapping: Add DMA_ATTR_ALLOC_SINGLE_PAGES support

Hi, On Thu, Mar 24, 2016 at 4:50 AM, Will Deacon wrote: >> > I have a slight snag with this, in that you don't consult the IOMMU >> > pgsize_bitmap at any point, and assume that it can map pages at the >> > same granularity as the CPU. The documentation for >> >

Re: [PATCH] arm64/dma-mapping: Add DMA_ATTR_ALLOC_SINGLE_PAGES support

Hi, On Thu, Mar 24, 2016 at 4:50 AM, Will Deacon wrote: >> > I have a slight snag with this, in that you don't consult the IOMMU >> > pgsize_bitmap at any point, and assume that it can map pages at the >> > same granularity as the CPU. The documentation for >> > DMA_ATTR_ALLOC_SINGLE_PAGES seems

Re: [PATCH 1/6] block: ensure we don't truncate top bits of the request command flags

On 03/24/2016 08:08 PM, Mike Christie wrote: On 03/22/2016 02:01 PM, Jens Axboe wrote: On 03/22/2016 12:59 PM, Christoph Hellwig wrote: On Tue, Mar 22, 2016 at 11:55:15AM -0600, Jens Axboe wrote: Some of the flags that we want to use from the make_request_fn path are now larger than 32-bit,

Re: [PATCH 1/6] block: ensure we don't truncate top bits of the request command flags

On 03/24/2016 08:08 PM, Mike Christie wrote: On 03/22/2016 02:01 PM, Jens Axboe wrote: On 03/22/2016 12:59 PM, Christoph Hellwig wrote: On Tue, Mar 22, 2016 at 11:55:15AM -0600, Jens Axboe wrote: Some of the flags that we want to use from the make_request_fn path are now larger than 32-bit,

Re: [PATCH] usb: chipidea: Configure DMA properties and ops from DT

On Tue, Mar 08, 2016 at 07:40:08PM -0800, Bjorn Andersson wrote: > On Tue, Mar 8, 2016 at 11:52 AM, Li Yang wrote: > > On Wed, Mar 2, 2016 at 4:59 PM, Li Yang wrote: > >> On Mon, Feb 22, 2016 at 4:07 PM, Bjorn Andersson > >>

Re: [GIT PULL] Ceph fixes for -rc7

On Sun, Mar 06 2016, Sage Weil wrote: > Hi Linus, > > Please pull the following Ceph patch from > > git://git.kernel.org/pub/scm/linux/kernel/git/sage/ceph-client.git for-linus > > This is a final commit we missed to align the protocol compatibility with > the feature bits. It decodes a few

Re: [PATCH] usb: chipidea: Configure DMA properties and ops from DT

On Tue, Mar 08, 2016 at 07:40:08PM -0800, Bjorn Andersson wrote: > On Tue, Mar 8, 2016 at 11:52 AM, Li Yang wrote: > > On Wed, Mar 2, 2016 at 4:59 PM, Li Yang wrote: > >> On Mon, Feb 22, 2016 at 4:07 PM, Bjorn Andersson > >> wrote: > >>> On Mon 22 Feb 02:03 PST 2016, Srinivas Kandagatla wrote:

Re: [GIT PULL] Ceph fixes for -rc7

On Sun, Mar 06 2016, Sage Weil wrote: > Hi Linus, > > Please pull the following Ceph patch from > > git://git.kernel.org/pub/scm/linux/kernel/git/sage/ceph-client.git for-linus > > This is a final commit we missed to align the protocol compatibility with > the feature bits. It decodes a few

[PATCH] ASoC: mediatek: Add second I2S on mt8173-rt5650 machine driver

This patch adds second I2S for rt5650 codec on mt8173-rt5650 machine driver. Signed-off-by: PC Liao --- .../devicetree/bindings/sound/mt8173-rt5650.txt|6 +++ sound/soc/mediatek/mt8173-rt5650.c | 55 ++-- 2 files changed, 56

[PATCH] ASoC: mediatek: Add second I2S on mt8173-rt5650 machine driver

This patch adds second I2S for rt5650 codec on mt8173-rt5650 machine driver. Signed-off-by: PC Liao --- .../devicetree/bindings/sound/mt8173-rt5650.txt|6 +++ sound/soc/mediatek/mt8173-rt5650.c | 55 ++-- 2 files changed, 56 insertions(+), 5

[PATCH] dt-bindings: input: add Raydium I2C touch bindings

Document the device tree binfings of Raydium I2C touch. Signed-off-by: jeffrey.lin --- .../devicetree/bindings/input/raydium_i2c_ts.txt | 20 .../devicetree/bindings/vendor-prefixes.txt | 1 + 2 files changed, 21 insertions(+) create

[PATCH] dt-bindings: input: add Raydium I2C touch bindings

Document the device tree binfings of Raydium I2C touch. Signed-off-by: jeffrey.lin --- .../devicetree/bindings/input/raydium_i2c_ts.txt | 20 .../devicetree/bindings/vendor-prefixes.txt | 1 + 2 files changed, 21 insertions(+) create mode 100644

Perf misreports userspace args to unoptimized functions

Hi. I'm seeing an issue with the way perf interfaces with uprobes that results in incorrect printing of function arguments under fairly normal conditions. Example: Let's say I have a trivial C program tst.c: = #include #include int f(int x) { return

Perf misreports userspace args to unoptimized functions

Hi. I'm seeing an issue with the way perf interfaces with uprobes that results in incorrect printing of function arguments under fairly normal conditions. Example: Let's say I have a trivial C program tst.c: = #include #include int f(int x) { return

Re: usb: gadget breakage on N900: bind UDC by name passed via usb_gadget_driver structure

OK, so at last I finished charging of my N900; found 1.8V USB to UART adapter and soldered it to the phone. I managed to boot N900 with working USB gadget (builtin g_ether) in boardfile mode, can ping it from PC and transfer data. I don't see any issue (except of musb name issue in twl phy

Re: usb: gadget breakage on N900: bind UDC by name passed via usb_gadget_driver structure

OK, so at last I finished charging of my N900; found 1.8V USB to UART adapter and soldered it to the phone. I managed to boot N900 with working USB gadget (builtin g_ether) in boardfile mode, can ping it from PC and transfer data. I don't see any issue (except of musb name issue in twl phy

Re: [PATCH 1/2] staging: dgnc: fix 'line over 80 characters'

On Fri, 2016-03-25 at 11:44 +0900, Daeseok Youn wrote: > fix checkpatch.pl warning about 'line over 80 characters' > in dgnc_neo.c [] > diff --git a/drivers/staging/dgnc/dgnc_neo.c b/drivers/staging/dgnc/dgnc_neo.c [] > @@ -77,7 +77,8 @@ struct board_ops dgnc_neo_ops = { >  

Re: [PATCH 1/2] staging: dgnc: fix 'line over 80 characters'

On Fri, 2016-03-25 at 11:44 +0900, Daeseok Youn wrote: > fix checkpatch.pl warning about 'line over 80 characters' > in dgnc_neo.c [] > diff --git a/drivers/staging/dgnc/dgnc_neo.c b/drivers/staging/dgnc/dgnc_neo.c [] > @@ -77,7 +77,8 @@ struct board_ops dgnc_neo_ops = { >  

[REDO PATCH] x86/perf: Move events_sysfs_show() outside CPU_SUP_INTEL

This patch moves events_sysfs_show outside CONFIG_CPU_SUP_INTEL, because this interface will be also used in an AMD power reporting PMU driver. Otherwise, below build error would be encountered: All error/warnings (new ones prefixed by >>): In file included from

[REDO PATCH] x86/perf: Move events_sysfs_show() outside CPU_SUP_INTEL

This patch moves events_sysfs_show outside CONFIG_CPU_SUP_INTEL, because this interface will be also used in an AMD power reporting PMU driver. Otherwise, below build error would be encountered: All error/warnings (new ones prefixed by >>): In file included from

Re: [PATCH v2] ARM: exynos_defconfig: Enable Samsung media platform drivers as modules

Hello Krzysztof, On 03/23/2016 10:00 PM, Krzysztof Kozlowski wrote: > On 24.03.2016 09:26, Javier Martinez Canillas wrote: >> There are a bunch of media platform drivers under drivers/media/platform/ >> that are for Samsung SoCs but are not being built with exynos_defconfig. >> >> This patch

Re: [PATCH v2] ARM: exynos_defconfig: Enable Samsung media platform drivers as modules

Hello Krzysztof, On 03/23/2016 10:00 PM, Krzysztof Kozlowski wrote: > On 24.03.2016 09:26, Javier Martinez Canillas wrote: >> There are a bunch of media platform drivers under drivers/media/platform/ >> that are for Samsung SoCs but are not being built with exynos_defconfig. >> >> This patch

[PATCH v2] arm64: cpuidle: make arm_cpuidle_suspend() a bit more efficient

Currently, we check two pointers: cpu_ops and cpu_suspend on every idle state entry. These pointers check can be avoided: If cpu_ops has not been registered, arm_cpuidle_init() will return -EOPNOTSUPP, so arm_cpuidle_suspend() will never have chance to run. In other word, the cpu_ops check can be

[PATCH v2] arm64: cpuidle: make arm_cpuidle_suspend() a bit more efficient

Currently, we check two pointers: cpu_ops and cpu_suspend on every idle state entry. These pointers check can be avoided: If cpu_ops has not been registered, arm_cpuidle_init() will return -EOPNOTSUPP, so arm_cpuidle_suspend() will never have chance to run. In other word, the cpu_ops check can be

Re: [PATCH] sbs-battery: fix power status when battery is dry

On Thu, Mar 24, 2016 at 2:43 PM, YH Huang wrote: > > Hi Daniel, > > On Thu, 2016-03-24 at 12:01 +0800, Daniel Kurtz wrote: > > Hi YH, > > > > On Wed, Mar 23, 2016 at 5:53 PM, YH Huang wrote: > > > When the battery is dry and BATTERY_FULL_DISCHARGED

Re: [PATCH] sbs-battery: fix power status when battery is dry

On Thu, Mar 24, 2016 at 2:43 PM, YH Huang wrote: > > Hi Daniel, > > On Thu, 2016-03-24 at 12:01 +0800, Daniel Kurtz wrote: > > Hi YH, > > > > On Wed, Mar 23, 2016 at 5:53 PM, YH Huang wrote: > > > When the battery is dry and BATTERY_FULL_DISCHARGED is set, > > > we should check

[PATCH] phy: twl4030-usb: fix musb-hdrc name for non-dt case

musb device is allocated with PLATFORM_DEVID_AUTO, fix incorrect lookup name in non-dt case. This fixes issue with musb initialization on Nokia N900 in boardfile boot mode. Signed-off-by: Ruslan Bilovol --- drivers/phy/phy-twl4030-usb.c | 2 +- 1 file changed, 1

[PATCH] phy: twl4030-usb: fix musb-hdrc name for non-dt case

musb device is allocated with PLATFORM_DEVID_AUTO, fix incorrect lookup name in non-dt case. This fixes issue with musb initialization on Nokia N900 in boardfile boot mode. Signed-off-by: Ruslan Bilovol --- drivers/phy/phy-twl4030-usb.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

Re: [PATCH 2/2] ARM: sun7i: dt: Enable dram gate 5 (tve0 clock) for simplefb TV output

On Fri, Mar 25, 2016 at 2:08 AM, Priit Laes wrote: > From: Priit Laes > > Seems like dram_gate 5 was forgotten when DRAM gating driver was added. > > Enable it. > > Signed-off-by: Priit Laes Fixes: 0b4bf5a5200b ("ARM: dts: sun7i: Add

Re: [PATCH 2/2] ARM: sun7i: dt: Enable dram gate 5 (tve0 clock) for simplefb TV output

On Fri, Mar 25, 2016 at 2:08 AM, Priit Laes wrote: > From: Priit Laes > > Seems like dram_gate 5 was forgotten when DRAM gating driver was added. > > Enable it. > > Signed-off-by: Priit Laes Fixes: 0b4bf5a5200b ("ARM: dts: sun7i: Add DRAM gates") Thanks! > --- >

Re: [PATCH 1/2] ARM: sun4i: dt: Enable dram gate 5 (tve0 clock) for simplefb TV output

On Fri, Mar 25, 2016 at 2:08 AM, Priit Laes wrote: > From: Priit Laes > > Seems like dram_gate 5 was forgotten when DRAM gate driver was added. > > Enable it. > > Signed-off-by: Priit Laes Fixes: 82f8582feef4 ("ARM: dts: sun4i: Add DRAM

Re: [PATCH 1/2] ARM: sun4i: dt: Enable dram gate 5 (tve0 clock) for simplefb TV output

On Fri, Mar 25, 2016 at 2:08 AM, Priit Laes wrote: > From: Priit Laes > > Seems like dram_gate 5 was forgotten when DRAM gate driver was added. > > Enable it. > > Signed-off-by: Priit Laes Fixes: 82f8582feef4 ("ARM: dts: sun4i: Add DRAM gates") Thanks! > --- >

4.4: INFO: rcu_sched self-detected stall on CPU

Hi all, Firstly, I've cross-posted this to xen-devel and the lkml - as this problem seems to only exist when using kernel 4.4 as a Xen DomU kernel. I have also CC'ed Greg KH for his awesome insight as maintainer. Please CC myself into replies - as I'm not a member of the kernel mailing list - I

4.4: INFO: rcu_sched self-detected stall on CPU

Hi all, Firstly, I've cross-posted this to xen-devel and the lkml - as this problem seems to only exist when using kernel 4.4 as a Xen DomU kernel. I have also CC'ed Greg KH for his awesome insight as maintainer. Please CC myself into replies - as I'm not a member of the kernel mailing list - I

[PATCH v2] netpoll: Fix extra refcount release in netpoll_cleanup()

netpoll_setup() does a dev_hold() on np->dev, the netpoll device. If it fails, it correctly does a dev_put() but leaves np->dev set. If we call netpoll_cleanup() after the failure, np->dev is still set so we do another dev_put(), which decrements the refcount an extra time. It's questionable to

[PATCH v2] netpoll: Fix extra refcount release in netpoll_cleanup()

netpoll_setup() does a dev_hold() on np->dev, the netpoll device. If it fails, it correctly does a dev_put() but leaves np->dev set. If we call netpoll_cleanup() after the failure, np->dev is still set so we do another dev_put(), which decrements the refcount an extra time. It's questionable to

Re: [PATCH 0/5] drivers/mtd: make several functions return bool

ccing: Brian and Richard Hi Yao, Is that really necessary? I am not sure how much benefit we can achieve from this change. Could you explain more? Yang On 03/25/2016 10:41 AM, Yaowei Bai wrote: This series only make several funcitons return bool to improve readability, no other

Re: [PATCH 0/5] drivers/mtd: make several functions return bool

ccing: Brian and Richard Hi Yao, Is that really necessary? I am not sure how much benefit we can achieve from this change. Could you explain more? Yang On 03/25/2016 10:41 AM, Yaowei Bai wrote: This series only make several funcitons return bool to improve readability, no other

[PATCH net-next] phy: keep the BCMR_LOOPBACK bit while setup forced mode

When tested the PHY SGMII Loopback,: 1.set the LOOPBACK bit, 2.set the autoneg to AUTONEG_DISABLE, it calls the genphy_setup_forced which will clear the bit. So just keep the LOOPBACK bit while setup forced mode. Signed-off-by: Weidong Wang ---

[PATCH net-next] phy: keep the BCMR_LOOPBACK bit while setup forced mode

When tested the PHY SGMII Loopback,: 1.set the LOOPBACK bit, 2.set the autoneg to AUTONEG_DISABLE, it calls the genphy_setup_forced which will clear the bit. So just keep the LOOPBACK bit while setup forced mode. Signed-off-by: Weidong Wang --- drivers/net/phy/phy_device.c | 2 ++ 1 file

[PATCH 2/2] staging: dgnc: fix Logical continuations should be on the

fix checkpatch.pl warning about 'Logical continuations should be on the previous line' in dgnc_neo.c file. I think the 'force' need to check first, because if the 'force' is true, it doesn't need to call another function call. Signed-off-by: Daeseok Youn ---

[PATCH 2/2] staging: dgnc: fix Logical continuations should be on the

fix checkpatch.pl warning about 'Logical continuations should be on the previous line' in dgnc_neo.c file. I think the 'force' need to check first, because if the 'force' is true, it doesn't need to call another function call. Signed-off-by: Daeseok Youn --- drivers/staging/dgnc/dgnc_neo.c | 4

Re: [PATCH 0/2] arm64: cpuidle: make arm_cpuidle_suspend() more efficient

Hi Lorenzo, On Thu, 24 Mar 2016 16:44:19 + Lorenzo Pieralisi wrote: > On Thu, Mar 24, 2016 at 09:18:53PM +0800, Jisheng Zhang wrote: > > Hi Will, > > > > On Thu, 24 Mar 2016 11:15:07 + Will Deacon wrote: > > > > > On Thu, Mar 24, 2016 at 01:08:48PM +0800,

Re: [PATCH 0/2] arm64: cpuidle: make arm_cpuidle_suspend() more efficient

Hi Lorenzo, On Thu, 24 Mar 2016 16:44:19 + Lorenzo Pieralisi wrote: > On Thu, Mar 24, 2016 at 09:18:53PM +0800, Jisheng Zhang wrote: > > Hi Will, > > > > On Thu, 24 Mar 2016 11:15:07 + Will Deacon wrote: > > > > > On Thu, Mar 24, 2016 at 01:08:48PM +0800, Jisheng Zhang wrote: > >

[PATCH 1/2] staging: dgnc: fix 'line over 80 characters'

fix checkpatch.pl warning about 'line over 80 characters' in dgnc_neo.c Signed-off-by: Daeseok Youn --- drivers/staging/dgnc/dgnc_neo.c | 66 +++-- 1 file changed, 44 insertions(+), 22 deletions(-) diff --git

[PATCH 1/2] staging: dgnc: fix 'line over 80 characters'

fix checkpatch.pl warning about 'line over 80 characters' in dgnc_neo.c Signed-off-by: Daeseok Youn --- drivers/staging/dgnc/dgnc_neo.c | 66 +++-- 1 file changed, 44 insertions(+), 22 deletions(-) diff --git a/drivers/staging/dgnc/dgnc_neo.c

[PATCH 1/5] drivers/mtd: mtd_is_partition can be boolean

This patch makes mtd_is_partition return bool to improve readability due to this particular function only using either one or zero as its return value. No functional change. Signed-off-by: Yaowei Bai --- drivers/mtd/mtdpart.c | 6 +++---

[PATCH 2/5] drivers/mtd: cfi_interleave_supported can be boolean

This patch makes cfi_interleave_supported return bool due to this particular function only using either one or zero as its return value. No functional change. Signed-off-by: Yaowei Bai --- include/linux/mtd/cfi.h | 6 +++--- 1 file changed, 3 insertions(+), 3

[PATCH 3/5] drivers/mtd: map_bankwidth_supported can be boolean

This patch makes map_bankwidth_supported return bool due to this particular function only using either one or zero as its return value. No functional change. Signed-off-by: Yaowei Bai --- include/linux/mtd/map.h | 6 +++--- 1 file changed, 3 insertions(+), 3

[PATCH 1/5] drivers/mtd: mtd_is_partition can be boolean

This patch makes mtd_is_partition return bool to improve readability due to this particular function only using either one or zero as its return value. No functional change. Signed-off-by: Yaowei Bai --- drivers/mtd/mtdpart.c | 6 +++--- include/linux/mtd/partitions.h | 2 +- 2 files

[PATCH 2/5] drivers/mtd: cfi_interleave_supported can be boolean

This patch makes cfi_interleave_supported return bool due to this particular function only using either one or zero as its return value. No functional change. Signed-off-by: Yaowei Bai --- include/linux/mtd/cfi.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git

[PATCH 3/5] drivers/mtd: map_bankwidth_supported can be boolean

This patch makes map_bankwidth_supported return bool due to this particular function only using either one or zero as its return value. No functional change. Signed-off-by: Yaowei Bai --- include/linux/mtd/map.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git

[PATCH 5/5] drivers/mtd/nand: nand_opcode_8bits can be boolean

This patch makes nand_opcode_8bits return bool due to this particular function only using either one or zero as its return value. No functional change. Signed-off-by: Yaowei Bai --- include/linux/mtd/nand.h | 6 +++--- 1 file changed, 3 insertions(+), 3

[PATCH 5/5] drivers/mtd/nand: nand_opcode_8bits can be boolean

This patch makes nand_opcode_8bits return bool due to this particular function only using either one or zero as its return value. No functional change. Signed-off-by: Yaowei Bai --- include/linux/mtd/nand.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git

[PATCH 0/5] drivers/mtd: make several functions return bool

This series only make several funcitons return bool to improve readability, no other funcitonal changes. Yaowei Bai (5): drivers/mtd: mtd_is_partition can be boolean drivers/mtd: cfi_interleave_supported can be boolean drivers/mtd: map_bankwidth_supported can be boolean drivers/mtd:

[PATCH 4/5] drivers/mtd: mtd_nand_has_bch can be boolean

This patch makes mtd_nand_has_bch return bool to improve readability due to this particular function only using either one or zero as its return value. No functional change. Signed-off-by: Yaowei Bai --- include/linux/mtd/nand_bch.h | 4 ++-- 1 file changed, 2

[PATCH 0/5] drivers/mtd: make several functions return bool

This series only make several funcitons return bool to improve readability, no other funcitonal changes. Yaowei Bai (5): drivers/mtd: mtd_is_partition can be boolean drivers/mtd: cfi_interleave_supported can be boolean drivers/mtd: map_bankwidth_supported can be boolean drivers/mtd:

[PATCH 4/5] drivers/mtd: mtd_nand_has_bch can be boolean

This patch makes mtd_nand_has_bch return bool to improve readability due to this particular function only using either one or zero as its return value. No functional change. Signed-off-by: Yaowei Bai --- include/linux/mtd/nand_bch.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)

Re: linux-next: Tree for Mar 24 (events/amd/power)

On Thu, Mar 24, 2016 at 10:05:03AM -0700, Randy Dunlap wrote: > On 03/23/16 19:09, Stephen Rothwell wrote: > > Hi all, > > > > Please do not add any v4.7 related material to your linux-next included > > trees until after v4.6-rc1 is released. > > > > Changes since 20160323: > > > > on i386: >

Re: linux-next: Tree for Mar 24 (events/amd/power)

On Thu, Mar 24, 2016 at 10:05:03AM -0700, Randy Dunlap wrote: > On 03/23/16 19:09, Stephen Rothwell wrote: > > Hi all, > > > > Please do not add any v4.7 related material to your linux-next included > > trees until after v4.6-rc1 is released. > > > > Changes since 20160323: > > > > on i386: >

[RFC PATCH V2 1/2] vhost: convert pre sorted vhost memory array to interval tree

Current pre-sorted memory region array has some limitations for future device IOTLB conversion: 1) need extra work for adding and removing a single region, and it's expected to be slow because of sorting or memory re-allocation. 2) need extra work of removing a large range which may intersect

[RFC PATCH V2 1/2] vhost: convert pre sorted vhost memory array to interval tree

Current pre-sorted memory region array has some limitations for future device IOTLB conversion: 1) need extra work for adding and removing a single region, and it's expected to be slow because of sorting or memory re-allocation. 2) need extra work of removing a large range which may intersect

[RFC PATCH V2 2/2] vhost: device IOTLB API

This patch tries to implement an device IOTLB for vhost. This could be used with for co-operation with userspace(qemu) implementation of DMA remapping. The idea is simple. When vhost meets an IOTLB miss, it will request the assistance of userspace to do the translation, this is done through: -

[RFC PATCH V2 0/2] basic device IOTLB support

This patch tries to implement an device IOTLB for vhost. This could be used with for co-operation with userspace(qemu) implementation of iommu for a secure DMA environment (DMAR) in guest. The idea is simple. When vhost meets an IOTLB miss, it will request the assistance of userspace to do the

[RFC PATCH V2 2/2] vhost: device IOTLB API

This patch tries to implement an device IOTLB for vhost. This could be used with for co-operation with userspace(qemu) implementation of DMA remapping. The idea is simple. When vhost meets an IOTLB miss, it will request the assistance of userspace to do the translation, this is done through: -

[RFC PATCH V2 0/2] basic device IOTLB support

This patch tries to implement an device IOTLB for vhost. This could be used with for co-operation with userspace(qemu) implementation of iommu for a secure DMA environment (DMAR) in guest. The idea is simple. When vhost meets an IOTLB miss, it will request the assistance of userspace to do the

Re: [PATCH 4/3] rtmutex: Avoid barrier in rt_mutex_handle_deadlock

Adding a few more Cc's for bcache. On Tue, 22 Mar 2016, Peter Zijlstra wrote: On Mon, Mar 21, 2016 at 11:16:22AM -0700, Davidlohr Bueso wrote: +/* + * Helpers for modifying the state of either the current task, or a foreign + * task. Each of these calls come in both full barrier and weak

Re: [PATCH 4/3] rtmutex: Avoid barrier in rt_mutex_handle_deadlock

Adding a few more Cc's for bcache. On Tue, 22 Mar 2016, Peter Zijlstra wrote: On Mon, Mar 21, 2016 at 11:16:22AM -0700, Davidlohr Bueso wrote: +/* + * Helpers for modifying the state of either the current task, or a foreign + * task. Each of these calls come in both full barrier and weak

[PATCH] ARM: uniphier: drop weird sizeof()

My intention was to ioremap a 4-byte register. Coincidentally enough, sizeof(SZ_4) equals to SZ_4, but this code is weird anyway. Signed-off-by: Masahiro Yamada --- arch/arm/mach-uniphier/platsmp.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

[PATCH] ARM: uniphier: drop weird sizeof()

My intention was to ioremap a 4-byte register. Coincidentally enough, sizeof(SZ_4) equals to SZ_4, but this code is weird anyway. Signed-off-by: Masahiro Yamada --- arch/arm/mach-uniphier/platsmp.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 2/2] drivers/ata: make ata_using_udma return directly and bool

This patch makes ata_using_udma return bool due to this particular function only using either one or zero as its return value. This patch also makes ata_using_udma return directly by removing if condition. No functional change. Signed-off-by: Yaowei Bai ---

[PATCH 2/2] drivers/ata: make ata_using_udma return directly and bool

This patch makes ata_using_udma return bool due to this particular function only using either one or zero as its return value. This patch also makes ata_using_udma return directly by removing if condition. No functional change. Signed-off-by: Yaowei Bai --- include/linux/libata.h | 6 ++

[PATCH 1/2] drivers/ata: delete unused ata_using_mwdma function

There's no user of ata_using_mwdma since introduced by commit b15b3ebae ("libata: Fix a large collection of DMA mode mismatches") in 2008, so remove it. Signed-off-by: Yaowei Bai --- include/linux/libata.h | 7 --- 1 file changed, 7 deletions(-) diff --git

[PATCH 1/2] drivers/ata: delete unused ata_using_mwdma function

There's no user of ata_using_mwdma since introduced by commit b15b3ebae ("libata: Fix a large collection of DMA mode mismatches") in 2008, so remove it. Signed-off-by: Yaowei Bai --- include/linux/libata.h | 7 --- 1 file changed, 7 deletions(-) diff --git a/include/linux/libata.h

Re: [PATCH v2] phy: rcar-gen3-usb2, rcar-gen2: Use ARCH_RENESAS

On Mon, Mar 07, 2016 at 09:01:48AM +0100, Geert Uytterhoeven wrote: > On Mon, Mar 7, 2016 at 2:14 AM, Simon Horman > wrote: > > Make use of ARCH_RENESAS in place of ARCH_SHMOBILE. > > A now redundant dependency on OF is also dropped. > > > > This is part of an ongoing

Re: [PATCH v2] phy: rcar-gen3-usb2, rcar-gen2: Use ARCH_RENESAS

On Mon, Mar 07, 2016 at 09:01:48AM +0100, Geert Uytterhoeven wrote: > On Mon, Mar 7, 2016 at 2:14 AM, Simon Horman > wrote: > > Make use of ARCH_RENESAS in place of ARCH_SHMOBILE. > > A now redundant dependency on OF is also dropped. > > > > This is part of an ongoing process to migrate from

Re: [PATCH 1/6] block: ensure we don't truncate top bits of the request command flags

On 03/22/2016 02:01 PM, Jens Axboe wrote: > On 03/22/2016 12:59 PM, Christoph Hellwig wrote: >> On Tue, Mar 22, 2016 at 11:55:15AM -0600, Jens Axboe wrote: >>> Some of the flags that we want to use from the make_request_fn path >>> are now larger than 32-bit, so change the functions involved to

Re: [PATCH 1/6] block: ensure we don't truncate top bits of the request command flags

On 03/22/2016 02:01 PM, Jens Axboe wrote: > On 03/22/2016 12:59 PM, Christoph Hellwig wrote: >> On Tue, Mar 22, 2016 at 11:55:15AM -0600, Jens Axboe wrote: >>> Some of the flags that we want to use from the make_request_fn path >>> are now larger than 32-bit, so change the functions involved to

Re: [PATCH v3 0/2] phy: rcar-gen2, rcar-gen3-usb2: add fallback binding

On Mon, Mar 07, 2016 at 10:58:39AM +0900, Simon Horman wrote: > Add fallback compatibility strings for rcar phy drivers. > > In the case of Renesas R-Car hardware we know that there are generations of > SoCs, e.g. Gen 2 and Gen 3. But beyond that its not clear what the > relationship between IP

Re: [PATCH v3 0/2] phy: rcar-gen2, rcar-gen3-usb2: add fallback binding

On Mon, Mar 07, 2016 at 10:58:39AM +0900, Simon Horman wrote: > Add fallback compatibility strings for rcar phy drivers. > > In the case of Renesas R-Car hardware we know that there are generations of > SoCs, e.g. Gen 2 and Gen 3. But beyond that its not clear what the > relationship between IP

[PATCH] x86/cpu: add some advanced power management bits

Bit 11 of CPUID 8000_0007 edx is processor feedback interface. Bit 12 of CPUID 8000_0007 edx is accumulated power. So this patch fixes the output of cpuinfo, and add some new names to make it more meaningful. Reported-by: Borislav Petkov Signed-off-by: Huang Rui

[PATCH] x86/cpu: add some advanced power management bits

Bit 11 of CPUID 8000_0007 edx is processor feedback interface. Bit 12 of CPUID 8000_0007 edx is accumulated power. So this patch fixes the output of cpuinfo, and add some new names to make it more meaningful. Reported-by: Borislav Petkov Signed-off-by: Huang Rui ---

[PATCH] fs/vfs: improve __mnt_is_readonly

This patch refactors __mnt_is_readonly and makes it return bool to improve readability due to this particular function only using either one or zero as its return value. No functional change. Signed-off-by: Yaowei Bai --- fs/namespace.c| 9 +++--

[PATCH] fs/vfs: improve __mnt_is_readonly

This patch refactors __mnt_is_readonly and makes it return bool to improve readability due to this particular function only using either one or zero as its return value. No functional change. Signed-off-by: Yaowei Bai --- fs/namespace.c| 9 +++-- include/linux/mount.h | 2 +- 2

  1   2   3   4   5   6   7   8   9   10   >