Re: [PATCHv2] serial: samsung: drop the spinlock around uart_write_wakeup

Hi Krzysztof, On 21 February 2016 at 07:07, Krzysztof Kozlowski wrote: > 2016-02-20 4:30 GMT+09:00 Peter Hurley : >> [ +cc Krzysztof Kozlowski ] >> >> On 02/18/2016 09:15 PM, Anand Moon wrote: >>> From: Anand Moon >>> >>>

Re: [PATCHv2] serial: samsung: drop the spinlock around uart_write_wakeup

Hi Krzysztof, On 21 February 2016 at 07:07, Krzysztof Kozlowski wrote: > 2016-02-20 4:30 GMT+09:00 Peter Hurley : >> [ +cc Krzysztof Kozlowski ] >> >> On 02/18/2016 09:15 PM, Anand Moon wrote: >>> From: Anand Moon >>> >>> drop the spin_unlock/lock around uart_write_wakeup to protect >>> write

Re: [PATCH v5 2/8] clk: rockchip: rk3036: fix and add node id for emac clock

Heiko, 在 2016年02月21日 10:26, Heiko Stuebner 写道: Hi Caesar, Xing, Am Dienstag, 2. Februar 2016, 11:48:19 schrieb Caesar Wang: From: zhengxing In the emac driver, we need to refer HCLK_MAC since there are only 3PLLs (APLL/GPLL/DPLL) on the rk3036, most clock are under

Re: [PATCH v5 2/8] clk: rockchip: rk3036: fix and add node id for emac clock

Heiko, 在 2016年02月21日 10:26, Heiko Stuebner 写道: Hi Caesar, Xing, Am Dienstag, 2. Februar 2016, 11:48:19 schrieb Caesar Wang: From: zhengxing In the emac driver, we need to refer HCLK_MAC since there are only 3PLLs (APLL/GPLL/DPLL) on the rk3036, most clock are under the GPLL, and it is

Re: [PATCH v5 2/8] clk: rockchip: rk3036: fix and add node id for emac clock

Hi Caesar, Xing, Am Dienstag, 2. Februar 2016, 11:48:19 schrieb Caesar Wang: > From: zhengxing > > In the emac driver, we need to refer HCLK_MAC since there are > only 3PLLs (APLL/GPLL/DPLL) on the rk3036, most clock are under the > GPLL, and it is unable to provide

Re: [PATCH v5 2/8] clk: rockchip: rk3036: fix and add node id for emac clock

Hi Caesar, Xing, Am Dienstag, 2. Februar 2016, 11:48:19 schrieb Caesar Wang: > From: zhengxing > > In the emac driver, we need to refer HCLK_MAC since there are > only 3PLLs (APLL/GPLL/DPLL) on the rk3036, most clock are under the > GPLL, and it is unable to provide the accurate rate for

Re: [PATCH v5 1/8] ARM: dts: rockchip: add hdmi/vop device node for rk3036

在 2016年02月21日 08:03, Heiko Stuebner 写道: Am Dienstag, 2. Februar 2016, 11:40:50 schrieb Caesar Wang: This patch adds the needed display info for rk3036 SOCs. The rk3036 support two overlay plane and one hwc plane, it supports IOMMU, and its IOMMU same as rk3288's. Meanwhile, add the inno hdmi

Re: [PATCH v5 1/8] ARM: dts: rockchip: add hdmi/vop device node for rk3036

在 2016年02月21日 08:03, Heiko Stuebner 写道: Am Dienstag, 2. Februar 2016, 11:40:50 schrieb Caesar Wang: This patch adds the needed display info for rk3036 SOCs. The rk3036 support two overlay plane and one hwc plane, it supports IOMMU, and its IOMMU same as rk3288's. Meanwhile, add the inno hdmi

[PATCH 1/2] cpufreq: governor: Fix race in dbs_update_util_handler()

From: Rafael J. Wysocki There is a scenarion that may lead to undesired results in dbs_update_util_handler(). Namely, if two CPUs sharing a policy enter the funtion at the same time, pass the sample delay check and then one of them is stalled until dbs_work_handler()

[PATCH 1/2] cpufreq: governor: Fix race in dbs_update_util_handler()

From: Rafael J. Wysocki There is a scenarion that may lead to undesired results in dbs_update_util_handler(). Namely, if two CPUs sharing a policy enter the funtion at the same time, pass the sample delay check and then one of them is stalled until dbs_work_handler() (queued up by the other

[PATCH 0/2] cpufreq: governor: Fixups on top of recent changes

Hi, Two fixups on top of recent cpufreq governor changes in the linux-next branch of linux-pm.git. [1/2] closes a tiny theoretical race in dbs_update_util_handler() that may lead to taking a sample prematurely in some weird cases. [2/2] removes an unnecessary function export.

[PATCH 2/2] cpufreq: governor: Make gov_set_update_util() static

From: Rafael J. Wysocki The gov_set_update_util() routine is only used internally by the common governor code and it doesn't need to be exported, so make it static. No functional changes. Signed-off-by: Rafael J. Wysocki ---

[PATCH 0/2] cpufreq: governor: Fixups on top of recent changes

Hi, Two fixups on top of recent cpufreq governor changes in the linux-next branch of linux-pm.git. [1/2] closes a tiny theoretical race in dbs_update_util_handler() that may lead to taking a sample prematurely in some weird cases. [2/2] removes an unnecessary function export.

[PATCH 2/2] cpufreq: governor: Make gov_set_update_util() static

From: Rafael J. Wysocki The gov_set_update_util() routine is only used internally by the common governor code and it doesn't need to be exported, so make it static. No functional changes. Signed-off-by: Rafael J. Wysocki --- drivers/cpufreq/cpufreq_governor.c |5 ++--- 1 file changed, 2

Re: [PATCH] btrfs: backref: Fixed checkpatch warning of over 80 characters

I apologize, I had my text editor set to a 4 space tab instead of 8 so I couldn't see this clearly. That's fixed now, and it won't happen again. Is this what you wanted? It seems to line up exactly like you proposed. On 02/20/2016 08:06 PM, Simon Quigley wrote: checkpatch.pl reported a

Re: [PATCH] btrfs: backref: Fixed checkpatch warning of over 80 characters

I apologize, I had my text editor set to a 4 space tab instead of 8 so I couldn't see this clearly. That's fixed now, and it won't happen again. Is this what you wanted? It seems to line up exactly like you proposed. On 02/20/2016 08:06 PM, Simon Quigley wrote: checkpatch.pl reported a

[PATCH] btrfs: backref: Fixed checkpatch warning of over 80 characters

checkpatch.pl reported a warning of over 80 characters on line 1833 Adjusted to put and on a different line Signed-off-by: Simon Quigley --- fs/btrfs/backref.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/fs/btrfs/backref.c b/fs/btrfs/backref.c

[PATCH] btrfs: backref: Fixed checkpatch warning of over 80 characters

checkpatch.pl reported a warning of over 80 characters on line 1833 Adjusted to put and on a different line Signed-off-by: Simon Quigley --- fs/btrfs/backref.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/fs/btrfs/backref.c b/fs/btrfs/backref.c index

[PATCH v2] Fix sun7i pin assignment for IRQ's

After testing IRQ pins we found some bugs in the pinctrl declaration. Signed-off-by: hp197 --- Changes in v2: After some more testing we found irq on PI pins. they where on mux6 so this is included in my patch. Also included is a warning for PI17, this pin

[PATCH v2] Fix sun7i pin assignment for IRQ's

After testing IRQ pins we found some bugs in the pinctrl declaration. Signed-off-by: hp197 --- Changes in v2: After some more testing we found irq on PI pins. they where on mux6 so this is included in my patch. Also included is a warning for PI17, this pin was not working on

Re: [PATCH 1/4] ASoC: wm9713: add binding for WM9713 codec

On Sat, Feb 20, 2016 at 11:24:02PM +0100, Robert Jarzmik wrote: Please fix your mail client to word wrap within paragraphs at something substantially less than 80 columns. Doing this makes your messages much easier to read and reply to. > Mark Brown writes: > > On Sat, Feb

Re: [PATCH 1/4] ASoC: wm9713: add binding for WM9713 codec

On Sat, Feb 20, 2016 at 11:24:02PM +0100, Robert Jarzmik wrote: Please fix your mail client to word wrap within paragraphs at something substantially less than 80 columns. Doing this makes your messages much easier to read and reply to. > Mark Brown writes: > > On Sat, Feb 20, 2016 at

Re: [PATCH] btrfs: backref: Fixed checkpatch warning of over 80

On Sat, 2016-02-20 at 18:57 -0600, Simon Quigley wrote: > Better? No, not really. The alignment should be to the open parenthesis as I wrote in the first reply. > On 02/20/2016 06:56 PM, Simon Quigley wrote: > > checkpatch.pl reported a warning of over 80 characters on line 1833 > > > >

Re: [PATCH] btrfs: backref: Fixed checkpatch warning of over 80

On Sat, 2016-02-20 at 18:57 -0600, Simon Quigley wrote: > Better? No, not really. The alignment should be to the open parenthesis as I wrote in the first reply. > On 02/20/2016 06:56 PM, Simon Quigley wrote: > > checkpatch.pl reported a warning of over 80 characters on line 1833 > > > >

Re: [PATCHv2] serial: samsung: drop the spinlock around uart_write_wakeup

2016-02-20 4:30 GMT+09:00 Peter Hurley : > [ +cc Krzysztof Kozlowski ] > > On 02/18/2016 09:15 PM, Anand Moon wrote: >> From: Anand Moon >> >> drop the spin_unlock/lock around uart_write_wakeup to protect >> write wakeup for uart port. > > What

Re: [PATCHv2] serial: samsung: drop the spinlock around uart_write_wakeup

2016-02-20 4:30 GMT+09:00 Peter Hurley : > [ +cc Krzysztof Kozlowski ] > > On 02/18/2016 09:15 PM, Anand Moon wrote: >> From: Anand Moon >> >> drop the spin_unlock/lock around uart_write_wakeup to protect >> write wakeup for uart port. > > What Krzysztof was saying wrt v1 of this patch is that

[PATCH 1/3] btrfs: backref: String formatting fixes

Checkpatch warns about a multi-line string This fixes that issue and seperates the variables to another line Signed-off-by: Simon Quigley --- fs/btrfs/backref.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/fs/btrfs/backref.c

[PATCH 2/3] btrfs: backref: Fixed string formatting error

Checkpatch reported an error that there was a multi-line string. This puts the string on one line and the variables on another. Signed-off-by: Simon Quigley --- fs/btrfs/backref.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/fs/btrfs/backref.c

[PATCH 1/3] btrfs: backref: String formatting fixes

Checkpatch warns about a multi-line string This fixes that issue and seperates the variables to another line Signed-off-by: Simon Quigley --- fs/btrfs/backref.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/fs/btrfs/backref.c b/fs/btrfs/backref.c index

[PATCH 2/3] btrfs: backref: Fixed string formatting error

Checkpatch reported an error that there was a multi-line string. This puts the string on one line and the variables on another. Signed-off-by: Simon Quigley --- fs/btrfs/backref.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/fs/btrfs/backref.c b/fs/btrfs/backref.c

[PATCH 3/3] btrfs: backref: Fixed string error generated by Checkpatch

Checkpatch threw an error that this string was on two lines. I put the string on one line and the variables on the other Signed-off-by: Simon Quigley --- fs/btrfs/backref.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/fs/btrfs/backref.c

[PATCH 3/3] btrfs: backref: Fixed string error generated by Checkpatch

Checkpatch threw an error that this string was on two lines. I put the string on one line and the variables on the other Signed-off-by: Simon Quigley --- fs/btrfs/backref.c | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/fs/btrfs/backref.c b/fs/btrfs/backref.c index

Re: [PATCH] serial: samsung: fix the inconsistency in spinlock

>>> In my next patch I have tried to remove the spin_unlock/spin_lock over >>> uart_write_wakeup(port); >> >> Which may create lockups. Previously there was no port locking around >> uart_write_wakeup. Now there will be. You are effectively adding locking >> over uart_write_wakeup(). >> Again, we

Re: [PATCH] serial: samsung: fix the inconsistency in spinlock

>>> In my next patch I have tried to remove the spin_unlock/spin_lock over >>> uart_write_wakeup(port); >> >> Which may create lockups. Previously there was no port locking around >> uart_write_wakeup. Now there will be. You are effectively adding locking >> over uart_write_wakeup(). >> Again, we

Re: [PATCH] btrfs: backref: Fixed checkpatch warning of over 80

Better? On 02/20/2016 06:56 PM, Simon Quigley wrote: checkpatch.pl reported a warning of over 80 characters on line 1833 Adjusted to put and on a different line Signed-off-by: Simon Quigley --- fs/btrfs/backref.c | 4 ++-- 1 file changed, 2 insertions(+), 2

[PATCH] btrfs: backref: Fixed checkpatch warning of over 80

checkpatch.pl reported a warning of over 80 characters on line 1833 Adjusted to put and on a different line Signed-off-by: Simon Quigley --- fs/btrfs/backref.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/fs/btrfs/backref.c b/fs/btrfs/backref.c

Re: [PATCH] btrfs: backref: Fixed checkpatch warning of over 80

Better? On 02/20/2016 06:56 PM, Simon Quigley wrote: checkpatch.pl reported a warning of over 80 characters on line 1833 Adjusted to put and on a different line Signed-off-by: Simon Quigley --- fs/btrfs/backref.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

[PATCH] btrfs: backref: Fixed checkpatch warning of over 80

checkpatch.pl reported a warning of over 80 characters on line 1833 Adjusted to put and on a different line Signed-off-by: Simon Quigley --- fs/btrfs/backref.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/fs/btrfs/backref.c b/fs/btrfs/backref.c index

Re: [PATCH V6 1/2] regulator: Add document for MT6323 regulator

On Wed, Feb 17, 2016 at 12:37:35PM +0100, John Crispin wrote: > Signed-off-by: John Crispin > Cc: devicet...@vger.kernel.org ...and dropped due to the dependency on MFD changes that you didn't mention :/ I can't apply this without a pull request from Lee with the MFD changes

Re: [PATCH V6 1/2] regulator: Add document for MT6323 regulator

On Wed, Feb 17, 2016 at 12:37:35PM +0100, John Crispin wrote: > Signed-off-by: John Crispin > Cc: devicet...@vger.kernel.org ...and dropped due to the dependency on MFD changes that you didn't mention :/ I can't apply this without a pull request from Lee with the MFD changes for the chip that I

Re: [PATCH v5 1/8] ARM: dts: rockchip: add hdmi/vop device node for rk3036

Am Dienstag, 2. Februar 2016, 11:40:50 schrieb Caesar Wang: > This patch adds the needed display info for rk3036 SOCs. > > The rk3036 support two overlay plane and one hwc plane, > it supports IOMMU, and its IOMMU same as rk3288's. > Meanwhile, add the inno hdmi for HDMI display. > >

Re: [PATCH v5 1/8] ARM: dts: rockchip: add hdmi/vop device node for rk3036

Am Dienstag, 2. Februar 2016, 11:40:50 schrieb Caesar Wang: > This patch adds the needed display info for rk3036 SOCs. > > The rk3036 support two overlay plane and one hwc plane, > it supports IOMMU, and its IOMMU same as rk3288's. > Meanwhile, add the inno hdmi for HDMI display. > >

Re: [PATCH] jme: remove the jme driver as it is no longer maintained

On Sat, Feb 20, 2016 at 10:16 PM, David Miller wrote: > > Sorry, this is not how things work. > > You can suggest marking the driver unmaintained in MAINTAINERS if the > listed developer has been unresponsive for a very long time. > > But removing the driver altogether is not

Re: [PATCH] jme: remove the jme driver as it is no longer maintained

On Sat, Feb 20, 2016 at 10:16 PM, David Miller wrote: > > Sorry, this is not how things work. > > You can suggest marking the driver unmaintained in MAINTAINERS if the > listed developer has been unresponsive for a very long time. > > But removing the driver altogether is not prudent at all. > >

Re: [PATCH] jme: remove the jme driver as it is no longer maintained

Sorry, this is not how things work. You can suggest marking the driver unmaintained in MAINTAINERS if the listed developer has been unresponsive for a very long time. But removing the driver altogether is not prudent at all. Just because it doesn't work %100 the way you like, and nobody has

Re: [PATCH] jme: remove the jme driver as it is no longer maintained

Sorry, this is not how things work. You can suggest marking the driver unmaintained in MAINTAINERS if the listed developer has been unresponsive for a very long time. But removing the driver altogether is not prudent at all. Just because it doesn't work %100 the way you like, and nobody has

Re: [PATCH] btrfs: backref: Fixed checkpatch warning of over 80 characters

On Sat, 2016-02-20 at 12:17 -0600, Simon Quigley wrote: > checkpatch.pl reported a warning of over 80 characters on line 1833 [] > diff --git a/fs/btrfs/backref.c b/fs/btrfs/backref.c [] > @@ -1830,7 +1830,11 @@ static int iterate_inode_extrefs(u64 inum, struct > btrfs_root *fs_root, >  

Re: [PATCH] btrfs: backref: Fixed checkpatch warning of over 80 characters

On Sat, 2016-02-20 at 12:17 -0600, Simon Quigley wrote: > checkpatch.pl reported a warning of over 80 characters on line 1833 [] > diff --git a/fs/btrfs/backref.c b/fs/btrfs/backref.c [] > @@ -1830,7 +1830,11 @@ static int iterate_inode_extrefs(u64 inum, struct > btrfs_root *fs_root, >  

Re: [PATCH] rtc: Add an option to invalidate dates in 2038

On 21/02/2016 at 00:17:02 +0100, Alexandre Belloni wrote : > All the failures seem quite random to me but the reports I get are not > that precise. > > I know it happens with PCF8523 and that can be true because the > datasheet says the date is undefined at reset. The handling of the OS > bit

Re: [PATCH] rtc: Add an option to invalidate dates in 2038

On 21/02/2016 at 00:17:02 +0100, Alexandre Belloni wrote : > All the failures seem quite random to me but the reports I get are not > that precise. > > I know it happens with PCF8523 and that can be true because the > datasheet says the date is undefined at reset. The handling of the OS > bit

Re: [RESEND PATCH] drivers: android: correct the size of struct binder_uintptr_t for BC_DEAD_BINDER_DONE

On Fri, Feb 19, 2016 at 07:08:40AM -0800, Olof Johansson wrote: > Hi, > > On Tue, Feb 16, 2016 at 5:32 PM, Nicolas Boichat > wrote: > > From: Lisa Du > > > > There's one point was missed in the patch commit da49889deb34 ("staging: > > binder: Support

Re: [RESEND PATCH] drivers: android: correct the size of struct binder_uintptr_t for BC_DEAD_BINDER_DONE

On Fri, Feb 19, 2016 at 07:08:40AM -0800, Olof Johansson wrote: > Hi, > > On Tue, Feb 16, 2016 at 5:32 PM, Nicolas Boichat > wrote: > > From: Lisa Du > > > > There's one point was missed in the patch commit da49889deb34 ("staging: > > binder: Support concurrent 32 bit and 64 bit processes.").

Re: [PATCH] staging: xgifb: Fix comment style

On Wed, Feb 17, 2016 at 02:53:34PM +0800, Bo YU wrote: > Fix comments to use trailing */ on separate lines. > > Signed-off-by: YU BO > --- > drivers/staging/xgifb/vb_init.c | 10 +- > 1 file changed, 5 insertions(+), 5 deletions(-) Patch doesn't apply :(

Re: [PATCH] staging: xgifb: Fix comment style

On Wed, Feb 17, 2016 at 02:53:34PM +0800, Bo YU wrote: > Fix comments to use trailing */ on separate lines. > > Signed-off-by: YU BO > --- > drivers/staging/xgifb/vb_init.c | 10 +- > 1 file changed, 5 insertions(+), 5 deletions(-) Patch doesn't apply :(

Re: [PATCH] staging: lusture: obdclass: Remove unnecessary NULL check

On Thu, Feb 18, 2016 at 08:55:39PM +0530, Bhaktipriya Shridhar wrote: > NULL check before the debugfs_remove_recursive function is not needed. > > This was detected using scripts/coccinelle/free/ifnullfree.cocci > > Signed-off-by: Bhaktipriya Shridhar > --- >

Re: [PATCH] staging: lusture: obdclass: Remove unnecessary NULL check

On Thu, Feb 18, 2016 at 08:55:39PM +0530, Bhaktipriya Shridhar wrote: > NULL check before the debugfs_remove_recursive function is not needed. > > This was detected using scripts/coccinelle/free/ifnullfree.cocci > > Signed-off-by: Bhaktipriya Shridhar > --- >

Re: [PATCH v6 20/25] perf hists browser: Implement hierarchy output

On Tue, Feb 16, 2016 at 11:08:38PM +0900, Namhyung Kim wrote: > Implement hierarchy mode in TUI. The output is look like stdio but it > also supports to fold/unfold children dynamically. > > Acked-by: Pekka Enberg > Signed-off-by: Namhyung Kim > --- >

Re: [PATCH v6 10/25] perf hists: Resort hist entries with hierarchy

On Tue, Feb 16, 2016 at 11:08:28PM +0900, Namhyung Kim wrote: SNIP > @@ -1349,6 +1427,17 @@ static void output_resort(struct hists *hists, struct > ui_progress *prog, > > min_callchain_hits = callchain_total * (callchain_param.min_percent / > 100); > > +

Re: [PATCH v6 25/25] perf top: Add --hierarchy option

On Tue, Feb 16, 2016 at 11:08:43PM +0900, Namhyung Kim wrote: > Support hierarchy output for perf-top using --hierarchy option. > > Acked-by: Pekka Enberg > Signed-off-by: Namhyung Kim > --- > tools/perf/Documentation/perf-top.txt | 3 +++ >

Re: [PATCH v6 20/25] perf hists browser: Implement hierarchy output

On Tue, Feb 16, 2016 at 11:08:38PM +0900, Namhyung Kim wrote: > Implement hierarchy mode in TUI. The output is look like stdio but it > also supports to fold/unfold children dynamically. > > Acked-by: Pekka Enberg > Signed-off-by: Namhyung Kim > --- > tools/perf/ui/browsers/hists.c | 269 >

Re: [PATCH v6 10/25] perf hists: Resort hist entries with hierarchy

On Tue, Feb 16, 2016 at 11:08:28PM +0900, Namhyung Kim wrote: SNIP > @@ -1349,6 +1427,17 @@ static void output_resort(struct hists *hists, struct > ui_progress *prog, > > min_callchain_hits = callchain_total * (callchain_param.min_percent / > 100); > > +

Re: [PATCH v6 25/25] perf top: Add --hierarchy option

On Tue, Feb 16, 2016 at 11:08:43PM +0900, Namhyung Kim wrote: > Support hierarchy output for perf-top using --hierarchy option. > > Acked-by: Pekka Enberg > Signed-off-by: Namhyung Kim > --- > tools/perf/Documentation/perf-top.txt | 3 +++ > tools/perf/builtin-top.c | 15

Re: [PATCH v6 09/25] perf hists: Basic support of hierarchical report view

On Tue, Feb 16, 2016 at 11:08:27PM +0900, Namhyung Kim wrote: SNIP > + int64_t cmp; > + > + while (*p != NULL) { > + parent = *p; > + iter = rb_entry(parent, struct hist_entry, rb_node_in); > + > + cmp = fmt->collapse(fmt, iter, he); > + if

Re: [PATCH v6 09/25] perf hists: Basic support of hierarchical report view

On Tue, Feb 16, 2016 at 11:08:27PM +0900, Namhyung Kim wrote: SNIP > + int64_t cmp; > + > + while (*p != NULL) { > + parent = *p; > + iter = rb_entry(parent, struct hist_entry, rb_node_in); > + > + cmp = fmt->collapse(fmt, iter, he); > + if

Re: [PATCH v6 16/25] perf ui/stdio: Implement hierarchy output mode

On Tue, Feb 16, 2016 at 11:08:34PM +0900, Namhyung Kim wrote: SNIP > +static int hist_entry__hierarchy_fprintf(struct hist_entry *he, > + struct perf_hpp *hpp, > + int nr_sort_key, struct hists *hists, > +

Re: [PATCH v6 16/25] perf ui/stdio: Implement hierarchy output mode

On Tue, Feb 16, 2016 at 11:08:34PM +0900, Namhyung Kim wrote: SNIP > +static int hist_entry__hierarchy_fprintf(struct hist_entry *he, > + struct perf_hpp *hpp, > + int nr_sort_key, struct hists *hists, > +

Re: [PATCH] rtc: Add an option to invalidate dates in 2038

On 20/02/2016 at 23:16:48 +0100, Arnd Bergmann wrote : > On Saturday 20 February 2016 21:47:15 Alexandre Belloni wrote: > > > > Actually, I'm not trying to solve the 2038 issue. > > > > But in the current state on 32 bit platforms, while the kernel is able > > to handle a 64bit date, userspace

Re: [PATCH] rtc: Add an option to invalidate dates in 2038

On 20/02/2016 at 23:16:48 +0100, Arnd Bergmann wrote : > On Saturday 20 February 2016 21:47:15 Alexandre Belloni wrote: > > > > Actually, I'm not trying to solve the 2038 issue. > > > > But in the current state on 32 bit platforms, while the kernel is able > > to handle a 64bit date, userspace

hello,

My name is Jack Antonik. I'm 45 years old, from the US. I'm in Syria right now fighting IS. I want to get to know you better, if I may be so bold. I consider myself an easy-going man, and I am currently looking for a relationship in which I feel loved. Please tell me more about yourself, if

hello,

My name is Jack Antonik. I'm 45 years old, from the US. I'm in Syria right now fighting IS. I want to get to know you better, if I may be so bold. I consider myself an easy-going man, and I am currently looking for a relationship in which I feel loved. Please tell me more about yourself, if

Re: [PATCH] Documentation/memory-barriers: fix wrong comment in example

On Sun, Feb 21, 2016 at 4:57 AM, Paul E. McKenney wrote: > On Sat, Feb 20, 2016 at 03:01:08PM +0900, SeongJae Park wrote: >> There is wrong comment in example for compiler store omit behavior. It >> shows example of the problem and than problem solved version code. >>

Re: [PATCH] Documentation/memory-barriers: fix wrong comment in example

On Sun, Feb 21, 2016 at 4:57 AM, Paul E. McKenney wrote: > On Sat, Feb 20, 2016 at 03:01:08PM +0900, SeongJae Park wrote: >> There is wrong comment in example for compiler store omit behavior. It >> shows example of the problem and than problem solved version code. >> However, the comment in the

Re: Requesting Thunderbolt 3 support

On Sat, Feb 20, 2016 at 5:02 PM, Greg KH wrote: > Do you have any hardware that supports this that isn't working with the > current Thunderbolt drivers? I don't, but I may have access to some in the next week or two to test. I assumed TB3 wouldn't be supported

Re: Requesting Thunderbolt 3 support

On Sat, Feb 20, 2016 at 5:02 PM, Greg KH wrote: > Do you have any hardware that supports this that isn't working with the > current Thunderbolt drivers? I don't, but I may have access to some in the next week or two to test. I assumed TB3 wouldn't be supported because it's different than TB2,

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

On Saturday 20 February 2016 18:48:22 Anurag Kumar Vulisha wrote: > index 7ca8b97..7e48dfc 100644 > --- a/Documentation/devicetree/bindings/ata/ahci-ceva.txt > +++ b/Documentation/devicetree/bindings/ata/ahci-ceva.txt > @@ -8,6 +8,7 @@ Required properties: > > Optional properties: >-

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

On Saturday 20 February 2016 18:48:22 Anurag Kumar Vulisha wrote: > index 7ca8b97..7e48dfc 100644 > --- a/Documentation/devicetree/bindings/ata/ahci-ceva.txt > +++ b/Documentation/devicetree/bindings/ata/ahci-ceva.txt > @@ -8,6 +8,7 @@ Required properties: > > Optional properties: >-

Re: [PATCH 43/45] staging/lustre/libcfs: Replace use of printk with pr_

On Tue, Feb 16, 2016 at 11:12:14AM -0500, Oleg Drokin wrote: > > On Feb 16, 2016, at 12:55 AM, Joe Perches wrote: > > > On Tue, 2016-02-16 at 00:47 -0500, gr...@linuxhacker.ru wrote: > >> From: Oleg Drokin > >> > >> This pacifies checkpatch amongst other things, also is

Re: [PATCH 43/45] staging/lustre/libcfs: Replace use of printk with pr_

On Tue, Feb 16, 2016 at 11:12:14AM -0500, Oleg Drokin wrote: > > On Feb 16, 2016, at 12:55 AM, Joe Perches wrote: > > > On Tue, 2016-02-16 at 00:47 -0500, gr...@linuxhacker.ru wrote: > >> From: Oleg Drokin > >> > >> This pacifies checkpatch amongst other things, also is shorter to write > >>

at76c50x-usb: usb_put_dev() if at76_load_internal_fw() succeed

I do not see any reason to call usb_put_dev() if at76_load_internal_fw() succeed. But it is here from the very beginning. Any suggestions? -- Thank you, Alexey

at76c50x-usb: usb_put_dev() if at76_load_internal_fw() succeed

I do not see any reason to call usb_put_dev() if at76_load_internal_fw() succeed. But it is here from the very beginning. Any suggestions? -- Thank you, Alexey

[PATCH] at76c50x-usb: avoid double usb_put_dev() after downloading internal firmware in at76_probe()

There is no need in usb_put_dev() if at76_load_internal_fw() succeed. Found by Linux Driver Verification project (linuxtesting.org). Signed-off-by: Alexey Khoroshilov --- drivers/net/wireless/atmel/at76c50x-usb.c | 2 -- 1 file changed, 2 deletions(-) diff --git

[PATCH] at76c50x-usb: avoid double usb_put_dev() after downloading internal firmware in at76_probe()

There is no need in usb_put_dev() if at76_load_internal_fw() succeed. Found by Linux Driver Verification project (linuxtesting.org). Signed-off-by: Alexey Khoroshilov --- drivers/net/wireless/atmel/at76c50x-usb.c | 2 -- 1 file changed, 2 deletions(-) diff --git

Re: [PATCH 1/4] ASoC: wm9713: add binding for WM9713 codec

Mark Brown writes: > On Sat, Feb 20, 2016 at 09:32:58PM +0100, Robert Jarzmik wrote: >> Mark Brown writes: >> > On Sat, Feb 20, 2016 at 07:22:04PM +0100, Robert Jarzmik wrote: >> I will. By now I fail to see how this will help in the wm9713 probing and >>

Re: [PATCH 1/4] ASoC: wm9713: add binding for WM9713 codec

Mark Brown writes: > On Sat, Feb 20, 2016 at 09:32:58PM +0100, Robert Jarzmik wrote: >> Mark Brown writes: >> > On Sat, Feb 20, 2016 at 07:22:04PM +0100, Robert Jarzmik wrote: >> I will. By now I fail to see how this will help in the wm9713 probing and >> detection ... > > It will eumerate the

Re: [PATCH] kernel/resource.c: fix muxed resource handling in __request_region()

On February 20, 2016 9:12:01 AM Linus Torvalds wrote: On Fri, Feb 19, 2016 at 3:25 PM, Jesse Barnes wrote: +Linus (the de-facto resource guy). On 02/19/2016 01:10 PM, Vincent Pelletier wrote: Tested-by: Vincent Pelletier

Re: [PATCH] kernel/resource.c: fix muxed resource handling in __request_region()

On February 20, 2016 9:12:01 AM Linus Torvalds wrote: On Fri, Feb 19, 2016 at 3:25 PM, Jesse Barnes wrote: +Linus (the de-facto resource guy). On 02/19/2016 01:10 PM, Vincent Pelletier wrote: Tested-by: Vincent Pelletier Hmm. So I'm not entirely happy with the patch, because I think

[PATCH] thermal: rcar: check for NULL return of of_match_device

From: Colin Ian King of_match_device can potentially return NULL, so we need to check for this case to avoid a null pointer dereference on of_id Signed-off-by: Colin Ian King --- drivers/thermal/rcar_thermal.c | 6 +- 1 file changed, 5

[PATCH] thermal: rcar: check for NULL return of of_match_device

From: Colin Ian King of_match_device can potentially return NULL, so we need to check for this case to avoid a null pointer dereference on of_id Signed-off-by: Colin Ian King --- drivers/thermal/rcar_thermal.c | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git

Re: [PATCH] rtc: Add an option to invalidate dates in 2038

On Saturday 20 February 2016 21:47:15 Alexandre Belloni wrote: > > Actually, I'm not trying to solve the 2038 issue. > > But in the current state on 32 bit platforms, while the kernel is able > to handle a 64bit date, userspace is not. The main issue is that > distributions use HCTOSYS so if the

Re: [PATCH] rtc: Add an option to invalidate dates in 2038

On Saturday 20 February 2016 21:47:15 Alexandre Belloni wrote: > > Actually, I'm not trying to solve the 2038 issue. > > But in the current state on 32 bit platforms, while the kernel is able > to handle a 64bit date, userspace is not. The main issue is that > distributions use HCTOSYS so if the

[PULL REQUEST] i2c for 4.5

Linus, some bugfixes from I2C for you: A fix for a RuntimePM regression with OMAP, a fix to enable TCO for Lewisburg platforms, and a typo fix while we are here. Please pull. Thanks, Wolfram The following changes since commit 388f7b1d6e8ca06762e2454d28d6c3c55ad0fe95: Linux 4.5-rc3

[PULL REQUEST] i2c for 4.5

Linus, some bugfixes from I2C for you: A fix for a RuntimePM regression with OMAP, a fix to enable TCO for Lewisburg platforms, and a typo fix while we are here. Please pull. Thanks, Wolfram The following changes since commit 388f7b1d6e8ca06762e2454d28d6c3c55ad0fe95: Linux 4.5-rc3

[PATCH] rtlwifi: pass struct rtl_stats by reference as it is more efficient

From: Colin Ian King passing rtl_stats by value is inefficient; the structure is over 300 bytes in size and generally just one field (packet_report_type) is being accessed, so the pass by value is a relatively large overhead. This change just affects just the

[PATCH] rtlwifi: pass struct rtl_stats by reference as it is more efficient

From: Colin Ian King passing rtl_stats by value is inefficient; the structure is over 300 bytes in size and generally just one field (packet_report_type) is being accessed, so the pass by value is a relatively large overhead. This change just affects just the rx_command_packet calls.

Re: Requesting Thunderbolt 3 support

On Sat, Feb 20, 2016 at 02:32:55PM -0500, Jeremy Carter wrote: > Hi, > > Please CC replies to me since I'm not subscribed to the list. > > I'm wondering if anyone is working on thunderbolt 3 support, and if > not I would like to request thunderbolt 3 support in the kernel. > > Thunderbolt 3

Re: Requesting Thunderbolt 3 support

On Sat, Feb 20, 2016 at 02:32:55PM -0500, Jeremy Carter wrote: > Hi, > > Please CC replies to me since I'm not subscribed to the list. > > I'm wondering if anyone is working on thunderbolt 3 support, and if > not I would like to request thunderbolt 3 support in the kernel. > > Thunderbolt 3

Linux 4.5-rc5

Things continue to look normal, and things hav ebeen fairly calm. Yes, the VM THP cleanup seems to still be problematic on s390, but other than that I don't see anything particularly worrisome. So another week, another rc. The patch looks pretty normal, with about 55% drivers (drm and clk drivers

Linux 4.5-rc5

Things continue to look normal, and things hav ebeen fairly calm. Yes, the VM THP cleanup seems to still be problematic on s390, but other than that I don't see anything particularly worrisome. So another week, another rc. The patch looks pretty normal, with about 55% drivers (drm and clk drivers

Re: [PATCH 12/15] ACPICA: ACPI 6.1: Add full support for this version of ACPI spec

On 2/19/2016 1:17 AM, Lv Zheng wrote: > From: Bob Moore > > ACPICA commit 5f21bddaa2cec035ca80608803ce2f0858d4f387 > > Small changes: > 1) A couple new predefined names > 2) New _HID values I don't see where you are adding new _HID values in this patch. > 3) New

Re: [PATCH 12/15] ACPICA: ACPI 6.1: Add full support for this version of ACPI spec

On 2/19/2016 1:17 AM, Lv Zheng wrote: > From: Bob Moore > > ACPICA commit 5f21bddaa2cec035ca80608803ce2f0858d4f387 > > Small changes: > 1) A couple new predefined names > 2) New _HID values I don't see where you are adding new _HID values in this patch. > 3) New subtable for HEST > > Link:

  1   2   3   4   >