Re: [PATCH net] xgene: Don't fail probe, if there is no clk resource for SGMII interfaces

On Thu, Jul 27, 2017 at 03:39:58PM -0700, Laura Abbott wrote: > I don't know the intricacies of the Mustang hardware but external > aborts have been a symptom of missing clocks on other hardware. you are right, it's a missing clock. For SGMII ports the driver doesn't really use the clock source

Re: [PATCH net] xgene: Don't fail probe, if there is no clk resource for SGMII interfaces

On Thu, Jul 27, 2017 at 03:39:58PM -0700, Laura Abbott wrote: > I don't know the intricacies of the Mustang hardware but external > aborts have been a symptom of missing clocks on other hardware. you are right, it's a missing clock. For SGMII ports the driver doesn't really use the clock source

Re: [RFC] perf: Delayed userspace unwind (Was: [PATCH v3 00/10] x86: ORC unwinder)

On Fri, Jul 28, 2017 at 04:13:25PM +0200, Jiri Olsa wrote: > On Tue, Jul 25, 2017 at 01:55:12PM +0200, Peter Zijlstra wrote: > > SNIP > > > > > diff --git a/kernel/events/callchain.c b/kernel/events/callchain.c > > index 1b2be63c8528..c98a12f3592c 100644 > > --- a/kernel/events/callchain.c > >

Re: [RFC] perf: Delayed userspace unwind (Was: [PATCH v3 00/10] x86: ORC unwinder)

On Fri, Jul 28, 2017 at 04:13:25PM +0200, Jiri Olsa wrote: > On Tue, Jul 25, 2017 at 01:55:12PM +0200, Peter Zijlstra wrote: > > SNIP > > > > > diff --git a/kernel/events/callchain.c b/kernel/events/callchain.c > > index 1b2be63c8528..c98a12f3592c 100644 > > --- a/kernel/events/callchain.c > >

Re: [PATCH] staging: pi433: use div_u64 for 64-bit division

Hi Arnd, we already have a patch for this: [PATCH 1/1] staging: pi433: fix problem with division in rf69_set_deviation from 20.07.2017 Maybe I did something wrong, but my first solution was exactly like your proposal. As far as I remeber, I wasn't able to compile it that way. Therefore I made

Re: [PATCH] staging: pi433: use div_u64 for 64-bit division

Hi Arnd, we already have a patch for this: [PATCH 1/1] staging: pi433: fix problem with division in rf69_set_deviation from 20.07.2017 Maybe I did something wrong, but my first solution was exactly like your proposal. As far as I remeber, I wasn't able to compile it that way. Therefore I made

RE: [Linux-ima-devel] [RFC PATCH 1/5] ima: extend clone() with IMA namespace support

> > Each measurement entry in the list could have new fields to identify > > the namespace. Since the namespaces can be reused, a timestamp or > > others fields could be added to uniquely identify the namespace id. > > The more fields included in the measurement list, the more > measurements will

RE: [Linux-ima-devel] [RFC PATCH 1/5] ima: extend clone() with IMA namespace support

> > Each measurement entry in the list could have new fields to identify > > the namespace. Since the namespaces can be reused, a timestamp or > > others fields could be added to uniquely identify the namespace id. > > The more fields included in the measurement list, the more > measurements will

Re: [PATCH] HID: wacom: add USB_HID dependency

On Fri, Jul 28, 2017 at 4:07 PM, Jason Gerecke wrote: > On July 28, 2017 6:18:00 AM PDT, Arnd Bergmann wrote: >>The driver has gained a compile-time dependency that we should >>express in Kconfig to avoid this link error: >> > > Would conditional compilation

Re: [PATCH] HID: wacom: add USB_HID dependency

On Fri, Jul 28, 2017 at 4:07 PM, Jason Gerecke wrote: > On July 28, 2017 6:18:00 AM PDT, Arnd Bergmann wrote: >>The driver has gained a compile-time dependency that we should >>express in Kconfig to avoid this link error: >> > > Would conditional compilation be an acceptable alternative to

Re: [PATCH] Staging: pi433: fix some warnings detected using sparse

On Fri, Jul 28, 2017 at 02:56:26PM +0200, Elia Geretto wrote: > This patch corrects some visibility issues regarding some functions and > solves a warning related to a non-matching union. After this patch, > sparse produces only one other warning regarding a bitwise operator; > however, this

Re: [PATCH] Staging: pi433: fix some warnings detected using sparse

On Fri, Jul 28, 2017 at 02:56:26PM +0200, Elia Geretto wrote: > This patch corrects some visibility issues regarding some functions and > solves a warning related to a non-matching union. After this patch, > sparse produces only one other warning regarding a bitwise operator; > however, this

Re: [PATCH] staging: comedi: ni_mio_common.c: fix coding style issue

On 23/07/17 13:14, Christopher Mårtensson wrote: From 3e90ab52ad9b437d7c09cc667161cdb855c0cc7b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Christopher=20M=C3=A5rtensson?= Date: Sun, 23 Jul 2017 13:05:09 +0200 Subject: [PATCH] staging: comedi: ni_mio_common.c: fix coding style

Re: [PATCH] staging: comedi: ni_mio_common.c: fix coding style issue

On 23/07/17 13:14, Christopher Mårtensson wrote: From 3e90ab52ad9b437d7c09cc667161cdb855c0cc7b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Christopher=20M=C3=A5rtensson?= Date: Sun, 23 Jul 2017 13:05:09 +0200 Subject: [PATCH] staging: comedi: ni_mio_common.c: fix coding style issue

Re: [RFC] perf: Delayed userspace unwind (Was: [PATCH v3 00/10] x86: ORC unwinder)

On Tue, Jul 25, 2017 at 01:55:12PM +0200, Peter Zijlstra wrote: SNIP > > diff --git a/kernel/events/callchain.c b/kernel/events/callchain.c > index 1b2be63c8528..c98a12f3592c 100644 > --- a/kernel/events/callchain.c > +++ b/kernel/events/callchain.c > @@ -12,6 +12,7 @@ > #include > #include

Re: [RFC] perf: Delayed userspace unwind (Was: [PATCH v3 00/10] x86: ORC unwinder)

On Tue, Jul 25, 2017 at 01:55:12PM +0200, Peter Zijlstra wrote: SNIP > > diff --git a/kernel/events/callchain.c b/kernel/events/callchain.c > index 1b2be63c8528..c98a12f3592c 100644 > --- a/kernel/events/callchain.c > +++ b/kernel/events/callchain.c > @@ -12,6 +12,7 @@ > #include > #include

Re: Suspend-resume failure on Intel Eagle Lake Core2Duo

On Fri, 28 Jul 2017, Tomi Sarvela wrote: > On 28/07/17 16:15, Thomas Gleixner wrote: > > Another question. Is the machine completely dead or not? > > Completely dead. Powerled is on, so host isn't shut down. So that means it does not even power the machine down. That's what I expected least. >

Re: Suspend-resume failure on Intel Eagle Lake Core2Duo

On Fri, 28 Jul 2017, Tomi Sarvela wrote: > On 28/07/17 16:15, Thomas Gleixner wrote: > > Another question. Is the machine completely dead or not? > > Completely dead. Powerled is on, so host isn't shut down. So that means it does not even power the machine down. That's what I expected least. >

Re: Possible race condition in oom-killer

On Fri 28-07-17 19:20:42, Manish Jaggi wrote: > > Hi Michal, > On 7/28/2017 6:02 PM, Michal Hocko wrote: > >[CC linux-mm] > > > >On Fri 28-07-17 17:22:25, Manish Jaggi wrote: > >>was: Re: [PATCH] mm, oom: allow oom reaper to race with exit_mmap > >> > >>Hi Michal, > >>On 7/27/2017 2:54 PM, Michal

Re: Possible race condition in oom-killer

On Fri 28-07-17 19:20:42, Manish Jaggi wrote: > > Hi Michal, > On 7/28/2017 6:02 PM, Michal Hocko wrote: > >[CC linux-mm] > > > >On Fri 28-07-17 17:22:25, Manish Jaggi wrote: > >>was: Re: [PATCH] mm, oom: allow oom reaper to race with exit_mmap > >> > >>Hi Michal, > >>On 7/27/2017 2:54 PM, Michal

[PATCH] [RFC] ARM: move __bug_table into .data for XIP_KERNEL

Matt Hart reports that vf610m4_defconfig kernels grew to 2GB xipImage size after the __bug_table change. I tried out a few things and found that moving the bug table into the .data section avoids this problem. However, the linker script magic is beyond my capabilities here, so this is almost

[PATCH] [RFC] ARM: move __bug_table into .data for XIP_KERNEL

Matt Hart reports that vf610m4_defconfig kernels grew to 2GB xipImage size after the __bug_table change. I tried out a few things and found that moving the bug table into the .data section avoids this problem. However, the linker script magic is beyond my capabilities here, so this is almost

Re: [PATCH v1 5/6] ASoC: codecs: msm8916-wcd-analog: add MBHC support

On 28/07/17 14:51, Mark Brown wrote: On Wed, Jul 26, 2017 at 02:35:11AM +0200, srinivas.kandaga...@linaro.org wrote: + if (wcd->hphl_jack_type_normally_open) + plug_type = CDC_A_HPHL_PLUG_TYPE_NO; + + if (wcd->gnd_jack_type_normally_open) + plug_type

Re: [PATCH v1 5/6] ASoC: codecs: msm8916-wcd-analog: add MBHC support

On 28/07/17 14:51, Mark Brown wrote: On Wed, Jul 26, 2017 at 02:35:11AM +0200, srinivas.kandaga...@linaro.org wrote: + if (wcd->hphl_jack_type_normally_open) + plug_type = CDC_A_HPHL_PLUG_TYPE_NO; + + if (wcd->gnd_jack_type_normally_open) + plug_type

Re: [RFC PATCH 6/8] EDAC, mce_amd: Convert to seq_buf

On Fri, Jul 28, 2017 at 08:59:59AM -0400, Steven Rostedt wrote: > Interesting, this is the first I heard of the genpool. I probably could > have used this in other code. Good to know (learn something new every > day :-) That's a safe assumption for each one of us. :) > I'll have to take a look

Re: [RFC PATCH 6/8] EDAC, mce_amd: Convert to seq_buf

On Fri, Jul 28, 2017 at 08:59:59AM -0400, Steven Rostedt wrote: > Interesting, this is the first I heard of the genpool. I probably could > have used this in other code. Good to know (learn something new every > day :-) That's a safe assumption for each one of us. :) > I'll have to take a look

Re: [PATCH V2] lightnvm: pblk fix for 4.13

> On 28 Jul 2017, at 16.06, Jens Axboe wrote: > > On 07/28/2017 07:13 AM, Javier González wrote: >> Hi Jens, >> >> Can you pick up this fix for 4.13? It is a fix to a read corruption in >> pblk that has been there form the beginning. It is due to a bad bio >> manipulation in

Re: [PATCH V2] lightnvm: pblk fix for 4.13

> On 28 Jul 2017, at 16.06, Jens Axboe wrote: > > On 07/28/2017 07:13 AM, Javier González wrote: >> Hi Jens, >> >> Can you pick up this fix for 4.13? It is a fix to a read corruption in >> pblk that has been there form the beginning. It is due to a bad bio >> manipulation in the case that an

Re: [PATCH v2 4/4] clk: meson: gxbb-aoclk: Add CEC 32k clock

On 07/28/2017 12:29 PM, Martin Blumenstingl wrote: > Hi Neil, > > thanks for these patches, CEC support is another good step! Hi Martin, Thanks for your feedback ! > > On Fri, Jul 28, 2017 at 11:53 AM, Neil Armstrong > wrote: >> The CEC 32K AO Clock is a dual divider

Re: [PATCH v2 4/4] clk: meson: gxbb-aoclk: Add CEC 32k clock

On 07/28/2017 12:29 PM, Martin Blumenstingl wrote: > Hi Neil, > > thanks for these patches, CEC support is another good step! Hi Martin, Thanks for your feedback ! > > On Fri, Jul 28, 2017 at 11:53 AM, Neil Armstrong > wrote: >> The CEC 32K AO Clock is a dual divider with dual counter to

Re: [PATCH 0/4] ACPI: DMA ranges management

On Fri, Jul 28, 2017 at 02:08:01PM +0100, Robin Murphy wrote: [...] > >>> To ensure that dma_set_mask() and friends actually respect _DMA, would > >>> you consider introducing a dma_supported() callback to check the input > >>> dma_mask against the FW defined limits? This would end up

Re: [PATCH 0/4] ACPI: DMA ranges management

On Fri, Jul 28, 2017 at 02:08:01PM +0100, Robin Murphy wrote: [...] > >>> To ensure that dma_set_mask() and friends actually respect _DMA, would > >>> you consider introducing a dma_supported() callback to check the input > >>> dma_mask against the FW defined limits? This would end up

Re: [PATCH] HID: wacom: add USB_HID dependency

On July 28, 2017 6:18:00 AM PDT, Arnd Bergmann wrote: >The driver has gained a compile-time dependency that we should >express in Kconfig to avoid this link error: > Would conditional compilation be an acceptable alternative to adding a dependency? The USB_HID code is only used

Re: [PATCH] HID: wacom: add USB_HID dependency

On July 28, 2017 6:18:00 AM PDT, Arnd Bergmann wrote: >The driver has gained a compile-time dependency that we should >express in Kconfig to avoid this link error: > Would conditional compilation be an acceptable alternative to adding a dependency? The USB_HID code is only used to check if the

Re: Possible race condition in oom-killer

On Fri 28-07-17 22:55:51, Tetsuo Handa wrote: > Michal Hocko wrote: > > On Fri 28-07-17 22:15:01, Tetsuo Handa wrote: > > > task_will_free_mem(current) in out_of_memory() returning false due to > > > MMF_OOM_SKIP already set allowed each thread sharing that mm to select a > > > new > > > OOM

Re: Possible race condition in oom-killer

On Fri 28-07-17 22:55:51, Tetsuo Handa wrote: > Michal Hocko wrote: > > On Fri 28-07-17 22:15:01, Tetsuo Handa wrote: > > > task_will_free_mem(current) in out_of_memory() returning false due to > > > MMF_OOM_SKIP already set allowed each thread sharing that mm to select a > > > new > > > OOM

[PATCH -tip v7 2/2] [BUGFIX] kprobes/x86: Do not jump-optimize kprobes on irq entry code

Since the kernel segment registers are not prepared at the entry of irq-entry code, if a kprobe on such code is jump-optimized, accessing per-cpu variables may cause kernel panic. However, if the kprobe is not optimized, it kicks int3 exception and set segment registers correctly. This checks

[PATCH -tip v7 2/2] [BUGFIX] kprobes/x86: Do not jump-optimize kprobes on irq entry code

Since the kernel segment registers are not prepared at the entry of irq-entry code, if a kprobe on such code is jump-optimized, accessing per-cpu variables may cause kernel panic. However, if the kprobe is not optimized, it kicks int3 exception and set segment registers correctly. This checks

Re: [PATCH V2] lightnvm: pblk fix for 4.13

On 07/28/2017 07:13 AM, Javier González wrote: > Hi Jens, > > Can you pick up this fix for 4.13? It is a fix to a read corruption in > pblk that has been there form the beginning. It is due to a bad bio > manipulation in the case that an I/O containing lbas that are invalid, > point to data in

Re: [PATCH v3] irqchip/tango: Don't use incorrect irq_mask_ack callback

On 27/07/2017 20:17, Florian Fainelli wrote: > On 07/26/2017 12:13 PM, Måns Rullgård wrote: > >> Florian Fainelli writes: >> >>> On 07/25/2017 06:29 AM, Måns Rullgård wrote: >>> Marc Gonzalez writes: > On 25/07/2017 15:16, Måns Rullgård wrote: >

Re: [PATCH v3] irqchip/tango: Don't use incorrect irq_mask_ack callback

On 27/07/2017 20:17, Florian Fainelli wrote: > On 07/26/2017 12:13 PM, Måns Rullgård wrote: > >> Florian Fainelli writes: >> >>> On 07/25/2017 06:29 AM, Måns Rullgård wrote: >>> Marc Gonzalez writes: > On 25/07/2017 15:16, Måns Rullgård wrote: > >> What happened to the

Re: [PATCH V2] lightnvm: pblk fix for 4.13

On 07/28/2017 07:13 AM, Javier González wrote: > Hi Jens, > > Can you pick up this fix for 4.13? It is a fix to a read corruption in > pblk that has been there form the beginning. It is due to a bad bio > manipulation in the case that an I/O containing lbas that are invalid, > point to data in

Re: [PATCH v1 3/6] ASoC: codecs: msm8916-wcd-analog: move codec reset to probe

On 28/07/17 14:40, Mark Brown wrote: On Wed, Jul 26, 2017 at 02:35:09AM +0200, srinivas.kandaga...@linaro.org wrote: From: Srinivas Kandagatla This patch move the codec reset code from dai ops to codec probe, so that the codec is not held in reset when

Re: [PATCH v1 3/6] ASoC: codecs: msm8916-wcd-analog: move codec reset to probe

On 28/07/17 14:40, Mark Brown wrote: On Wed, Jul 26, 2017 at 02:35:09AM +0200, srinivas.kandaga...@linaro.org wrote: From: Srinivas Kandagatla This patch move the codec reset code from dai ops to codec probe, so that the codec is not held in reset when headset detection block is still

Re: [PATCH v2] cpuset: fix a deadlock due to incomplete patching of cpusets_enabled()

On 07/28/2017 11:30 AM, Peter Zijlstra wrote: > On Fri, Jul 28, 2017 at 09:45:16AM +0200, Vlastimil Babka wrote: >> [+CC PeterZ] >> >> On 07/27/2017 06:46 PM, Dima Zavin wrote: >>> In codepaths that use the begin/retry interface for reading >>> mems_allowed_seq with irqs disabled, there exists a

Re: [PATCH v2] cpuset: fix a deadlock due to incomplete patching of cpusets_enabled()

On 07/28/2017 11:30 AM, Peter Zijlstra wrote: > On Fri, Jul 28, 2017 at 09:45:16AM +0200, Vlastimil Babka wrote: >> [+CC PeterZ] >> >> On 07/27/2017 06:46 PM, Dima Zavin wrote: >>> In codepaths that use the begin/retry interface for reading >>> mems_allowed_seq with irqs disabled, there exists a

Re: pull-request: wireless-drivers-next 2017-07-28

Kalle Valo writes: > Hi Dave, > > here's a pull request for net, more info the signed tag below. Please > let me know if there are any problems. > > Kalle > > The following changes since commit d755cbc26e8295ae8e5d30425364e093b4247a85: > > Merge tag

Re: pull-request: wireless-drivers-next 2017-07-28

Kalle Valo writes: > Hi Dave, > > here's a pull request for net, more info the signed tag below. Please > let me know if there are any problems. > > Kalle > > The following changes since commit d755cbc26e8295ae8e5d30425364e093b4247a85: > > Merge tag 'iwlwifi-for-kalle-2017-07-21' of >

[PATCH -tip v7 1/2] irq: Make irqentry text section unconditional

Generate irqentry and softirqentry text sections without any configs. This will add above extra sections, but no performace impact. Signed-off-by: Masami Hiramatsu Suggested-by: Ingo Molnar --- Changes in v7: - fix arch/x86/kernel/unwind_frame.c too

[PATCH -tip v7 1/2] irq: Make irqentry text section unconditional

Generate irqentry and softirqentry text sections without any configs. This will add above extra sections, but no performace impact. Signed-off-by: Masami Hiramatsu Suggested-by: Ingo Molnar --- Changes in v7: - fix arch/x86/kernel/unwind_frame.c too --- arch/arm/include/asm/traps.h |

pull-request: wireless-drivers-next 2017-07-28

Hi Dave, here's a pull request for net, more info the signed tag below. Please let me know if there are any problems. Kalle The following changes since commit d755cbc26e8295ae8e5d30425364e093b4247a85: Merge tag 'iwlwifi-for-kalle-2017-07-21' of

pull-request: wireless-drivers-next 2017-07-28

Hi Dave, here's a pull request for net, more info the signed tag below. Please let me know if there are any problems. Kalle The following changes since commit d755cbc26e8295ae8e5d30425364e093b4247a85: Merge tag 'iwlwifi-for-kalle-2017-07-21' of

Re: [PATCH v1 4/6] ASoC: codecs: msm8916-wcd-analog: set default micbias voltage to 1.8

On Fri, Jul 28, 2017 at 02:54:59PM +0100, Srinivas Kandagatla wrote: > On 28/07/17 14:40, Mark Brown wrote: > > On Wed, Jul 26, 2017 at 02:35:10AM +0200, srinivas.kandaga...@linaro.org > > wrote: > > > From: Srinivas Kandagatla > > > This patch sets the default

Re: [PATCH v1 4/6] ASoC: codecs: msm8916-wcd-analog: set default micbias voltage to 1.8

On Fri, Jul 28, 2017 at 02:54:59PM +0100, Srinivas Kandagatla wrote: > On 28/07/17 14:40, Mark Brown wrote: > > On Wed, Jul 26, 2017 at 02:35:10AM +0200, srinivas.kandaga...@linaro.org > > wrote: > > > From: Srinivas Kandagatla > > > This patch sets the default internal micbias voltage to 1.8v.

Re: [PATCH -tip v6 1/2] irq: Make irqentry text section unconditional

On Fri, 28 Jul 2017 21:24:54 +0900 Masami Hiramatsu wrote: > Generate irqentry and softirqentry text sections without > any configs. This will add above extra sections, but > no performace impact. > > Signed-off-by: Masami Hiramatsu > Suggested-by:

Re: [PATCH -tip v6 1/2] irq: Make irqentry text section unconditional

On Fri, 28 Jul 2017 21:24:54 +0900 Masami Hiramatsu wrote: > Generate irqentry and softirqentry text sections without > any configs. This will add above extra sections, but > no performace impact. > > Signed-off-by: Masami Hiramatsu > Suggested-by: Ingo Molnar > --- >

Re: Possible race condition in oom-killer

Michal Hocko wrote: > On Fri 28-07-17 22:15:01, Tetsuo Handa wrote: > > task_will_free_mem(current) in out_of_memory() returning false due to > > MMF_OOM_SKIP already set allowed each thread sharing that mm to select a new > > OOM victim. If task_will_free_mem(current) in out_of_memory() did not

Re: Possible race condition in oom-killer

Michal Hocko wrote: > On Fri 28-07-17 22:15:01, Tetsuo Handa wrote: > > task_will_free_mem(current) in out_of_memory() returning false due to > > MMF_OOM_SKIP already set allowed each thread sharing that mm to select a new > > OOM victim. If task_will_free_mem(current) in out_of_memory() did not

Re: [PATCH 0/3] net-next: stmmac: support future possible different internal phy mode

On Fri, Jul 28, 2017 at 11:28:15AM +0200, Corentin Labbe wrote: > Hello > > The current way to find if the phy is internal is to compare DT phy-mode > and emac_variant/internal_phy. > But it will negate a possible future SoC where an external PHY use the > same phy mode than the internal one. >

Re: [PATCH 0/3] net-next: stmmac: support future possible different internal phy mode

On Fri, Jul 28, 2017 at 11:28:15AM +0200, Corentin Labbe wrote: > Hello > > The current way to find if the phy is internal is to compare DT phy-mode > and emac_variant/internal_phy. > But it will negate a possible future SoC where an external PHY use the > same phy mode than the internal one. >

[PATCH 1/2] ARM64: dts: meson-gxl-khadas-vim: Add GPIO lines names

This patch describes the GPIO lines usage on the Khadas VIM board. This is useful in the debugfs gpio file and using the cdev gpio API. Signed-off-by: Neil Armstrong --- .../dts/amlogic/meson-gxl-s905x-khadas-vim.dts | 56 ++ 1 file changed, 56

[PATCH 0/2] ARM64: dts: meson-gx: Add GPIO names for SBCs

This patchset adds the GPIO line names like the Odroid-C2 previous patch, for the Khadas VIM and Nanopi K2 boards. Neil Armstrong (2): ARM64: dts: meson-gxl-khadas-vim: Add GPIO lines names ARM64: dts: meson-gxbb-nanopi-k2: Add GPIO lines names .../boot/dts/amlogic/meson-gxbb-nanopi-k2.dts

[PATCH 1/2] ARM64: dts: meson-gxl-khadas-vim: Add GPIO lines names

This patch describes the GPIO lines usage on the Khadas VIM board. This is useful in the debugfs gpio file and using the cdev gpio API. Signed-off-by: Neil Armstrong --- .../dts/amlogic/meson-gxl-s905x-khadas-vim.dts | 56 ++ 1 file changed, 56 insertions(+) diff --git

[PATCH 0/2] ARM64: dts: meson-gx: Add GPIO names for SBCs

This patchset adds the GPIO line names like the Odroid-C2 previous patch, for the Khadas VIM and Nanopi K2 boards. Neil Armstrong (2): ARM64: dts: meson-gxl-khadas-vim: Add GPIO lines names ARM64: dts: meson-gxbb-nanopi-k2: Add GPIO lines names .../boot/dts/amlogic/meson-gxbb-nanopi-k2.dts

Re: [PATCH v1 4/6] ASoC: codecs: msm8916-wcd-analog: set default micbias voltage to 1.8

On 28/07/17 14:40, Mark Brown wrote: On Wed, Jul 26, 2017 at 02:35:10AM +0200, srinivas.kandaga...@linaro.org wrote: From: Srinivas Kandagatla This patch sets the default internal micbias voltage to 1.8v. This default value is required for mbhc buttons to

Re: [PATCH v1 4/6] ASoC: codecs: msm8916-wcd-analog: set default micbias voltage to 1.8

On 28/07/17 14:40, Mark Brown wrote: On Wed, Jul 26, 2017 at 02:35:10AM +0200, srinivas.kandaga...@linaro.org wrote: From: Srinivas Kandagatla This patch sets the default internal micbias voltage to 1.8v. This default value is required for mbhc buttons to work. Also adds dt bindings to

[PATCH 2/2] ARM64: dts: meson-gxbb-nanopi-k2: Add GPIO lines names

This patch describes the GPIO lines usage on the Nanopi K2 board. This is useful in the debugfs gpio file and using the cdev gpio API. Signed-off-by: Neil Armstrong --- .../boot/dts/amlogic/meson-gxbb-nanopi-k2.dts | 58 ++ 1 file changed, 58

[PATCH 2/2] ARM64: dts: meson-gxbb-nanopi-k2: Add GPIO lines names

This patch describes the GPIO lines usage on the Nanopi K2 board. This is useful in the debugfs gpio file and using the cdev gpio API. Signed-off-by: Neil Armstrong --- .../boot/dts/amlogic/meson-gxbb-nanopi-k2.dts | 58 ++ 1 file changed, 58 insertions(+) diff --git

Re: [PATCH 4.4 66/90] powerpc/numa: Fix percpu allocations to be NUMA aware

JFYI. We have encountered a regression after applying this patch on a large ppc machine. While the patch is the right thing to do it doesn't work well with the current vmalloc area size on ppc and large machines where NUMA nodes are very far from each other. Just for the reference the boot fails

Re: [PATCH 4.4 66/90] powerpc/numa: Fix percpu allocations to be NUMA aware

JFYI. We have encountered a regression after applying this patch on a large ppc machine. While the patch is the right thing to do it doesn't work well with the current vmalloc area size on ppc and large machines where NUMA nodes are very far from each other. Just for the reference the boot fails

Re: [PATCH] crypto/rng: ensure that the RNG is ready before using

On Sun, Jul 16, 2017 at 07:22:06PM +0200, Jason A. Donenfeld wrote: > Otherwise, we might be seeding the RNG using bad randomness, which is > dangerous. The one use of this function from within the kernel -- not > from userspace -- is being removed (keys/big_key), so that call site > isn't

Re: [PATCH] crypto/rng: ensure that the RNG is ready before using

On Sun, Jul 16, 2017 at 07:22:06PM +0200, Jason A. Donenfeld wrote: > Otherwise, we might be seeding the RNG using bad randomness, which is > dangerous. The one use of this function from within the kernel -- not > from userspace -- is being removed (keys/big_key), so that call site > isn't

Re: [PATCH v2 2/2] crypto: engine - Permit to enqueue skcipher request

On Fri, Jul 14, 2017 at 01:15:36PM +0200, Corentin Labbe wrote: > On Fri, Jun 23, 2017 at 02:48:37PM +0800, Herbert Xu wrote: > > On Mon, Jun 19, 2017 at 09:55:24AM +0200, Corentin Labbe wrote: > > > > > > Since there are two different user of "crypto engine + ablkcipher", it > > > will be not

Re: [PATCH v2 2/2] crypto: engine - Permit to enqueue skcipher request

On Fri, Jul 14, 2017 at 01:15:36PM +0200, Corentin Labbe wrote: > On Fri, Jun 23, 2017 at 02:48:37PM +0800, Herbert Xu wrote: > > On Mon, Jun 19, 2017 at 09:55:24AM +0200, Corentin Labbe wrote: > > > > > > Since there are two different user of "crypto engine + ablkcipher", it > > > will be not

Re: [PATCH v1 5/6] ASoC: codecs: msm8916-wcd-analog: add MBHC support

On Wed, Jul 26, 2017 at 02:35:11AM +0200, srinivas.kandaga...@linaro.org wrote: > + if (wcd->hphl_jack_type_normally_open) > + plug_type = CDC_A_HPHL_PLUG_TYPE_NO; > + > + if (wcd->gnd_jack_type_normally_open) > + plug_type |= CDC_A_GND_PLUG_TYPE_NO; It'd be

Re: [PATCH v1 5/6] ASoC: codecs: msm8916-wcd-analog: add MBHC support

On Wed, Jul 26, 2017 at 02:35:11AM +0200, srinivas.kandaga...@linaro.org wrote: > + if (wcd->hphl_jack_type_normally_open) > + plug_type = CDC_A_HPHL_PLUG_TYPE_NO; > + > + if (wcd->gnd_jack_type_normally_open) > + plug_type |= CDC_A_GND_PLUG_TYPE_NO; It'd be

Re: Possible race condition in oom-killer

Hi Michal, On 7/28/2017 6:02 PM, Michal Hocko wrote: [CC linux-mm] On Fri 28-07-17 17:22:25, Manish Jaggi wrote: was: Re: [PATCH] mm, oom: allow oom reaper to race with exit_mmap Hi Michal, On 7/27/2017 2:54 PM, Michal Hocko wrote: On Thu 27-07-17 13:59:09, Manish Jaggi wrote: [...] With

Re: Possible race condition in oom-killer

Hi Michal, On 7/28/2017 6:02 PM, Michal Hocko wrote: [CC linux-mm] On Fri 28-07-17 17:22:25, Manish Jaggi wrote: was: Re: [PATCH] mm, oom: allow oom reaper to race with exit_mmap Hi Michal, On 7/27/2017 2:54 PM, Michal Hocko wrote: On Thu 27-07-17 13:59:09, Manish Jaggi wrote: [...] With

Re: [PATCH v4 10/10] x86/mm: Try to preserve old TLB entries using PCID

On Wed, Jul 05, 2017 at 09:10:00AM -0700, Andy Lutomirski wrote: > On Wed, Jul 5, 2017 at 5:25 AM, Peter Zijlstra wrote: > > On Thu, Jun 29, 2017 at 08:53:22AM -0700, Andy Lutomirski wrote: > >> +static void choose_new_asid(struct mm_struct *next, u64 next_tlb_gen, > >> +

Re: [PATCH v4 10/10] x86/mm: Try to preserve old TLB entries using PCID

On Wed, Jul 05, 2017 at 09:10:00AM -0700, Andy Lutomirski wrote: > On Wed, Jul 5, 2017 at 5:25 AM, Peter Zijlstra wrote: > > On Thu, Jun 29, 2017 at 08:53:22AM -0700, Andy Lutomirski wrote: > >> +static void choose_new_asid(struct mm_struct *next, u64 next_tlb_gen, > >> +

Re: [PATCH 0/2] STM32 HASH crypto driver

On Thu, Jul 13, 2017 at 03:32:25PM +0200, Lionel Debieve wrote: > This set of patches adds a new crypto driver for STMicroelectronics stm32 HW. > This drivers uses the crypto API and provides with HW-enabled md5, sha1, > sha224, sha256 hash based algorithms. > It makes use of the crypto engine to

Re: [PATCH 0/2] STM32 HASH crypto driver

On Thu, Jul 13, 2017 at 03:32:25PM +0200, Lionel Debieve wrote: > This set of patches adds a new crypto driver for STMicroelectronics stm32 HW. > This drivers uses the crypto API and provides with HW-enabled md5, sha1, > sha224, sha256 hash based algorithms. > It makes use of the crypto engine to

Re: [PATCH 0/3] STM32 CRC update

On Thu, Jul 13, 2017 at 03:06:30PM +0200, Lionel Debieve wrote: > This set of patches update the STM32 CRC driver. > It contains two corrections and one global Kconfig rework. > First correction is about the relaxed usage in scope of arm > platform usage, second about a unbind driver issue. > Last

Re: [PATCH 0/3] STM32 CRC update

On Thu, Jul 13, 2017 at 03:06:30PM +0200, Lionel Debieve wrote: > This set of patches update the STM32 CRC driver. > It contains two corrections and one global Kconfig rework. > First correction is about the relaxed usage in scope of arm > platform usage, second about a unbind driver issue. > Last

Re: [PATCH v2] crypto: caam - free qman_fq after kill_fq

On Thu, Jul 13, 2017 at 05:21:01AM -0400, Xulin Sun wrote: > kill_fq removes a complete frame queue, it needs to free the qman_fq > in the last. Else kmemleak will report the below warning: > > unreferenced object 0x800073085c80 (size 128): > comm "cryptomgr_test", pid 199, jiffies

Re: [PATCH v2] crypto: caam - free qman_fq after kill_fq

On Thu, Jul 13, 2017 at 05:21:01AM -0400, Xulin Sun wrote: > kill_fq removes a complete frame queue, it needs to free the qman_fq > in the last. Else kmemleak will report the below warning: > > unreferenced object 0x800073085c80 (size 128): > comm "cryptomgr_test", pid 199, jiffies

Re: [PATCH 0/3] net-next: stmmac: support future possible different internal phy mode

On Fri, Jul 28, 2017 at 05:53:40PM +0800, Chen-Yu Tsai wrote: > On Fri, Jul 28, 2017 at 5:28 PM, Corentin Labbe > wrote: > > Hello > > > > The current way to find if the phy is internal is to compare DT phy-mode > > and emac_variant/internal_phy. > > But it will negate

Re: [PATCH 0/3] net-next: stmmac: support future possible different internal phy mode

On Fri, Jul 28, 2017 at 05:53:40PM +0800, Chen-Yu Tsai wrote: > On Fri, Jul 28, 2017 at 5:28 PM, Corentin Labbe > wrote: > > Hello > > > > The current way to find if the phy is internal is to compare DT phy-mode > > and emac_variant/internal_phy. > > But it will negate a possible future SoC where

Re: [PATCH 1/3] perf tools: Add callchain to ctf conversion

On 07/28/2017 05:25 AM, Jiri Olsa wrote: > On Thu, Jul 27, 2017 at 02:12:03PM -0400, Geneviève Bastien wrote: >> The field perf_callchain, if available, is added to the sampling >> events during the CTF conversion. It is an array of u64 values. >> The perf_callchain_size field contains the size

Re: [PATCH 1/3] perf tools: Add callchain to ctf conversion

On 07/28/2017 05:25 AM, Jiri Olsa wrote: > On Thu, Jul 27, 2017 at 02:12:03PM -0400, Geneviève Bastien wrote: >> The field perf_callchain, if available, is added to the sampling >> events during the CTF conversion. It is an array of u64 values. >> The perf_callchain_size field contains the size

Re: [PATCH v1 4/6] ASoC: codecs: msm8916-wcd-analog: set default micbias voltage to 1.8

On Wed, Jul 26, 2017 at 02:35:10AM +0200, srinivas.kandaga...@linaro.org wrote: > From: Srinivas Kandagatla > > This patch sets the default internal micbias voltage to 1.8v. This > default value is required for mbhc buttons to work. Also adds dt > bindings to

Re: [PATCH v1 4/6] ASoC: codecs: msm8916-wcd-analog: set default micbias voltage to 1.8

On Wed, Jul 26, 2017 at 02:35:10AM +0200, srinivas.kandaga...@linaro.org wrote: > From: Srinivas Kandagatla > > This patch sets the default internal micbias voltage to 1.8v. This > default value is required for mbhc buttons to work. Also adds dt > bindings to allow the board level file to

Re: [PATCH v1 3/6] ASoC: codecs: msm8916-wcd-analog: move codec reset to probe

On Wed, Jul 26, 2017 at 02:35:09AM +0200, srinivas.kandaga...@linaro.org wrote: > From: Srinivas Kandagatla > > This patch move the codec reset code from dai ops to codec probe, so > that the codec is not held in reset when headset detection block is > still

Re: [PATCH v1 3/6] ASoC: codecs: msm8916-wcd-analog: move codec reset to probe

On Wed, Jul 26, 2017 at 02:35:09AM +0200, srinivas.kandaga...@linaro.org wrote: > From: Srinivas Kandagatla > > This patch move the codec reset code from dai ops to codec probe, so > that the codec is not held in reset when headset detection block is > still active. This means that the CODEC

Re: [media] vimc: API proposal, configuring the topology from user space

Hi Helen, Finally after way too long I found some time to review this. See my comments below. On 04/11/2017 12:53 AM, Helen Koike wrote: > > Hi, > > Continuing the discussion about the API of the vimc driver, I made some > changes > based on the previous comments, please see below and let me

Re: [media] vimc: API proposal, configuring the topology from user space

Hi Helen, Finally after way too long I found some time to review this. See my comments below. On 04/11/2017 12:53 AM, Helen Koike wrote: > > Hi, > > Continuing the discussion about the API of the vimc driver, I made some > changes > based on the previous comments, please see below and let me

Re: [PATCH net-next v2 01/10] net: dsa: lan9303: Fixed MDIO interface

On Fri, Jul 28, 2017 at 01:08:25PM +0200, Egil Hjelmeland wrote: > On 26. juli 2017 18:55, Andrew Lunn wrote: > >On Tue, Jul 25, 2017 at 06:15:44PM +0200, Egil Hjelmeland wrote: > >It is better to use mdiobus_read/write or if you are nesting mdio > >busses,

Re: [PATCH net-next v2 01/10] net: dsa: lan9303: Fixed MDIO interface

On Fri, Jul 28, 2017 at 01:08:25PM +0200, Egil Hjelmeland wrote: > On 26. juli 2017 18:55, Andrew Lunn wrote: > >On Tue, Jul 25, 2017 at 06:15:44PM +0200, Egil Hjelmeland wrote: > >It is better to use mdiobus_read/write or if you are nesting mdio > >busses,

[net-next PATCH] IB/hns: include linux/interrupt.h

I ran into this build error on linux-next: drivers/infiniband/hw/hns/hns_roce_eq.c:477:8: error: unknown type name 'irqreturn_t' static irqreturn_t hns_roce_msi_x_interrupt(int irq, void *eq_ptr) ^~~ drivers/infiniband/hw/hns/hns_roce_eq.c: In function

[net-next PATCH] IB/hns: include linux/interrupt.h

I ran into this build error on linux-next: drivers/infiniband/hw/hns/hns_roce_eq.c:477:8: error: unknown type name 'irqreturn_t' static irqreturn_t hns_roce_msi_x_interrupt(int irq, void *eq_ptr) ^~~ drivers/infiniband/hw/hns/hns_roce_eq.c: In function

<    4   5   6   7   8   9   10   11   12   13   >