Re: [PATCH v3 05/16] mtd: rawnand: qcom: remove dt property nand-ecc-step-size

On 2018-05-26 14:12, Miquel Raynal wrote: Hi Abhishek, On Fri, 25 May 2018 17:51:33 +0530, Abhishek Sahu wrote: QCOM NAND controller supports only one step size (512) so nand-ecc-step-size DT property is redundant. This property can be removed and ecc step size can be

Re: [PATCH v3 05/16] mtd: rawnand: qcom: remove dt property nand-ecc-step-size

On 2018-05-26 14:12, Miquel Raynal wrote: Hi Abhishek, On Fri, 25 May 2018 17:51:33 +0530, Abhishek Sahu wrote: QCOM NAND controller supports only one step size (512) so nand-ecc-step-size DT property is redundant. This property can be removed and ecc step size can be assigned with 512

Re: [PATCH v3 03/16] dt-bindings: qcom_nandc: make nand-ecc-strength optional

On 2018-05-26 14:12, Miquel Raynal wrote: Hi Abhishek, On Fri, 25 May 2018 17:51:31 +0530, Abhishek Sahu wrote: If nand-ecc-strength specified in DT, then controller will use this ECC strength otherwise ECC strength will be calculated according to chip requirement and

Re: [PATCH v3 03/16] dt-bindings: qcom_nandc: make nand-ecc-strength optional

On 2018-05-26 14:12, Miquel Raynal wrote: Hi Abhishek, On Fri, 25 May 2018 17:51:31 +0530, Abhishek Sahu wrote: If nand-ecc-strength specified in DT, then controller will use this ECC strength otherwise ECC strength will be calculated according to chip requirement and available OOB size.

Re: [PATCH v3 01/16] mtd: rawnand: helper function for setting up ECC configuration

On 2018-05-26 14:12, Miquel Raynal wrote: Hi Abhishek, On Fri, 25 May 2018 17:51:29 +0530, Abhishek Sahu wrote: commit 2c8f8afa7f92 ("mtd: nand: add generic helpers to check, match, maximize ECC settings") provides generic helpers which drivers can use for setting up

Re: [PATCH v3 01/16] mtd: rawnand: helper function for setting up ECC configuration

On 2018-05-26 14:12, Miquel Raynal wrote: Hi Abhishek, On Fri, 25 May 2018 17:51:29 +0530, Abhishek Sahu wrote: commit 2c8f8afa7f92 ("mtd: nand: add generic helpers to check, match, maximize ECC settings") provides generic helpers which drivers can use for setting up ECC parameters. Since

[PATCH 3/3] thermal: broadcom: Add Stingray thermal driver

From: Pramod Kumar This commit adds stingray thermal driver to monitor six thermal zones temperature and trips at critical temperature. Signed-off-by: Pramod Kumar Signed-off-by: Srinath Mannam Reviewed-by: Ray

[PATCH 2/3] arm64: dts: stingray: Add Stingray Thermal DT support.

From: Pramod Kumar Add DT nodes for thermal zones memory base address to read temperature. Signed-off-by: Pramod Kumar Reviewed-by: Ray Jui Reviewed-by: Scott Branden Reviewed-by: Srinath

[PATCH 3/3] thermal: broadcom: Add Stingray thermal driver

From: Pramod Kumar This commit adds stingray thermal driver to monitor six thermal zones temperature and trips at critical temperature. Signed-off-by: Pramod Kumar Signed-off-by: Srinath Mannam Reviewed-by: Ray Jui Reviewed-by: Scott Branden Reviewed-by: Vikram Prakash ---

[PATCH 2/3] arm64: dts: stingray: Add Stingray Thermal DT support.

From: Pramod Kumar Add DT nodes for thermal zones memory base address to read temperature. Signed-off-by: Pramod Kumar Reviewed-by: Ray Jui Reviewed-by: Scott Branden Reviewed-by: Srinath Mannam --- .../arm64/boot/dts/broadcom/stingray/stingray.dtsi | 37 ++ 1 file

[PATCH 1/3] dt-bindings: thermal: Add binding document for SR thermal

From: Pramod Kumar Add binding document for supported thermal implementation in Stingray. Signed-off-by: Pramod Kumar Reviewed-by: Ray Jui Reviewed-by: Scott Branden Reviewed-by: Srinath

[PATCH 1/3] dt-bindings: thermal: Add binding document for SR thermal

From: Pramod Kumar Add binding document for supported thermal implementation in Stingray. Signed-off-by: Pramod Kumar Reviewed-by: Ray Jui Reviewed-by: Scott Branden Reviewed-by: Srinath Mannam --- .../bindings/thermal/brcm,sr-thermal.txt | 45 ++ 1 file

[PATCH 0/3] Stingray thermal driver support

These patches adds the stingray thermal driver and its corresponding DT nodes with documentation. Pramod Kumar (3): dt-bindings: thermal: Add binding document for SR thermal arm64: dts: stingray: Add Stingray Thermal DT support. thermal: broadcom: Add Stingray thermal driver

[PATCH 0/3] Stingray thermal driver support

These patches adds the stingray thermal driver and its corresponding DT nodes with documentation. Pramod Kumar (3): dt-bindings: thermal: Add binding document for SR thermal arm64: dts: stingray: Add Stingray Thermal DT support. thermal: broadcom: Add Stingray thermal driver

Re: [PATCH 04/11] PM / devfreq: Remove redundant frequency adjustment from governors

Hi, On 2018년 05월 26일 05:30, Matthias Kaehlcke wrote: > The userspace and simpleondemand governor determine a target frequency and > then adjust it according to the df->min/max_freq limits that might have > been set by user space. This adjustment is redundant, it is done in > update_devfreq() for

Re: [PATCH 04/11] PM / devfreq: Remove redundant frequency adjustment from governors

Hi, On 2018년 05월 26일 05:30, Matthias Kaehlcke wrote: > The userspace and simpleondemand governor determine a target frequency and > then adjust it according to the df->min/max_freq limits that might have > been set by user space. This adjustment is redundant, it is done in > update_devfreq() for

Re: [PATCH v9 01/10] drivers: qcom: rpmh-rsc: add RPMH controller for QCOM SoCs

Hi, On 5/24/2018 4:15 PM, Raju P L S S S N wrote: From: Lina Iyer Add controller driver for QCOM SoCs that have hardware based shared resource management. The hardware IP known as RSC (Resource State Coordinator) houses multiple Direct Resource Voter (DRV) for different

Re: [PATCH v9 01/10] drivers: qcom: rpmh-rsc: add RPMH controller for QCOM SoCs

Hi, On 5/24/2018 4:15 PM, Raju P L S S S N wrote: From: Lina Iyer Add controller driver for QCOM SoCs that have hardware based shared resource management. The hardware IP known as RSC (Resource State Coordinator) houses multiple Direct Resource Voter (DRV) for different execution levels. A

Re: B53 DSA switch problem on Banana Pi-R1 on Fedora 26 - systemd-networkd problem

On 27.05.2018 22:31, Florian Fainelli wrote: Le 05/27/18 à 12:01, Gerhard Wiesinger a écrit : On 24.05.2018 08:22, Gerhard Wiesinger wrote: On 24.05.2018 07:29, Gerhard Wiesinger wrote: After some analysis with Florian (thnx) we found out that the current implementation is broken:

Re: B53 DSA switch problem on Banana Pi-R1 on Fedora 26 - systemd-networkd problem

On 27.05.2018 22:31, Florian Fainelli wrote: Le 05/27/18 à 12:01, Gerhard Wiesinger a écrit : On 24.05.2018 08:22, Gerhard Wiesinger wrote: On 24.05.2018 07:29, Gerhard Wiesinger wrote: After some analysis with Florian (thnx) we found out that the current implementation is broken:

Can I use 'signed -off-by' to define maintainers' workload?

Hi all, I am a student from Peking University. I'm not sure if it's appropriate to ask questions here. I have already tried other mailing lists, but I got no reply. I am very sorry to bother all of you. I am doing a research about the maintainers' workload in the Linux kernel community. We all

Can I use 'signed -off-by' to define maintainers' workload?

Hi all, I am a student from Peking University. I'm not sure if it's appropriate to ask questions here. I have already tried other mailing lists, but I got no reply. I am very sorry to bother all of you. I am doing a research about the maintainers' workload in the Linux kernel community. We all

Re: [PATCH 03/11] PM / devfreq: Remove check for df->max_freq == 0 from governors

Hi, On 2018년 05월 26일 05:30, Matthias Kaehlcke wrote: > Commit "PM / devfreq: Fix handling of min/max_freq == 0" ensures that > df->max_freq is not 0, remove unnecessary checks. > > Signed-off-by: Matthias Kaehlcke > --- > drivers/devfreq/governor_performance.c| 5 + >

Re: [PATCH 03/11] PM / devfreq: Remove check for df->max_freq == 0 from governors

Hi, On 2018년 05월 26일 05:30, Matthias Kaehlcke wrote: > Commit "PM / devfreq: Fix handling of min/max_freq == 0" ensures that > df->max_freq is not 0, remove unnecessary checks. > > Signed-off-by: Matthias Kaehlcke > --- > drivers/devfreq/governor_performance.c| 5 + >

Re: [PATCH 01/11] PM / devfreq: Init user limits from OPP limits, not viceversa

Hi, On 2018년 05월 26일 05:30, Matthias Kaehlcke wrote: > Commit ab8f58ad72c4 ("PM / devfreq: Set min/max_freq when adding > the devfreq device") introduced the initialization of the user > limits min/max_freq from the lowest/highest available OPPs. Later > commit f1d981eaecf8 ("PM / devfreq: Use

Re: [RFC PATCH] m68k: set dma and coherent masks for Macintosh SONIC based ethernet

On Sat, May 26, 2018 at 09:15:05PM -0700, Guenter Roeck wrote: > Good point. Maybe it would be better to limit the warning to SMP systems > instead of (unnecessarily) fixing drivers all over the place ? No. The coherent_dma_mask is the mask used for dma_alloc_coherent and dma_alloc_attrs. It

Re: [PATCH 01/11] PM / devfreq: Init user limits from OPP limits, not viceversa

Hi, On 2018년 05월 26일 05:30, Matthias Kaehlcke wrote: > Commit ab8f58ad72c4 ("PM / devfreq: Set min/max_freq when adding > the devfreq device") introduced the initialization of the user > limits min/max_freq from the lowest/highest available OPPs. Later > commit f1d981eaecf8 ("PM / devfreq: Use

Re: [RFC PATCH] m68k: set dma and coherent masks for Macintosh SONIC based ethernet

On Sat, May 26, 2018 at 09:15:05PM -0700, Guenter Roeck wrote: > Good point. Maybe it would be better to limit the warning to SMP systems > instead of (unnecessarily) fixing drivers all over the place ? No. The coherent_dma_mask is the mask used for dma_alloc_coherent and dma_alloc_attrs. It

Re: [RFC PATCH] m68k: set dma and coherent masks for Macintosh SONIC based ethernet

On Mon, 28 May 2018, Michael Schmitz wrote: > Hi Finn, > > Am 27.05.2018 um 17:49 schrieb Finn Thain: > > On Sun, 27 May 2018, Michael Schmitz wrote: > > > >> That should have fixed the warning already ... > > > > It's still not fixed (hence my "acked-by" for Geunter's patch). > > > > Odd -

Re: [RFC PATCH] m68k: set dma and coherent masks for Macintosh SONIC based ethernet

On Mon, 28 May 2018, Michael Schmitz wrote: > Hi Finn, > > Am 27.05.2018 um 17:49 schrieb Finn Thain: > > On Sun, 27 May 2018, Michael Schmitz wrote: > > > >> That should have fixed the warning already ... > > > > It's still not fixed (hence my "acked-by" for Geunter's patch). > > > > Odd -

Re: B53 DSA switch problem on Banana Pi-R1 on Fedora 26 - systemd-networkd problem

On 27.05.2018 22:35, Florian Fainelli wrote: Le 05/27/18 à 12:18, Gerhard Wiesinger a écrit : On 27.05.2018 21:01, Gerhard Wiesinger wrote: On 24.05.2018 08:22, Gerhard Wiesinger wrote: On 24.05.2018 07:29, Gerhard Wiesinger wrote: After some analysis with Florian (thnx) we found out that

Re: B53 DSA switch problem on Banana Pi-R1 on Fedora 26 - systemd-networkd problem

On 27.05.2018 22:35, Florian Fainelli wrote: Le 05/27/18 à 12:18, Gerhard Wiesinger a écrit : On 27.05.2018 21:01, Gerhard Wiesinger wrote: On 24.05.2018 08:22, Gerhard Wiesinger wrote: On 24.05.2018 07:29, Gerhard Wiesinger wrote: After some analysis with Florian (thnx) we found out that

RE: [PATCH 08/11] PM / devfreq: Make update_devfreq() public

>Currently update_devfreq() is only visible to devfreq governors outside >of devfreq.c. Make it public to allow drivers that adjust devfreq policies >to cause a re-evaluation of the frequency after a policy change. > >Signed-off-by: Matthias Kaehlcke >--- >

RE: [PATCH 08/11] PM / devfreq: Make update_devfreq() public

>Currently update_devfreq() is only visible to devfreq governors outside >of devfreq.c. Make it public to allow drivers that adjust devfreq policies >to cause a re-evaluation of the frequency after a policy change. > >Signed-off-by: Matthias Kaehlcke >--- > drivers/devfreq/governor.h | 3 --- >

RE: [PATCH v11 00/26] Speculative page faults

Some regression and improvements is found by LKP-tools(linux kernel performance) on V9 patch series tested on Intel 4s Skylake platform. The regression result is sorted by the metric will-it-scale.per_thread_ops. Branch: Laurent-Dufour/Speculative-page-faults/20180316-151833 (V9 patch series)

RE: [PATCH v11 00/26] Speculative page faults

Some regression and improvements is found by LKP-tools(linux kernel performance) on V9 patch series tested on Intel 4s Skylake platform. The regression result is sorted by the metric will-it-scale.per_thread_ops. Branch: Laurent-Dufour/Speculative-page-faults/20180316-151833 (V9 patch series)

RE: [PATCH v2] dcdbas: Add support for WSMT ACPI table

> -Original Message- > From: Warzecha, Douglas > Sent: Friday, May 25, 2018 2:02 PM > To: Stuart Hayes > Cc: Limonciello, Mario; Dominguez, Jared; linux-kernel@vger.kernel.org > Subject: RE: [PATCH v2] dcdbas: Add support for WSMT ACPI table > > > On 05/16/2018 9:06 AM, Stuart Hayes

RE: [PATCH v2] dcdbas: Add support for WSMT ACPI table

> -Original Message- > From: Warzecha, Douglas > Sent: Friday, May 25, 2018 2:02 PM > To: Stuart Hayes > Cc: Limonciello, Mario; Dominguez, Jared; linux-kernel@vger.kernel.org > Subject: RE: [PATCH v2] dcdbas: Add support for WSMT ACPI table > > > On 05/16/2018 9:06 AM, Stuart Hayes

Re: [PATCH 3/3] s390:add missing CONFIG_STRICT_KERNEL_RWX for mark_rodata_ro

On Mon, May 28, 2018 at 11:33:55AM +0800, nixiaoming wrote: > Signed-off-by: nixiaoming Please do not submit patches without any changelog text. I do not accept such patches, but other maintainers might be easier... greg k-h

Re: [PATCH 3/3] s390:add missing CONFIG_STRICT_KERNEL_RWX for mark_rodata_ro

On Mon, May 28, 2018 at 11:33:55AM +0800, nixiaoming wrote: > Signed-off-by: nixiaoming Please do not submit patches without any changelog text. I do not accept such patches, but other maintainers might be easier... greg k-h

Re: [RFC PATCH] m68k: set dma and coherent masks for Macintosh SONIC based ethernet

Hi Finn, Am 27.05.2018 um 17:49 schrieb Finn Thain: > On Sun, 27 May 2018, Michael Schmitz wrote: > >> That should have fixed the warning already ... > > It's still not fixed (hence my "acked-by" for Geunter's patch). > Odd - does link order still matter even though the

Re: [RFC PATCH] m68k: set dma and coherent masks for Macintosh SONIC based ethernet

Hi Finn, Am 27.05.2018 um 17:49 schrieb Finn Thain: > On Sun, 27 May 2018, Michael Schmitz wrote: > >> That should have fixed the warning already ... > > It's still not fixed (hence my "acked-by" for Geunter's patch). > Odd - does link order still matter even though the

RE: [PATCH 07/11] PM / devfreg: Add support policy notifiers

>Policy notifiers are called before a frequency change and may narrow >the min/max frequency range in devfreq_policy, which is used to adjust >the target frequency if it is beyond this range. > >Also add a few helpers: > - devfreq_verify_within_[dev_]limits() >- should be used by the notifiers

RE: [PATCH 07/11] PM / devfreg: Add support policy notifiers

>Policy notifiers are called before a frequency change and may narrow >the min/max frequency range in devfreq_policy, which is used to adjust >the target frequency if it is beyond this range. > >Also add a few helpers: > - devfreq_verify_within_[dev_]limits() >- should be used by the notifiers

Re: [PATCH v3 1/2] rtmutex: allow specifying a subclass for nested locking

On Thu, May 24, 2018 at 03:52:39PM +0200, Peter Rosin wrote: > Needed for annotating rt_mutex locks. > > Signed-off-by: Peter Rosin > --- > include/linux/rtmutex.h | 7 +++ > kernel/locking/rtmutex.c | 29 + > 2 files changed, 32 insertions(+),

Re: [PATCH v3 1/2] rtmutex: allow specifying a subclass for nested locking

On Thu, May 24, 2018 at 03:52:39PM +0200, Peter Rosin wrote: > Needed for annotating rt_mutex locks. > > Signed-off-by: Peter Rosin > --- > include/linux/rtmutex.h | 7 +++ > kernel/locking/rtmutex.c | 29 + > 2 files changed, 32 insertions(+), 4 deletions(-) >

Re: [PATCH v2] Revert "alx: remove WoL support"

Hi all, Just inform you a news reported by a user who confirmed the wake up issue can't be reproduce by the new kernel. https://bugzilla.kernel.org/show_bug.cgi?id=61651#c126 Guillaume de Jabrun 2018-05-27 15:12:54 UTC I am using this patch for a long time. I was experiencing the "wake up

Re: [PATCH v2] Revert "alx: remove WoL support"

Hi all, Just inform you a news reported by a user who confirmed the wake up issue can't be reproduce by the new kernel. https://bugzilla.kernel.org/show_bug.cgi?id=61651#c126 Guillaume de Jabrun 2018-05-27 15:12:54 UTC I am using this patch for a long time. I was experiencing the "wake up

RE: [PATCH 05/11] PM / devfreq: governors: Return device frequency limits instead of user limits

>The performance, powersave and simpleondemand governors can return >df->min/max_freq, which are the user defined frequency limits. >update_devfreq() already takes care of adjusting the target frequency >with the user limits if necessary, therefore we can return >df->scaling_min/max_freq instead,

RE: [PATCH 05/11] PM / devfreq: governors: Return device frequency limits instead of user limits

>The performance, powersave and simpleondemand governors can return >df->min/max_freq, which are the user defined frequency limits. >update_devfreq() already takes care of adjusting the target frequency >with the user limits if necessary, therefore we can return >df->scaling_min/max_freq instead,

Re: [PATCH v14 1/2] cpufreq: Add Kryo CPU scaling driver

On 25-05-18, 15:41, Ilia Lin wrote: > In Certain QCOM SoCs like apq8096 and msm8996 that have KRYO processors, > the CPU frequency subset and voltage value of each OPP varies > based on the silicon variant in use. Qualcomm Process Voltage Scaling Tables > defines the voltage and frequency value

Re: [PATCH v14 1/2] cpufreq: Add Kryo CPU scaling driver

On 25-05-18, 15:41, Ilia Lin wrote: > In Certain QCOM SoCs like apq8096 and msm8996 that have KRYO processors, > the CPU frequency subset and voltage value of each OPP varies > based on the silicon variant in use. Qualcomm Process Voltage Scaling Tables > defines the voltage and frequency value

RE: [PATCH 04/11] PM / devfreq: Remove redundant frequency adjustment from governors

> The userspace and simpleondemand governor determine a target frequency and > then adjust it according to the df->min/max_freq limits that might have > been set by user space. This adjustment is redundant, it is done in > update_devfreq() for any governor, right after returning from >

RE: [PATCH 04/11] PM / devfreq: Remove redundant frequency adjustment from governors

> The userspace and simpleondemand governor determine a target frequency and > then adjust it according to the df->min/max_freq limits that might have > been set by user space. This adjustment is redundant, it is done in > update_devfreq() for any governor, right after returning from >

RE: [PATCH 03/11] PM / devfreq: Remove check for df->max_freq == 0 from governors

>Commit "PM / devfreq: Fix handling of min/max_freq == 0" ensures that >df->max_freq is not 0, remove unnecessary checks. > >Signed-off-by: Matthias Kaehlcke >--- > drivers/devfreq/governor_performance.c| 5 + > drivers/devfreq/governor_simpleondemand.c | 7 +++ > 2

RE: [PATCH 03/11] PM / devfreq: Remove check for df->max_freq == 0 from governors

>Commit "PM / devfreq: Fix handling of min/max_freq == 0" ensures that >df->max_freq is not 0, remove unnecessary checks. > >Signed-off-by: Matthias Kaehlcke >--- > drivers/devfreq/governor_performance.c| 5 + > drivers/devfreq/governor_simpleondemand.c | 7 +++ > 2 files changed, 4

Re: [PATCH] mm-kasan-dont-vfree-nonexistent-vm_area-fix

On Mon, 2018-05-28 at 12:13 +0800, Ian Kent wrote: > On Fri, 2018-05-25 at 20:48 -0700, Andrew Morton wrote: > > On Sat, 26 May 2018 11:31:35 +0800 kbuild test robot wrote: > > > > > Hi Andrey, > > > > > > I love your patch! Yet something to improve: > > > > > > [auto build

Re: [PATCH] mm-kasan-dont-vfree-nonexistent-vm_area-fix

On Mon, 2018-05-28 at 12:13 +0800, Ian Kent wrote: > On Fri, 2018-05-25 at 20:48 -0700, Andrew Morton wrote: > > On Sat, 26 May 2018 11:31:35 +0800 kbuild test robot wrote: > > > > > Hi Andrey, > > > > > > I love your patch! Yet something to improve: > > > > > > [auto build test ERROR on

Re: [PATCH] mm-kasan-dont-vfree-nonexistent-vm_area-fix

On Fri, 2018-05-25 at 20:48 -0700, Andrew Morton wrote: > On Sat, 26 May 2018 11:31:35 +0800 kbuild test robot wrote: > > > Hi Andrey, > > > > I love your patch! Yet something to improve: > > > > [auto build test ERROR on mmotm/master] > > [cannot apply to v4.17-rc6] > > [if

Re: [PATCH] mm-kasan-dont-vfree-nonexistent-vm_area-fix

On Fri, 2018-05-25 at 20:48 -0700, Andrew Morton wrote: > On Sat, 26 May 2018 11:31:35 +0800 kbuild test robot wrote: > > > Hi Andrey, > > > > I love your patch! Yet something to improve: > > > > [auto build test ERROR on mmotm/master] > > [cannot apply to v4.17-rc6] > > [if your patch is

RE: [PATCH 02/11] PM / devfreq: Fix handling of min/max_freq == 0

> Commit ab8f58ad72c4 ("PM / devfreq: Set min/max_freq when adding the > devfreq device") initializes df->min/max_freq with the min/max OPP when > the device is added. Later commit f1d981eaecf8 ("PM / devfreq: Use the > available min/max frequency") adds df->scaling_min/max_freq and the >

RE: [PATCH 02/11] PM / devfreq: Fix handling of min/max_freq == 0

> Commit ab8f58ad72c4 ("PM / devfreq: Set min/max_freq when adding the > devfreq device") initializes df->min/max_freq with the min/max OPP when > the device is added. Later commit f1d981eaecf8 ("PM / devfreq: Use the > available min/max frequency") adds df->scaling_min/max_freq and the >

[PATCH 1/3] arm64:add missing CONFIG_STRICT_KERNEL_RWX for mark_rodata_ro

Signed-off-by: nixiaoming --- arch/arm64/mm/mmu.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm64/mm/mmu.c b/arch/arm64/mm/mmu.c index 2dbb2c9..849f326 100644 --- a/arch/arm64/mm/mmu.c +++ b/arch/arm64/mm/mmu.c @@ -491,6 +491,7 @@ static void __init

[PATCH 2/3] x86:add missing CONFIG_STRICT_KERNEL_RWX for mark_rodata_ro

Signed-off-by: nixiaoming --- arch/x86/mm/init_32.c | 2 ++ arch/x86/mm/init_64.c | 2 ++ 2 files changed, 4 insertions(+) diff --git a/arch/x86/mm/init_32.c b/arch/x86/mm/init_32.c index c893c6a..121c567 100644 --- a/arch/x86/mm/init_32.c +++ b/arch/x86/mm/init_32.c @@

[PATCH 1/3] arm64:add missing CONFIG_STRICT_KERNEL_RWX for mark_rodata_ro

Signed-off-by: nixiaoming --- arch/arm64/mm/mmu.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/arm64/mm/mmu.c b/arch/arm64/mm/mmu.c index 2dbb2c9..849f326 100644 --- a/arch/arm64/mm/mmu.c +++ b/arch/arm64/mm/mmu.c @@ -491,6 +491,7 @@ static void __init map_mem(pgd_t *pgdp) #endif

[PATCH 2/3] x86:add missing CONFIG_STRICT_KERNEL_RWX for mark_rodata_ro

Signed-off-by: nixiaoming --- arch/x86/mm/init_32.c | 2 ++ arch/x86/mm/init_64.c | 2 ++ 2 files changed, 4 insertions(+) diff --git a/arch/x86/mm/init_32.c b/arch/x86/mm/init_32.c index c893c6a..121c567 100644 --- a/arch/x86/mm/init_32.c +++ b/arch/x86/mm/init_32.c @@ -920,6 +920,7 @@ static

[PATCH 3/3] s390:add missing CONFIG_STRICT_KERNEL_RWX for mark_rodata_ro

Signed-off-by: nixiaoming --- arch/s390/mm/init.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/s390/mm/init.c b/arch/s390/mm/init.c index 3fa3e53..a96fc3f 100644 --- a/arch/s390/mm/init.c +++ b/arch/s390/mm/init.c @@ -116,6 +116,7 @@ void __init

[PATCH 3/3] s390:add missing CONFIG_STRICT_KERNEL_RWX for mark_rodata_ro

Signed-off-by: nixiaoming --- arch/s390/mm/init.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/arch/s390/mm/init.c b/arch/s390/mm/init.c index 3fa3e53..a96fc3f 100644 --- a/arch/s390/mm/init.c +++ b/arch/s390/mm/init.c @@ -116,6 +116,7 @@ void __init paging_init(void)

Re: [PATCH] perf test 39 (Session topology) dumps core on s390

Hi Thomas, On 05/24/2018 07:26 PM, Thomas Richter wrote: > @@ -95,7 +98,7 @@ int test__session_topology(struct test *test > __maybe_unused, int subtest __maybe > { > char path[PATH_MAX]; > struct cpu_map *map; > - int ret = -1; > + int ret; This is failing for me:

Re: [PATCH] perf test 39 (Session topology) dumps core on s390

Hi Thomas, On 05/24/2018 07:26 PM, Thomas Richter wrote: > @@ -95,7 +98,7 @@ int test__session_topology(struct test *test > __maybe_unused, int subtest __maybe > { > char path[PATH_MAX]; > struct cpu_map *map; > - int ret = -1; > + int ret; This is failing for me:

[v2] ASoC: AMD: make channel 1 dma as circular

channel 1: SYSMEM<->ACP channel 2: ACP<->I2S Instead of waiting on period interrupt of ch 2 and then starting dma on ch1, we make ch1 dma as circular. This removes dependency of period granularity on hw pointer. Signed-off-by: Akshu Agrawal Reviewed-by: Daniel Kurtz

[v2] ASoC: AMD: make channel 1 dma as circular

channel 1: SYSMEM<->ACP channel 2: ACP<->I2S Instead of waiting on period interrupt of ch 2 and then starting dma on ch1, we make ch1 dma as circular. This removes dependency of period granularity on hw pointer. Signed-off-by: Akshu Agrawal Reviewed-by: Daniel Kurtz Tested-by: Daniel Kurtz ---

Re: [PATCH v2 2/5] gpio: syscon: Add gpio-syscon for rockchip

On 2018-05-24 8:18 PM, Heiko Stuebner wrote: Hi Levin, Am Donnerstag, 24. Mai 2018, 03:59:36 CEST schrieb Levin Du: Hi all, I'd like to quote reply of Robin Murphy at http://lists.infradead.org/pipermail/linux-rockchip/2018-May/020619.html I would suggest s/pin number/bit number in the

Re: [PATCH v2 2/5] gpio: syscon: Add gpio-syscon for rockchip

On 2018-05-24 8:18 PM, Heiko Stuebner wrote: Hi Levin, Am Donnerstag, 24. Mai 2018, 03:59:36 CEST schrieb Levin Du: Hi all, I'd like to quote reply of Robin Murphy at http://lists.infradead.org/pipermail/linux-rockchip/2018-May/020619.html I would suggest s/pin number/bit number in the

Re: [REGRESSION] (>= v4.12) IO w/dmcrypt causing audio underruns

On Thu, Jan 25, 2018 at 12:33:21AM -0800, vcap...@pengaru.com wrote: > On Fri, Jan 19, 2018 at 11:57:32AM +0100, Enric Balletbo Serra wrote: > > Hi Vito, > > > > 2018-01-17 23:48 GMT+01:00 : > > > On Mon, Dec 18, 2017 at 10:25:33AM +0100, Enric Balletbo Serra wrote: > > >>

Re: [REGRESSION] (>= v4.12) IO w/dmcrypt causing audio underruns

On Thu, Jan 25, 2018 at 12:33:21AM -0800, vcap...@pengaru.com wrote: > On Fri, Jan 19, 2018 at 11:57:32AM +0100, Enric Balletbo Serra wrote: > > Hi Vito, > > > > 2018-01-17 23:48 GMT+01:00 : > > > On Mon, Dec 18, 2017 at 10:25:33AM +0100, Enric Balletbo Serra wrote: > > >> Hi Vito, > > >> > > >>

[GIT PULL] nds32 fixes for 4.17

Linux 4.17-rc6 (2018-05-20 15:31:38 -0700) are available in the Git repository at: ssh://g...@gitolite.kernel.org/pub/scm/linux/kernel/git/greentime/linux.git tags/nds32-for-linus-4.17-fixes for you to fetch changes up to a30e7d1e37e8acc37c25420d93af218166cca3ae: nds32: Fix compiler

[GIT PULL] nds32 fixes for 4.17

Linux 4.17-rc6 (2018-05-20 15:31:38 -0700) are available in the Git repository at: ssh://g...@gitolite.kernel.org/pub/scm/linux/kernel/git/greentime/linux.git tags/nds32-for-linus-4.17-fixes for you to fetch changes up to a30e7d1e37e8acc37c25420d93af218166cca3ae: nds32: Fix compiler

Re: [PATCH] perf tools: Fix indexing for decoder packet queue

On Fri, May 25, 2018 at 05:10:54PM -0600, Mathieu Poirier wrote: > The tail of a queue is supposed to be pointing to the next available slot > in a queue. In this implementation the tail is incremented before it is > used and as such points to the last used element, something that has the >

Re: [PATCH] perf tools: Fix indexing for decoder packet queue

On Fri, May 25, 2018 at 05:10:54PM -0600, Mathieu Poirier wrote: > The tail of a queue is supposed to be pointing to the next available slot > in a queue. In this implementation the tail is incremented before it is > used and as such points to the last used element, something that has the >

Re: [PATCH] drivers/net/phy/micrel: Fix for PHY KSZ8061 errrata: Potential link-up failure when Ethernet cable is connected slowly

> This e-mail (including any attachments) is confidential and may be > legally privileged. If you are not an intended recipient or an > authorized representative of an intended recipient, you are > prohibited from using, copying or distributing the information in > this e-mail or its attachments.

Re: [PATCH] drivers/net/phy/micrel: Fix for PHY KSZ8061 errrata: Potential link-up failure when Ethernet cable is connected slowly

> This e-mail (including any attachments) is confidential and may be > legally privileged. If you are not an intended recipient or an > authorized representative of an intended recipient, you are > prohibited from using, copying or distributing the information in > this e-mail or its attachments.

Re: [PATCH v3 8/8] drm/mediatek: add third ddp path

Hi, Stu: On Mon, 2018-05-28 at 10:26 +0800, Stu Hsieh wrote: > Hi, CK: > I've some idea as below. > > On Fri, 2018-05-25 at 13:00 +0800, CK Hu wrote: > > Hi, Stu: > > > > On Fri, 2018-05-25 at 10:34 +0800, stu.hs...@mediatek.com wrote: > > > From: Stu Hsieh > > > > > >

Re: [PATCH v3 8/8] drm/mediatek: add third ddp path

Hi, Stu: On Mon, 2018-05-28 at 10:26 +0800, Stu Hsieh wrote: > Hi, CK: > I've some idea as below. > > On Fri, 2018-05-25 at 13:00 +0800, CK Hu wrote: > > Hi, Stu: > > > > On Fri, 2018-05-25 at 10:34 +0800, stu.hs...@mediatek.com wrote: > > > From: Stu Hsieh > > > > > > This patch create third

Re: [RESEND PATCH V5 00/33] block: support multipage bvec

On Sun, May 27, 2018 at 07:44:52PM -0600, Jens Axboe wrote: > On 5/27/18 1:23 AM, Ming Lei wrote: > > On Fri, May 25, 2018 at 10:30:46AM -0600, Jens Axboe wrote: > >> On 5/24/18 10:53 PM, Kent Overstreet wrote: > >>> On Fri, May 25, 2018 at 11:45:48AM +0800, Ming Lei wrote: > Hi, > >

Re: [RESEND PATCH V5 00/33] block: support multipage bvec

On Sun, May 27, 2018 at 07:44:52PM -0600, Jens Axboe wrote: > On 5/27/18 1:23 AM, Ming Lei wrote: > > On Fri, May 25, 2018 at 10:30:46AM -0600, Jens Axboe wrote: > >> On 5/24/18 10:53 PM, Kent Overstreet wrote: > >>> On Fri, May 25, 2018 at 11:45:48AM +0800, Ming Lei wrote: > Hi, > >

Re: [PATCHv4 1/2] ARM: imx53: add secure-reg-access support for PMU

On Tue, Feb 27, 2018 at 11:17:12AM +0100, Sebastian Reichel wrote: > Hi, > > On Tue, Feb 27, 2018 at 09:10:34AM +0800, Shawn Guo wrote: > > On Mon, Feb 26, 2018 at 02:47:41PM +0100, Sebastian Reichel wrote: > > > On Sat, Feb 24, 2018 at 03:45:44PM +0800, Shawn Guo wrote: > > > > On Mon, Feb 12,

Re: [PATCHv4 1/2] ARM: imx53: add secure-reg-access support for PMU

On Tue, Feb 27, 2018 at 11:17:12AM +0100, Sebastian Reichel wrote: > Hi, > > On Tue, Feb 27, 2018 at 09:10:34AM +0800, Shawn Guo wrote: > > On Mon, Feb 26, 2018 at 02:47:41PM +0100, Sebastian Reichel wrote: > > > On Sat, Feb 24, 2018 at 03:45:44PM +0800, Shawn Guo wrote: > > > > On Mon, Feb 12,

Re: [PATCH v3 8/8] drm/mediatek: add third ddp path

Hi, CK: I've some idea as below. On Fri, 2018-05-25 at 13:00 +0800, CK Hu wrote: > Hi, Stu: > > On Fri, 2018-05-25 at 10:34 +0800, stu.hs...@mediatek.com wrote: > > From: Stu Hsieh > > > > This patch create third crtc by third ddp path > > > > Apply this patch before

Re: [PATCH v3 8/8] drm/mediatek: add third ddp path

Hi, CK: I've some idea as below. On Fri, 2018-05-25 at 13:00 +0800, CK Hu wrote: > Hi, Stu: > > On Fri, 2018-05-25 at 10:34 +0800, stu.hs...@mediatek.com wrote: > > From: Stu Hsieh > > > > This patch create third crtc by third ddp path > > > > Apply this patch before the patch 'Add support

Re: [PATCH] powerpc-opal: fix spelling mistake "Uniterrupted" -> "Uninterrupted"

Colin King writes: > From: Colin Ian King > > Trivial fix to spelling mistake in hmi_error_types text > > Signed-off-by: Colin Ian King Reviewed-by: Stewart Smith -- Stewart Smith OPAL

Re: [PATCH] powerpc-opal: fix spelling mistake "Uniterrupted" -> "Uninterrupted"

Colin King writes: > From: Colin Ian King > > Trivial fix to spelling mistake in hmi_error_types text > > Signed-off-by: Colin Ian King Reviewed-by: Stewart Smith -- Stewart Smith OPAL Architect, IBM.

Re: [Nouveau] [PATCH][next] drm/nouveau/disp: avoid potential overflow on shift of int value

On Sun, May 27, 2018 at 5:54 PM, Colin King wrote: > From: Colin Ian King > > The constant values being shifted are 32 bit integers and may potentially > overflow on the shift. Avoid this potential overflow by making them > unsigned long long

Re: [Nouveau] [PATCH][next] drm/nouveau/disp: avoid potential overflow on shift of int value

On Sun, May 27, 2018 at 5:54 PM, Colin King wrote: > From: Colin Ian King > > The constant values being shifted are 32 bit integers and may potentially > overflow on the shift. Avoid this potential overflow by making them > unsigned long long values before the shift. > > Detected by

[PATCH v6 1/4] random: Fix whitespace pre random-bytes work

There are a couple of whitespace issues around the function get_random_bytes_arch(). In preparation for patching this function let's clean them up. Signed-off-by: Tobin C. Harding Acked-by: Theodore Ts'o --- drivers/char/random.c | 3 +-- 1 file changed, 1

[PATCH v6 3/4] vsprintf: Use hw RNG for ptr_key

Currently we must wait for enough entropy to become available before hashed pointers can be printed. We can remove this wait by using the hw RNG if available. Use hw RNG to get keying material. Cc: Steven Rostedt (VMware) Suggested-by: Kees Cook

[PATCH v6 4/4] vsprintf: Add command line option debug_boot_weak_hash

Currently printing [hashed] pointers requires enough entropy to be available. Early in the boot sequence this may not be the case resulting in a dummy string '(ptrval)' being printed. This makes debugging the early boot sequence difficult. We can relax the requirement to use

[PATCH v6 4/4] vsprintf: Add command line option debug_boot_weak_hash

Currently printing [hashed] pointers requires enough entropy to be available. Early in the boot sequence this may not be the case resulting in a dummy string '(ptrval)' being printed. This makes debugging the early boot sequence difficult. We can relax the requirement to use

[PATCH v6 1/4] random: Fix whitespace pre random-bytes work

There are a couple of whitespace issues around the function get_random_bytes_arch(). In preparation for patching this function let's clean them up. Signed-off-by: Tobin C. Harding Acked-by: Theodore Ts'o --- drivers/char/random.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff

[PATCH v6 3/4] vsprintf: Use hw RNG for ptr_key

Currently we must wait for enough entropy to become available before hashed pointers can be printed. We can remove this wait by using the hw RNG if available. Use hw RNG to get keying material. Cc: Steven Rostedt (VMware) Suggested-by: Kees Cook Signed-off-by: Tobin C. Harding ---

  1   2   3   4   >