Re: [PATCH 0/3] sched: Fix wakeup preemption regression

On Tue, 2016-05-10 at 19:43 +0200, Peter Zijlstra wrote: > Mike, Pavan, could you guys please confirm? Plugging the series into master.today, all seems peachy on my end. -Mike

Re: [PATCH 0/3] sched: Fix wakeup preemption regression

On Tue, 2016-05-10 at 19:43 +0200, Peter Zijlstra wrote: > Mike, Pavan, could you guys please confirm? Plugging the series into master.today, all seems peachy on my end. -Mike

[PATCH 6/8] ARM: dts: AM437X-SK-EVM: Remove redundant regulator compatibles

With the device tree parsing using the regulator framework there is a no longer a need for separate compatibles for individual regulator nodes. Hence removing them all. Signed-off-by: Keerthy --- arch/arm/boot/dts/am437x-sk-evm.dts | 5 - 1 file changed, 5 deletions(-)

[PATCH 8/8] ARM: dts: AM43X-EPOS-EVM: Remove redundant regulator compatibles

With the device tree parsing using the regulator framework there is a no longer a need for separate compatibles for individual regulator nodes. Hence removing them all. Signed-off-by: Keerthy --- arch/arm/boot/dts/am43x-epos-evm.dts | 7 --- 1 file changed, 7 deletions(-)

[PATCH 6/8] ARM: dts: AM437X-SK-EVM: Remove redundant regulator compatibles

With the device tree parsing using the regulator framework there is a no longer a need for separate compatibles for individual regulator nodes. Hence removing them all. Signed-off-by: Keerthy --- arch/arm/boot/dts/am437x-sk-evm.dts | 5 - 1 file changed, 5 deletions(-) diff --git

[PATCH 8/8] ARM: dts: AM43X-EPOS-EVM: Remove redundant regulator compatibles

With the device tree parsing using the regulator framework there is a no longer a need for separate compatibles for individual regulator nodes. Hence removing them all. Signed-off-by: Keerthy --- arch/arm/boot/dts/am43x-epos-evm.dts | 7 --- 1 file changed, 7 deletions(-) diff --git

[PATCH 0/8] regulator: tps65218: Clean ups

The series cleans up mainly the regulator driver and implements the device tree parsing using the regulator framework. Removes all the redundant compatibles for the individual regulators. One of the patch removes redundant read wrapper and makes use of regmap_read wherever necessary. The series

[PATCH 3/8] mfd: tps65218: Use mfd_add_devices instead of of_platform_populate

mfd_add_devices enables parsing device tree nodes without compatibles for child nodes. Replace of_platform_populate with mfd_add_devices. Signed-off-by: Keerthy --- drivers/mfd/tps65218.c | 10 -- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git

[PATCH 5/8] ARM: dts: AM437X-GP-EVM: Remove redundant regulator compatibles

With the device tree parsing using the regulator framework there is a no longer a need for separate compatibles for individual regulator nodes. Hence removing them all. Signed-off-by: Keerthy --- arch/arm/boot/dts/am437x-gp-evm.dts | 6 -- 1 file changed, 6 deletions(-)

[PATCH 0/8] regulator: tps65218: Clean ups

The series cleans up mainly the regulator driver and implements the device tree parsing using the regulator framework. Removes all the redundant compatibles for the individual regulators. One of the patch removes redundant read wrapper and makes use of regmap_read wherever necessary. The series

[PATCH 3/8] mfd: tps65218: Use mfd_add_devices instead of of_platform_populate

mfd_add_devices enables parsing device tree nodes without compatibles for child nodes. Replace of_platform_populate with mfd_add_devices. Signed-off-by: Keerthy --- drivers/mfd/tps65218.c | 10 -- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/drivers/mfd/tps65218.c

[PATCH 5/8] ARM: dts: AM437X-GP-EVM: Remove redundant regulator compatibles

With the device tree parsing using the regulator framework there is a no longer a need for separate compatibles for individual regulator nodes. Hence removing them all. Signed-off-by: Keerthy --- arch/arm/boot/dts/am437x-gp-evm.dts | 6 -- 1 file changed, 6 deletions(-) diff --git

Re: [PATCH] ARM: dts: exynos: Only Odroid XU3-family boards use DTSI with CPU thermal nodes

On 05/10/2016 09:45 PM, Anand Moon wrote: > Hi Krzysztof, > > Sorry I am not able to explain my self clearly. > But I have once gain tested these changes. > > Only could you append with following changes. > > +

Re: [PATCH] ARM: dts: exynos: Only Odroid XU3-family boards use DTSI with CPU thermal nodes

On 05/10/2016 09:45 PM, Anand Moon wrote: > Hi Krzysztof, > > Sorry I am not able to explain my self clearly. > But I have once gain tested these changes. > > Only could you append with following changes. > > +

Re: [PATCH] x86/extable: ensure entries are swapped completely when sorting

On 10 May 2016 at 23:07, Mathias Krause wrote: > The x86 exception table sorting was changed in commit 29934b0fb8ff > ("x86/extable: use generic search and sort routines") to use the arch > independent code in lib/extable.c. However, the patch was mangled > somehow on its

Re: [PATCH] x86/extable: ensure entries are swapped completely when sorting

On 10 May 2016 at 23:07, Mathias Krause wrote: > The x86 exception table sorting was changed in commit 29934b0fb8ff > ("x86/extable: use generic search and sort routines") to use the arch > independent code in lib/extable.c. However, the patch was mangled > somehow on its way into the kernel from

[PATCH 1/2] ARM: dts: sun6i: primo81: Drop constraints on dc1sw regulator

This is the same issue fixed in commit dcf5341f0150 ("ARM: dts: sun8i-q8-common: Do not set constraints on dc1sw regulator"). Commit message copied: dc1sw is an on/off only regulator and as such it cannot have constraints. This is a limitation of the kernel regulator implementation which

[PATCH 1/2] ARM: dts: sun6i: primo81: Drop constraints on dc1sw regulator

This is the same issue fixed in commit dcf5341f0150 ("ARM: dts: sun8i-q8-common: Do not set constraints on dc1sw regulator"). Commit message copied: dc1sw is an on/off only regulator and as such it cannot have constraints. This is a limitation of the kernel regulator implementation which

[PATCH 0/2] ARM: dts: sun6i: Drop constraints on dc1sw regulator

Hi Arnd, Olof, Here are 2 last minute fixes for 4.6. The 2 patches drop constaints on the dc1sw regulator for 2 A31s tablets. I checked with Maxime and he said to send them directly to you. The issue was first brought up and fixed for A23/A33 Q8 tablets in commit dcf5341f0150 ("ARM: dts:

[PATCH 0/2] ARM: dts: sun6i: Drop constraints on dc1sw regulator

Hi Arnd, Olof, Here are 2 last minute fixes for 4.6. The 2 patches drop constaints on the dc1sw regulator for 2 A31s tablets. I checked with Maxime and he said to send them directly to you. The issue was first brought up and fixed for A23/A33 Q8 tablets in commit dcf5341f0150 ("ARM: dts:

[PATCH 2/2] ARM: dts: sun6i: yones-toptech-bs1078-v2: Drop constraints on dc1sw regulator

This is the same issue fixed in commit dcf5341f0150 ("ARM: dts: sun8i-q8-common: Do not set constraints on dc1sw regulator"). Commit message copied: dc1sw is an on/off only regulator and as such it cannot have constraints. This is a limitation of the kernel regulator implementation which

[PATCH 2/2] ARM: dts: sun6i: yones-toptech-bs1078-v2: Drop constraints on dc1sw regulator

This is the same issue fixed in commit dcf5341f0150 ("ARM: dts: sun8i-q8-common: Do not set constraints on dc1sw regulator"). Commit message copied: dc1sw is an on/off only regulator and as such it cannot have constraints. This is a limitation of the kernel regulator implementation which

linux-next: Tree for May 11

Hi all, Changes since 20160510: The vfs tree gained a conflict against the overlayfs tree. The net-next tree gained a conflict against the net tree and lost its build failure. The sound-asoc tree gained a build failure for which I applied a fix patch. The dt-rh tree gained a conflict against

linux-next: Tree for May 11

Hi all, Changes since 20160510: The vfs tree gained a conflict against the overlayfs tree. The net-next tree gained a conflict against the net tree and lost its build failure. The sound-asoc tree gained a build failure for which I applied a fix patch. The dt-rh tree gained a conflict against

Re: [PATCH] cfg80211/nl80211: add wifi tx power mode switching support

On Fri, May 6, 2016 at 4:19 PM, Wei-Ning Huang wrote: > On Fri, May 6, 2016 at 12:07 AM, Dan Williams wrote: >> >> On Thu, 2016-05-05 at 14:44 +0800, Wei-Ning Huang wrote: >> > Recent new hardware has the ability to switch between tablet mode and >> >

Re: [PATCH] cfg80211/nl80211: add wifi tx power mode switching support

On Fri, May 6, 2016 at 4:19 PM, Wei-Ning Huang wrote: > On Fri, May 6, 2016 at 12:07 AM, Dan Williams wrote: >> >> On Thu, 2016-05-05 at 14:44 +0800, Wei-Ning Huang wrote: >> > Recent new hardware has the ability to switch between tablet mode and >> > clamshell mode. To optimize WiFi

Re: [PATCH 1/3] intel_pstate: Clarify average performance computation

On Tue, 2016-05-10 at 22:57 +0200, Rafael J. Wysocki wrote: > > > > [...] > --- > From: Rafael J. Wysocki > Subject: [PATCH] intel_pstate: Clarify average performance > computation > > The core_pct_busy field of struct sample actually contains the > average

Re: [PATCH 1/3] intel_pstate: Clarify average performance computation

On Tue, 2016-05-10 at 22:57 +0200, Rafael J. Wysocki wrote: > > > > [...] > --- > From: Rafael J. Wysocki > Subject: [PATCH] intel_pstate: Clarify average performance > computation > > The core_pct_busy field of struct sample actually contains the > average performace during the last sampling

Re: [RFC][PATCH 5/7] sched: Rewrite select_idle_siblings()

On Mon, May 09, 2016 at 12:48:12PM +0200, Peter Zijlstra wrote: > +/* > + * Scan the LLC domain for idle CPUs; this is dynamically regulated by > + * comparing the average scan cost (tracked in sd->avg_scan_cost) against the tracked in this_sd->avg_scan_cost

Re: [RFC][PATCH 5/7] sched: Rewrite select_idle_siblings()

On Mon, May 09, 2016 at 12:48:12PM +0200, Peter Zijlstra wrote: > +/* > + * Scan the LLC domain for idle CPUs; this is dynamically regulated by > + * comparing the average scan cost (tracked in sd->avg_scan_cost) against the tracked in this_sd->avg_scan_cost

Re: [PATCH v2] mailbox: pcc: Support HW-Reduced Communication Subspace Type 2

Hi Ashwin, Thanks for your review ! On Tue, May 10, 2016 at 5:00 AM, Ashwin Chaugule wrote: > Hello, > > On 6 May 2016 at 14:38, Hoan Tran wrote: >> From: hotran >> >> ACPI 6.1 has a PCC HW-Reduced Communication Subspace Type 2

Re: [PATCH v2] mailbox: pcc: Support HW-Reduced Communication Subspace Type 2

Hi Ashwin, Thanks for your review ! On Tue, May 10, 2016 at 5:00 AM, Ashwin Chaugule wrote: > Hello, > > On 6 May 2016 at 14:38, Hoan Tran wrote: >> From: hotran >> >> ACPI 6.1 has a PCC HW-Reduced Communication Subspace Type 2 intended for >> use on HW-Reduce ACPI Platform, which requires

Re: [PATCH v6 00/13] x86/xsaves: Fix XSAVES issues

On Tue, May 10, 2016 at 04:29:52PM -0700, Yu-cheng Yu wrote: > XSAVES is a kernel-mode instruction. It offers a compacted format and > memory-write optimization. These patches fix issues in the first > implementation. > > Changes since Version 5: Please, for the future, do send your patchset

Re: sched: tweak select_idle_sibling to look for idle threads

On Wed, 2016-05-11 at 03:16 +0800, Yuyang Du wrote: > On Tue, May 10, 2016 at 05:26:05PM +0200, Mike Galbraith wrote: > > On Tue, 2016-05-10 at 09:49 +0200, Mike Galbraith wrote: > > > > > Only whacking > > > cfs_rq_runnable_load_avg() with a rock makes schbench -m -t > > > -a work well.

Re: [PATCH v6 00/13] x86/xsaves: Fix XSAVES issues

On Tue, May 10, 2016 at 04:29:52PM -0700, Yu-cheng Yu wrote: > XSAVES is a kernel-mode instruction. It offers a compacted format and > memory-write optimization. These patches fix issues in the first > implementation. > > Changes since Version 5: Please, for the future, do send your patchset

Re: sched: tweak select_idle_sibling to look for idle threads

On Wed, 2016-05-11 at 03:16 +0800, Yuyang Du wrote: > On Tue, May 10, 2016 at 05:26:05PM +0200, Mike Galbraith wrote: > > On Tue, 2016-05-10 at 09:49 +0200, Mike Galbraith wrote: > > > > > Only whacking > > > cfs_rq_runnable_load_avg() with a rock makes schbench -m -t > > > -a work well.

Re: [PATCH] Staging: wlan-ng: fix comments style

On Tue, May 10, 2016 at 09:05:15PM -0400, YU Bo wrote: > Hi Greg, > On Mon, May 09, 2016 at 02:26:13PM +0200, Kroah-Hartman wrote: > > On Sun, May 08, 2016 at 10:45:16AM -0400, YU Bo wrote: > > > The patch fixed warning reported by checkpatch.pl: Block comments use a > > > trailing */ on a

Re: [PATCH] Staging: wlan-ng: fix comments style

On Tue, May 10, 2016 at 09:05:15PM -0400, YU Bo wrote: > Hi Greg, > On Mon, May 09, 2016 at 02:26:13PM +0200, Kroah-Hartman wrote: > > On Sun, May 08, 2016 at 10:45:16AM -0400, YU Bo wrote: > > > The patch fixed warning reported by checkpatch.pl: Block comments use a > > > trailing */ on a

Re: [PATCH -v2] x86/hweight: Get rid of the special calling convention

On Tue, May 10, 2016 at 03:30:48PM -0700, H. Peter Anvin wrote: > I didn't mean inline assembly. How does that matter? The problem is having as less insn bytes as possible and the minimal size we can do is issuing POPCNT everywhere which is 4 or 5 bytes. The alternatives then replace that with a

Re: [PATCH -v2] x86/hweight: Get rid of the special calling convention

On Tue, May 10, 2016 at 03:30:48PM -0700, H. Peter Anvin wrote: > I didn't mean inline assembly. How does that matter? The problem is having as less insn bytes as possible and the minimal size we can do is issuing POPCNT everywhere which is 4 or 5 bytes. The alternatives then replace that with a

[PATCH v8 8/8] i2c: rk3x: support fast-mode plus for rk3399

Signed-off-by: David Wu Reviewed-by: Douglas Anderson --- Change in v8: - None drivers/i2c/busses/i2c-rk3x.c | 21 + 1 file changed, 17 insertions(+), 4 deletions(-) diff --git a/drivers/i2c/busses/i2c-rk3x.c

[PATCH v8 8/8] i2c: rk3x: support fast-mode plus for rk3399

Signed-off-by: David Wu Reviewed-by: Douglas Anderson --- Change in v8: - None drivers/i2c/busses/i2c-rk3x.c | 21 + 1 file changed, 17 insertions(+), 4 deletions(-) diff --git a/drivers/i2c/busses/i2c-rk3x.c b/drivers/i2c/busses/i2c-rk3x.c index 25ed1ad..0ba25ee 100644

[PATCH v8 6/8] dt-bindings: i2c: rk3x: add support for rk3399

The bus clock and function clock are separated at rk3399, and others use one clock as the bus clock and function clock. Signed-off-by: David Wu Reviewed-by: Douglas Anderson --- Change in v8: - remove error description.

[PATCH v8 6/8] dt-bindings: i2c: rk3x: add support for rk3399

The bus clock and function clock are separated at rk3399, and others use one clock as the bus clock and function clock. Signed-off-by: David Wu Reviewed-by: Douglas Anderson --- Change in v8: - remove error description. Documentation/devicetree/bindings/i2c/i2c-rk3x.txt | 16 +---

[PATCH v8 7/8] i2c: rk3x: add i2c support for rk3399 soc

- new method to caculate i2c timings for rk3399: There was an timing issue about "repeated start" time at the I2C controller of version0, controller appears to drop SDA at .875x (7/8) programmed clk high. On version 1 of the controller, the rule(.875x) isn't enough to meet tSU;STA

[PATCH v8 7/8] i2c: rk3x: add i2c support for rk3399 soc

- new method to caculate i2c timings for rk3399: There was an timing issue about "repeated start" time at the I2C controller of version0, controller appears to drop SDA at .875x (7/8) programmed clk high. On version 1 of the controller, the rule(.875x) isn't enough to meet tSU;STA

[PATCH v8 5/8] i2c: rk3x: Move spec timing data to "static const" structs

The i2c timing specs are really just constant data. There's no reason to write code to init them, so move them out to structures. This not only is a cleaner solution but it will reduce code duplication when we introduce a new variant of rk3x_i2c_calc_divs() in a future patch. Signed-off-by:

[PATCH v8 5/8] i2c: rk3x: Move spec timing data to "static const" structs

The i2c timing specs are really just constant data. There's no reason to write code to init them, so move them out to structures. This not only is a cleaner solution but it will reduce code duplication when we introduce a new variant of rk3x_i2c_calc_divs() in a future patch. Signed-off-by:

Re: [GIT PULL] overlayfs fixes for 4.6-rc7

On Wed, May 11, 2016 at 01:23:42AM +0200, Miklos Szeredi wrote: > Hi Al, > > Hopefully this addresses your concerns. I couldn't find a better name for > lookup_hash(), after all it's just that. > > Please pull: > > git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git >

Re: [GIT PULL] overlayfs fixes for 4.6-rc7

On Wed, May 11, 2016 at 01:23:42AM +0200, Miklos Szeredi wrote: > Hi Al, > > Hopefully this addresses your concerns. I couldn't find a better name for > lookup_hash(), after all it's just that. > > Please pull: > > git://git.kernel.org/pub/scm/linux/kernel/git/mszeredi/vfs.git >

Re: [PATCH v2] mailbox: pcc: Support HW-Reduced Communication Subspace Type 2

Hi Alexey, On Tue, May 10, 2016 at 3:34 AM, Alexey Klimov wrote: > On Mon, May 09, 2016 at 10:38:24AM -0700, Hoan Tran wrote: >> Hi Alexey, >> >> On Mon, May 9, 2016 at 2:43 AM, Alexey Klimov wrote: >> > Hi Hoan, >> > >> > On Fri, May 06, 2016 at

Re: [PATCH v2] mailbox: pcc: Support HW-Reduced Communication Subspace Type 2

Hi Alexey, On Tue, May 10, 2016 at 3:34 AM, Alexey Klimov wrote: > On Mon, May 09, 2016 at 10:38:24AM -0700, Hoan Tran wrote: >> Hi Alexey, >> >> On Mon, May 9, 2016 at 2:43 AM, Alexey Klimov wrote: >> > Hi Hoan, >> > >> > On Fri, May 06, 2016 at 11:38:34AM -0700, Hoan Tran wrote: >> >> From:

[PATCH v8 0/8] add i2c driver supported for rk3399

There are three points differert from others: - new method to caculate i2c timings for rk3399 - pclk and function clk are separated at rk3399 - add fast-plus mode supported for rk3399 David Wu (8): i2c: rk3x: add documentation to fields in "struct rk3x_i2c" i2c: rk3x: use struct

[PATCH v8 0/8] add i2c driver supported for rk3399

There are three points differert from others: - new method to caculate i2c timings for rk3399 - pclk and function clk are separated at rk3399 - add fast-plus mode supported for rk3399 David Wu (8): i2c: rk3x: add documentation to fields in "struct rk3x_i2c" i2c: rk3x: use struct

[PATCH v8 4/8] i2c: rk3x: Change SoC data to not use array

Specifying the i2c SoC data in an array provides very little benefit and gets unwieldly / confusing as the array grows since the next bit of code needs to refer to elements in the array by their raw integral index. Let's just create a single 'static const' structure for each SoC so that we can

[PATCH v8 4/8] i2c: rk3x: Change SoC data to not use array

Specifying the i2c SoC data in an array provides very little benefit and gets unwieldly / confusing as the array grows since the next bit of code needs to refer to elements in the array by their raw integral index. Let's just create a single 'static const' structure for each SoC so that we can

[PATCH v8 1/8] i2c: rk3x: add documentation to fields in "struct rk3x_i2c"

Signed-off-by: David Wu Reviewed-by: Douglas Anderson --- Change in v8: - none drivers/i2c/busses/i2c-rk3x.c | 22 +- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/drivers/i2c/busses/i2c-rk3x.c

[PATCH v8 1/8] i2c: rk3x: add documentation to fields in "struct rk3x_i2c"

Signed-off-by: David Wu Reviewed-by: Douglas Anderson --- Change in v8: - none drivers/i2c/busses/i2c-rk3x.c | 22 +- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/drivers/i2c/busses/i2c-rk3x.c b/drivers/i2c/busses/i2c-rk3x.c index 80bed02..7e45d51 100644

[PATCH v8 3/8] i2c: rk3x: Remove redundant rk3x_i2c_clean_ipd()

Call rk3x_i2c_setup() before rk3x_i2c_start() and the last thing in setup was to clean the IPD, so no reason to do it at the beginning of start. Signed-off-by: David Wu Reviewed-by: Douglas Anderson --- Change in v8: - none

[PATCH v8 2/8] i2c: rk3x: use struct "rk3x_i2c_calced_timings"

The "div_high" and "div_low" values are always used together. Group them into a structure to make it easier to pass them both around. This structure also provides a place for future calculated timings. Signed-off-by: David Wu Reviewed-by: Douglas Anderson

[PATCH v8 3/8] i2c: rk3x: Remove redundant rk3x_i2c_clean_ipd()

Call rk3x_i2c_setup() before rk3x_i2c_start() and the last thing in setup was to clean the IPD, so no reason to do it at the beginning of start. Signed-off-by: David Wu Reviewed-by: Douglas Anderson --- Change in v8: - none drivers/i2c/busses/i2c-rk3x.c | 1 - 1 file changed, 1 deletion(-)

[PATCH v8 2/8] i2c: rk3x: use struct "rk3x_i2c_calced_timings"

The "div_high" and "div_low" values are always used together. Group them into a structure to make it easier to pass them both around. This structure also provides a place for future calculated timings. Signed-off-by: David Wu Reviewed-by: Douglas Anderson --- Change in v8: - add commit

Re: [PATCH v2] pinctrl: rockchip: fix pull setting error for rk3399

Caesar, On Tue, May 10, 2016 at 8:39 PM, Caesar Wang wrote: > From: David Wu > > This patch fixes the pinctrl pull bias setting, since the pull up/down > setting is the contrary for gpio0(just the gpio0a and gpio0b) and > gpio2(just the gpio2c and

Re: [PATCH v2] pinctrl: rockchip: fix pull setting error for rk3399

Caesar, On Tue, May 10, 2016 at 8:39 PM, Caesar Wang wrote: > From: David Wu > > This patch fixes the pinctrl pull bias setting, since the pull up/down > setting is the contrary for gpio0(just the gpio0a and gpio0b) and > gpio2(just the gpio2c and gpio2d). > > From the TRM said, the gpio0a pull

Re: [Intel-wired-lan] [PATCH] e1000e: prevent division by zero if TIMINCA is zero

Jarod Wilson wrote: On Fri, May 06, 2016 at 11:43:17PM +, Rustad, Mark D wrote: Denys Vlasenko wrote: Users report that under VMWare, er32(TIMINCA) returns zero. This causes division by zero at init time as follows: ==>incvalue =

Re: [Intel-wired-lan] [PATCH] e1000e: prevent division by zero if TIMINCA is zero

Jarod Wilson wrote: On Fri, May 06, 2016 at 11:43:17PM +, Rustad, Mark D wrote: Denys Vlasenko wrote: Users report that under VMWare, er32(TIMINCA) returns zero. This causes division by zero at init time as follows: ==>incvalue = er32(TIMINCA) &

Re: [PATCH 6/6] mpt3sas: Used "synchronize_irq()"API to synchronize timed-out IO & TMs

On Tue, May 10, 2016 at 6:41 PM, Tomas Henzl wrote: > On 6.5.2016 10:59, Chaitra P B wrote: >> Replaced mpt3sas_base_flush_reply_queues()with >> mpt3sas_base_sync_reply_irqs(),as mpt3sas_base_flush_reply_queues() >> skips over reply queues that are currently busy (i.e. being

Re: [PATCH 6/6] mpt3sas: Used "synchronize_irq()"API to synchronize timed-out IO & TMs

On Tue, May 10, 2016 at 6:41 PM, Tomas Henzl wrote: > On 6.5.2016 10:59, Chaitra P B wrote: >> Replaced mpt3sas_base_flush_reply_queues()with >> mpt3sas_base_sync_reply_irqs(),as mpt3sas_base_flush_reply_queues() >> skips over reply queues that are currently busy (i.e. being handled >> by

Re: [PATCH 2/2] dt-bindings: rockchip-dw-mshc: add rockchip,default-drv-phase

Hi, On Tue, May 10, 2016 at 7:50 PM, Shawn Lin wrote: >>> maybe. But I think 180(downside) is the better. > > > NAK my previous comments here. Downside is better for SRD, but won't > work for DDR mode. When running in DDR mode, we should use 90 instead. > > So let me

Re: [PATCH 2/2] dt-bindings: rockchip-dw-mshc: add rockchip,default-drv-phase

Hi, On Tue, May 10, 2016 at 7:50 PM, Shawn Lin wrote: >>> maybe. But I think 180(downside) is the better. > > > NAK my previous comments here. Downside is better for SRD, but won't > work for DDR mode. When running in DDR mode, we should use 90 instead. > > So let me elaborate a bit more here. >

Re: [RFC v2 PATCH 0/8] VFS:userns: support portable root filesystems

On Wed, 2016-05-11 at 01:53 +0100, Al Viro wrote: > On Tue, May 10, 2016 at 04:36:56PM -0700, James Bottomley wrote: > > +static int shiftfs_rename2(struct inode *olddir, struct dentry > > *old, > > + struct inode *newdir, struct dentry > > *new, > > +

Re: [RFC v2 PATCH 0/8] VFS:userns: support portable root filesystems

On Wed, 2016-05-11 at 01:53 +0100, Al Viro wrote: > On Tue, May 10, 2016 at 04:36:56PM -0700, James Bottomley wrote: > > +static int shiftfs_rename2(struct inode *olddir, struct dentry > > *old, > > + struct inode *newdir, struct dentry > > *new, > > +

RE: [PATCH] drivers: usb: dwc3 : Configure DMA properties and ops from DT

> -Original Message- > From: Felipe Balbi [mailto:felipe.ba...@linux.intel.com] > Sent: Wednesday, May 04, 2016 1:28 PM > To: Rajesh Bhagat ; linux-...@vger.kernel.org > Cc: linux-kernel@vger.kernel.org; gre...@linuxfoundation.org; Yang-Leo Li >

RE: [PATCH] drivers: usb: dwc3 : Configure DMA properties and ops from DT

> -Original Message- > From: Felipe Balbi [mailto:felipe.ba...@linux.intel.com] > Sent: Wednesday, May 04, 2016 1:28 PM > To: Rajesh Bhagat ; linux-...@vger.kernel.org > Cc: linux-kernel@vger.kernel.org; gre...@linuxfoundation.org; Yang-Leo Li > ; Sriram Dash ; Rajesh Bhagat > >

[PATCH v2] pinctrl: rockchip: fix pull setting error for rk3399

From: David Wu This patch fixes the pinctrl pull bias setting, since the pull up/down setting is the contrary for gpio0(just the gpio0a and gpio0b) and gpio2(just the gpio2c and gpio2d). >From the TRM said, the gpio0a pull polarity setting: gpio0a_p GPIO0A PE/PS

[PATCH v2] pinctrl: rockchip: fix pull setting error for rk3399

From: David Wu This patch fixes the pinctrl pull bias setting, since the pull up/down setting is the contrary for gpio0(just the gpio0a and gpio0b) and gpio2(just the gpio2c and gpio2d). >From the TRM said, the gpio0a pull polarity setting: gpio0a_p GPIO0A PE/PS programmation section, every

Re: [RFC 2/2] perf/core: change errno for sampling event not supported in hardware

On Mon, 9 May 2016, Vineet Gupta wrote: > On Monday 09 May 2016 07:24 PM, Vince Weaver wrote: > > On Mon, 9 May 2016, Vineet Gupta wrote: > > > >> This allows userspace to identify this case specifically from the > >> catch all error msg it prints currently. > >> > >> This is an ABI change > >

Re: [RFC 2/2] perf/core: change errno for sampling event not supported in hardware

On Mon, 9 May 2016, Vineet Gupta wrote: > On Monday 09 May 2016 07:24 PM, Vince Weaver wrote: > > On Mon, 9 May 2016, Vineet Gupta wrote: > > > >> This allows userspace to identify this case specifically from the > >> catch all error msg it prints currently. > >> > >> This is an ABI change > >

Re: linux-next: build failure after merge of the sound-asoc tree

On Wed, May 11, 2016 at 11:07:02AM +1000, Stephen Rothwell wrote: > Hi all, > > After merging the sound-asoc tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > sound/soc/intel/boards/bxt_rt298.c:257:3: error: unknown field 'be_id' > specified in initializer >.be_id

Re: linux-next: build failure after merge of the sound-asoc tree

On Wed, May 11, 2016 at 11:07:02AM +1000, Stephen Rothwell wrote: > Hi all, > > After merging the sound-asoc tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > sound/soc/intel/boards/bxt_rt298.c:257:3: error: unknown field 'be_id' > specified in initializer >.be_id

Re: [PATCH] dma: rcar-dmac: use list_add() on rcar_dmac_desc_put()

Hi Laurent, Vinod, > > > From: Kuninori Morimoto > > > > > > Current rcar_dmac_desc_put() is using list_add_tail() in order to > > > push used descriptor to list of free descriptors, and next DMA transfer > > > try to reuse it from this list. But because it is

[PATCH v2 0/4] perf script: fix duplicate symbols in db-export

Changes since v1: - fixed scripts/checkpatch.pl errors This patch set contains 3 fixes for duplicate symbol creation in the db-export implementation and one new symbol API required for the fixes. commit 9c7b37cd63d0 ("perf symbols: Fix handling of zero-length symbols.") already removed the

Re: [PATCH] dma: rcar-dmac: use list_add() on rcar_dmac_desc_put()

Hi Laurent, Vinod, > > > From: Kuninori Morimoto > > > > > > Current rcar_dmac_desc_put() is using list_add_tail() in order to > > > push used descriptor to list of free descriptors, and next DMA transfer > > > try to reuse it from this list. But because it is using *_tail(), > > > this reuse

[PATCH v2 0/4] perf script: fix duplicate symbols in db-export

Changes since v1: - fixed scripts/checkpatch.pl errors This patch set contains 3 fixes for duplicate symbol creation in the db-export implementation and one new symbol API required for the fixes. commit 9c7b37cd63d0 ("perf symbols: Fix handling of zero-length symbols.") already removed the

[PATCH v2 3/4] perf script: fix callchain addresses in db-export

Remove the call to map_ip, because it has already been called when assembling the callchain. Calling it a second time can result in incorrect addresses being used. This can have effects such as duplicate symbols being created and exported. Signed-off-by: Chris Phlipot ---

[PATCH v2 3/4] perf script: fix callchain addresses in db-export

Remove the call to map_ip, because it has already been called when assembling the callchain. Calling it a second time can result in incorrect addresses being used. This can have effects such as duplicate symbols being created and exported. Signed-off-by: Chris Phlipot ---

[PATCH v2 2/4] perf script: fix symbol insertion behavior in db-export

Use the dso__insert_symbol function instead of symbols__insert in order to properly update the dso symbol cache. If the cache is not updated, then duplicate symbols can be unintentionally created, inserted, and exported. This change prevents duplicate symbols from being exported due to

[PATCH v2 4/4] perf script: fix export of callchains with recursion in db-export

When an IP with an unresolved symbol occurs in the callchain more than once (ie. recursion), then duplicate symbols can be created because the callchain nodes are never updated after they are first created. To fix this issue we call dso__find_symbol whenever we encounter a NULL symbol, in case we

[PATCH v2 2/4] perf script: fix symbol insertion behavior in db-export

Use the dso__insert_symbol function instead of symbols__insert in order to properly update the dso symbol cache. If the cache is not updated, then duplicate symbols can be unintentionally created, inserted, and exported. This change prevents duplicate symbols from being exported due to

[PATCH v2 4/4] perf script: fix export of callchains with recursion in db-export

When an IP with an unresolved symbol occurs in the callchain more than once (ie. recursion), then duplicate symbols can be created because the callchain nodes are never updated after they are first created. To fix this issue we call dso__find_symbol whenever we encounter a NULL symbol, in case we

Re: [v10, 7/7] mmc: sdhci-of-esdhc: fix host version for T4240-R1.0-R2.0

On Thu, 2016-05-05 at 13:10 +0200, Arnd Bergmann wrote: > On Thursday 05 May 2016 09:41:32 Yangbo Lu wrote: > > > -Original Message- > > > From: Arnd Bergmann [mailto:a...@arndb.de] > > > Sent: Thursday, May 05, 2016 4:32 PM > > > To: linuxppc-...@lists.ozlabs.org > > > Cc: Yangbo Lu;

[PATCH v2 1/4] perf symbols: add dso__insert_symbol function

The current method for inserting symbols is to use the symbols__insert function. However symbols__insert does not update the dso symbol cache. This causes problems in the following scenario: 1. symbol not found at ip using dso__find_symbol 2. symbol inserted at ip using the existing

[PATCH v2 1/4] perf symbols: add dso__insert_symbol function

The current method for inserting symbols is to use the symbols__insert function. However symbols__insert does not update the dso symbol cache. This causes problems in the following scenario: 1. symbol not found at ip using dso__find_symbol 2. symbol inserted at ip using the existing

Re: [v10, 7/7] mmc: sdhci-of-esdhc: fix host version for T4240-R1.0-R2.0

On Thu, 2016-05-05 at 13:10 +0200, Arnd Bergmann wrote: > On Thursday 05 May 2016 09:41:32 Yangbo Lu wrote: > > > -Original Message- > > > From: Arnd Bergmann [mailto:a...@arndb.de] > > > Sent: Thursday, May 05, 2016 4:32 PM > > > To: linuxppc-...@lists.ozlabs.org > > > Cc: Yangbo Lu;

Re: [PATCH v2 5/5] vf610-soc: Add Vybrid SoC device tree binding documentation

On Mon, May 9, 2016 at 8:13 PM, Stefan Agner wrote: > On 2016-05-09 15:58, Rob Herring wrote: >> On Mon, May 9, 2016 at 1:25 PM, Stefan Agner wrote: >>> On 2016-05-09 10:14, Rob Herring wrote: On Thu, May 5, 2016 at 3:27 AM,

Re: [PATCH v2 5/5] vf610-soc: Add Vybrid SoC device tree binding documentation

On Mon, May 9, 2016 at 8:13 PM, Stefan Agner wrote: > On 2016-05-09 15:58, Rob Herring wrote: >> On Mon, May 9, 2016 at 1:25 PM, Stefan Agner wrote: >>> On 2016-05-09 10:14, Rob Herring wrote: On Thu, May 5, 2016 at 3:27 AM, wrote: > Hello Rob, > > On 16-05-03 21:30:26, Rob

Re: [PATCH 0/3] usb: USB Type-C Class and driver for UCSI

Heikki, On 05/06/2016 01:08 AM, Heikki Krogerus wrote: Hi, [ ... ] I don't have not made any new code for the class driver yet, but I'm attempting to prepare v2 next week. Would it make sense to send feedback about v1 now, or should I wait for v2 ? Thanks, Guenter

Re: [PATCH 0/3] usb: USB Type-C Class and driver for UCSI

Heikki, On 05/06/2016 01:08 AM, Heikki Krogerus wrote: Hi, [ ... ] I don't have not made any new code for the class driver yet, but I'm attempting to prepare v2 next week. Would it make sense to send feedback about v1 now, or should I wait for v2 ? Thanks, Guenter

Re: [PATCH 1/6] f2fs: support in batch multi blocks preallocation

On 2016/5/11 10:32, Jaegeuk Kim wrote: > On Wed, May 11, 2016 at 10:22:05AM +0800, Chao Yu wrote: >> On 2016/5/11 5:41, Jaegeuk Kim wrote: >>> + >>> + f2fs_wait_on_page_writeback(dn->node_page, NODE, true); >>> + >>> + for (; count > 0; dn->ofs_in_node++) { >>> + block_t blkaddr =

Re: [PATCH 1/6] f2fs: support in batch multi blocks preallocation

On 2016/5/11 10:32, Jaegeuk Kim wrote: > On Wed, May 11, 2016 at 10:22:05AM +0800, Chao Yu wrote: >> On 2016/5/11 5:41, Jaegeuk Kim wrote: >>> + >>> + f2fs_wait_on_page_writeback(dn->node_page, NODE, true); >>> + >>> + for (; count > 0; dn->ofs_in_node++) { >>> + block_t blkaddr =

  1   2   3   4   5   6   7   8   9   10   >