[PATCH] ASoC: samsung: i2s: Supported high resolution rates

This driver can support more frequencies over 96KHz. There are no reasons to limit the frequency range below 96KHz. If codecs/amps or something else can't support high resolution rates, the constraints would be set rates properly because each drivers have its own limits. Signed-off-by: Jaechul

[PATCH] ASoC: samsung: i2s: Supported high resolution rates

This driver can support more frequencies over 96KHz. There are no reasons to limit the frequency range below 96KHz. If codecs/amps or something else can't support high resolution rates, the constraints would be set rates properly because each drivers have its own limits. Signed-off-by: Jaechul

Re: [PATCH 1/2] drivers: dma-coherent: Add support for default DMA coherent pool

Hi George, [auto build test ERROR on staging/staging-testing] [also build test ERROR on v4.12] [cannot apply to next-20170704] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/vitaly_kuzmichev

Re: [PATCH 1/2] drivers: dma-coherent: Add support for default DMA coherent pool

Hi George, [auto build test ERROR on staging/staging-testing] [also build test ERROR on v4.12] [cannot apply to next-20170704] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/vitaly_kuzmichev

[PATCH] mfd: Fix potential NULL pointer dereference

if 'max8998_i2c_parse_dt_pdata() fails (when out of memory), a NULL pointer dereference will occur in the error handling code. Return directly instead. Fixes: ee999fb3f17f("mfd: max8998: Add support for Device Tree") Signed-off-by: Christophe JAILLET ---

[PATCH] mfd: Fix potential NULL pointer dereference

if 'max8998_i2c_parse_dt_pdata() fails (when out of memory), a NULL pointer dereference will occur in the error handling code. Return directly instead. Fixes: ee999fb3f17f("mfd: max8998: Add support for Device Tree") Signed-off-by: Christophe JAILLET --- drivers/mfd/max8998.c | 6 ++ 1

[PATCH v3] ideapad-laptop: Add several models to no_hw_rfkill

From: Yang Jiaxun Some Lenovo ideapad models do not have hardware rfkill switches, but trying to read the rfkill switches through the ideapad-laptop module. It caused to always reported blocking breaking wifi. Fix it by adding those models to no_hw_rfkill_list. Signed-off-by:

[PATCH v3] ideapad-laptop: Add several models to no_hw_rfkill

From: Yang Jiaxun Some Lenovo ideapad models do not have hardware rfkill switches, but trying to read the rfkill switches through the ideapad-laptop module. It caused to always reported blocking breaking wifi. Fix it by adding those models to no_hw_rfkill_list. Signed-off-by: Yang Jiaxun ---

[PATCH] hwtracing: coresight: constify attribute_group structures.

attribute_groups are not supposed to change at runtime. All functions working with attribute_groups provided by work with const attribute_group. So mark the non-const structs as const. File size before: text data bss dec hex filename 2573 288 2963157 c55

[PATCH] hwtracing: coresight: constify attribute_group structures.

attribute_groups are not supposed to change at runtime. All functions working with attribute_groups provided by work with const attribute_group. So mark the non-const structs as const. File size before: text data bss dec hex filename 2573 288 2963157 c55

[QUESTION] perf annotate: how do we fix the 'total period' feature ?

Hi, Two problems of perf-annotate were mentioned in recent PATCH reviews by Milian and Namhyung. Currently perf-annotate has a '--show-total-period' option and a 't' key "Toggle total period view" on TUI browser. However, they actually show the number of samples, not period(Raw number of

[QUESTION] perf annotate: how do we fix the 'total period' feature ?

Hi, Two problems of perf-annotate were mentioned in recent PATCH reviews by Milian and Namhyung. Currently perf-annotate has a '--show-total-period' option and a 't' key "Toggle total period view" on TUI browser. However, they actually show the number of samples, not period(Raw number of

[PATCH] ideapad-laptop: Add several models to no_hw_rfkill

From 8db74a4eef334f614bf727232e5b88f67f824862 Mon Sep 17 00:00:00 2001 From: Yang Jiaxun Date: Tue, 4 Jul 2017 11:28:41 +0800 Subject: [PATCH] ideapad-laptop: Add several models to no_hw_rfkill Some Lenovo ideapad models do not have hardware rfkill switches, but trying to

[PATCH] ideapad-laptop: Add several models to no_hw_rfkill

From 8db74a4eef334f614bf727232e5b88f67f824862 Mon Sep 17 00:00:00 2001 From: Yang Jiaxun Date: Tue, 4 Jul 2017 11:28:41 +0800 Subject: [PATCH] ideapad-laptop: Add several models to no_hw_rfkill Some Lenovo ideapad models do not have hardware rfkill switches, but trying to read the rfkill

[PATCH v2] ideapad-laptop: Add several models to no_hw_rfkill

From daaa74f5b5f8ecfad4d452af787276f8c43f79b9 Mon Sep 17 00:00:00 2001 From: Yang Jiaxun Date: Tue, 4 Jul 2017 13:49:41 + Subject: [PATCH v2] ideapad-laptop: Add several models to no_hw_rfkill Some Lenovo ideapad models do not have hardware rfkill switches, but trying to

[PATCH v2] ideapad-laptop: Add several models to no_hw_rfkill

From daaa74f5b5f8ecfad4d452af787276f8c43f79b9 Mon Sep 17 00:00:00 2001 From: Yang Jiaxun Date: Tue, 4 Jul 2017 13:49:41 + Subject: [PATCH v2] ideapad-laptop: Add several models to no_hw_rfkill Some Lenovo ideapad models do not have hardware rfkill switches, but trying to read the rfkill

Re: [PATCH v3] [media] mtk-vcodec: Show mtk driver error without DEBUG definition

Fixing whitespace in the previous patch. On Wed, Jul 5, 2017 at 2:33 PM, Hirokazu Honda wrote: > A driver error message is shown without DEBUG definition > to find an error and debug easily. > > Signed-off-by: Hirokazu Honda > --- >

Re: [PATCH v3] [media] mtk-vcodec: Show mtk driver error without DEBUG definition

Fixing whitespace in the previous patch. On Wed, Jul 5, 2017 at 2:33 PM, Hirokazu Honda wrote: > A driver error message is shown without DEBUG definition > to find an error and debug easily. > > Signed-off-by: Hirokazu Honda > --- > drivers/media/platform/mtk-vcodec/mtk_vcodec_util.h | 20

[PATCH] hwmon: adt7475: constify attribute_group structures.

attribute_groups are not supposed to change at runtime. All functions working with attribute_groups provided by work with const attribute_group. So mark the non-const structs as const. File size before: textdata bss dec hex filename 100557032 0 1708742bf

[PATCH] hwmon: adt7475: constify attribute_group structures.

attribute_groups are not supposed to change at runtime. All functions working with attribute_groups provided by work with const attribute_group. So mark the non-const structs as const. File size before: textdata bss dec hex filename 100557032 0 1708742bf

[PATCH v3] [media] mtk-vcodec: Show mtk driver error without DEBUG definition

A driver error message is shown without DEBUG definition to find an error and debug easily. Signed-off-by: Hirokazu Honda --- drivers/media/platform/mtk-vcodec/mtk_vcodec_util.h | 20 +--- 1 file changed, 9 insertions(+), 11 deletions(-) diff --git

[PATCH v3] [media] mtk-vcodec: Show mtk driver error without DEBUG definition

A driver error message is shown without DEBUG definition to find an error and debug easily. Signed-off-by: Hirokazu Honda --- drivers/media/platform/mtk-vcodec/mtk_vcodec_util.h | 20 +--- 1 file changed, 9 insertions(+), 11 deletions(-) diff --git

linux-next: Tree for Jul 5

Hi all, Please do not add any v4.14 material to you linux-next included branches until after v4.13-rc1 has been released. Changes since 20170704: Non-merge commits (relative to Linus' tree): 7599 6571 files changed, 77 insertions(+), 131931 deletions

linux-next: Tree for Jul 5

Hi all, Please do not add any v4.14 material to you linux-next included branches until after v4.13-rc1 has been released. Changes since 20170704: Non-merge commits (relative to Linus' tree): 7599 6571 files changed, 77 insertions(+), 131931 deletions

Re: [PATCH 4.9 000/172] 4.9.36-stable review

On Tue, Jul 04, 2017 at 10:02:27PM +0530, Sumit Semwal wrote: > Hi Greg, > > On 3 July 2017 at 19:03, Greg Kroah-Hartman > wrote: > > This is the start of the stable review cycle for the 4.9.36 release. > > There are 172 patches in this series, all will be posted as

Re: [PATCH 4.9 000/172] 4.9.36-stable review

On Tue, Jul 04, 2017 at 10:02:27PM +0530, Sumit Semwal wrote: > Hi Greg, > > On 3 July 2017 at 19:03, Greg Kroah-Hartman > wrote: > > This is the start of the stable review cycle for the 4.9.36 release. > > There are 172 patches in this series, all will be posted as a response > > to this one.

[PATCH] hwmon: adc128d818: constify attribute_group structures.

attribute_groups are not supposed to change at runtime. All functions working with attribute_groups provided by work with const attribute_group. So mark the non-const structs as const. File size before: textdata bss dec hex filename 23042936 052401478

[PATCH] hwmon: adc128d818: constify attribute_group structures.

attribute_groups are not supposed to change at runtime. All functions working with attribute_groups provided by work with const attribute_group. So mark the non-const structs as const. File size before: textdata bss dec hex filename 23042936 052401478

Re: [PATCH v9 2/3] PCI: Add tango PCIe host bridge support

On Wed, Jul 05, 2017 at 01:59:55AM +0200, Mason wrote: > Do larger SoC vendors have HW devs working closely with > Linux devs, to avoid these design bloopers? Yes they generally do, as they have learned from their prior mistakes :) good luck! greg k-h

Re: [PATCH v9 2/3] PCI: Add tango PCIe host bridge support

On Wed, Jul 05, 2017 at 01:59:55AM +0200, Mason wrote: > Do larger SoC vendors have HW devs working closely with > Linux devs, to avoid these design bloopers? Yes they generally do, as they have learned from their prior mistakes :) good luck! greg k-h

[PATCH v2] hwmon: nct7802: constify attribute_group structures.

attribute_groups are not supposed to change at runtime. All functions working with attribute_groups provided by work with const attribute_group. So mark the non-const structs as const. File size before: textdata bss dec hex filename 61619400 0 155613cc9

[PATCH v2] hwmon: nct7802: constify attribute_group structures.

attribute_groups are not supposed to change at runtime. All functions working with attribute_groups provided by work with const attribute_group. So mark the non-const structs as const. File size before: textdata bss dec hex filename 61619400 0 155613cc9

[PATCH] hwmon: nct7802: constify attribute_group structures.

attribute_groups are not supposed to change at runtime. All functions working with attribute_groups provided by work with const attribute_group. So mark the non-const structs as const. File size before: textdata bss dec hex filename 6655 304 069591b2f

[PATCH] hwmon: nct7802: constify attribute_group structures.

attribute_groups are not supposed to change at runtime. All functions working with attribute_groups provided by work with const attribute_group. So mark the non-const structs as const. File size before: textdata bss dec hex filename 6655 304 069591b2f

Re: [PATCH] thermal: imx: interpret fsl,tempmon-data through nvmem

On 19/06/17 14:40, Leonard Crestez wrote: On imx6sx accessing the ocotp memory area directly is wrong because the ocotp clock needs to be enabled first. Fix this by reinterpreting the fsl,tempmon-data phandle as a reference to a nvmem_device and doing all the read through that. This looks

Re: [PATCH] thermal: imx: interpret fsl,tempmon-data through nvmem

On 19/06/17 14:40, Leonard Crestez wrote: On imx6sx accessing the ocotp memory area directly is wrong because the ocotp clock needs to be enabled first. Fix this by reinterpreting the fsl,tempmon-data phandle as a reference to a nvmem_device and doing all the read through that. This looks

[GIT PULL] gcc-plugins updates for v4.13-rc1

Hi, Please pull these gcc-plugins changes for v4.13-rc1. The big part is the randstruct plugin infrastructure. This is the first of two expected pull requests for randstruct since there are dependencies in other trees that would be easier to merge once those have landed. Notably, the IPC

[GIT PULL] gcc-plugins updates for v4.13-rc1

Hi, Please pull these gcc-plugins changes for v4.13-rc1. The big part is the randstruct plugin infrastructure. This is the first of two expected pull requests for randstruct since there are dependencies in other trees that would be easier to merge once those have landed. Notably, the IPC

Re: [RFC][PATCHv3 2/5] printk: introduce printing kernel thread

Hello, Petr, thanks for commenting/taking a look On (07/04/17 16:03), Petr Mladek wrote: > On Fri 2017-06-30 21:42:24, Sergey Senozhatsky wrote: > > Hello, > > > > On (06/30/17 13:54), Petr Mladek wrote: > > > > but. > > > > the opposite possibility is that messages either won't be printed

Re: [RFC][PATCHv3 2/5] printk: introduce printing kernel thread

Hello, Petr, thanks for commenting/taking a look On (07/04/17 16:03), Petr Mladek wrote: > On Fri 2017-06-30 21:42:24, Sergey Senozhatsky wrote: > > Hello, > > > > On (06/30/17 13:54), Petr Mladek wrote: > > > > but. > > > > the opposite possibility is that messages either won't be printed

[PATCH] hwmon: constify attribute_group structures.

attribute_groups are not supposed to change at runtime. All functions working with attribute_groups provided by work with const attribute_group. So mark the non-const structs as const. File size before: textdata bss dec hex filename 6655 304 069591b2f

[PATCH] hwmon: constify attribute_group structures.

attribute_groups are not supposed to change at runtime. All functions working with attribute_groups provided by work with const attribute_group. So mark the non-const structs as const. File size before: textdata bss dec hex filename 6655 304 069591b2f

Re: [PATCH v2 1/6] cpufreq: schedutil: ignore sugov kthreads

On 04-07-17, 18:34, Patrick Bellasi wrote: > In system where multiple CPUs shares the same frequency domain a small > workload on a CPU can still be subject to frequency spikes, generated by > the activation of the sugov's kthread. > > Since the sugov kthread is a special RT task, which goal is

Re: [PATCH v2 1/6] cpufreq: schedutil: ignore sugov kthreads

On 04-07-17, 18:34, Patrick Bellasi wrote: > In system where multiple CPUs shares the same frequency domain a small > workload on a CPU can still be subject to frequency spikes, generated by > the activation of the sugov's kthread. > > Since the sugov kthread is a special RT task, which goal is

Re: [PATCH v2 2/6] cpufreq: schedutil: reset sg_cpus's flags at IDLE enter

On 04-07-17, 18:34, Patrick Bellasi wrote: > diff --git a/include/linux/sched/cpufreq.h b/include/linux/sched/cpufreq.h > index d2be2cc..36ac8d2 100644 > --- a/include/linux/sched/cpufreq.h > +++ b/include/linux/sched/cpufreq.h > @@ -10,6 +10,7 @@ > #define SCHED_CPUFREQ_RT (1U << 0) >

Re: [PATCH v2 2/6] cpufreq: schedutil: reset sg_cpus's flags at IDLE enter

On 04-07-17, 18:34, Patrick Bellasi wrote: > diff --git a/include/linux/sched/cpufreq.h b/include/linux/sched/cpufreq.h > index d2be2cc..36ac8d2 100644 > --- a/include/linux/sched/cpufreq.h > +++ b/include/linux/sched/cpufreq.h > @@ -10,6 +10,7 @@ > #define SCHED_CPUFREQ_RT (1U << 0) >

Re: [PATCH] powerpc/mm: fix a hardcode on memory boundary checking

On 01/12/2017 02:39 PM, Rui Teng wrote: > The offset of hugepage block will not be 16G, if the expected > page is more than one. Calculate the totol size instead of the > hardcode value. > > Signed-off-by: Rui Teng I have a redundant patch, this one is the original.

Re: [PATCH] powerpc/mm: fix a hardcode on memory boundary checking

On 01/12/2017 02:39 PM, Rui Teng wrote: > The offset of hugepage block will not be 16G, if the expected > page is more than one. Calculate the totol size instead of the > hardcode value. > > Signed-off-by: Rui Teng I have a redundant patch, this one is the original. Tested-by: Anshuman

Re: [PATCH] powerpc/mm: Implemented default_hugepagesz verification for powerpc

On 07/04/2017 01:35 AM, Victor Aoqui wrote: > Implemented default hugepage size verification (default_hugepagesz=) > in order to allow allocation of defined number of pages (hugepages=) > only for supported hugepage sizes. > > Signed-off-by: Victor Aoqui > --- >

Re: [PATCH] powerpc/mm: Implemented default_hugepagesz verification for powerpc

On 07/04/2017 01:35 AM, Victor Aoqui wrote: > Implemented default hugepage size verification (default_hugepagesz=) > in order to allow allocation of defined number of pages (hugepages=) > only for supported hugepage sizes. > > Signed-off-by: Victor Aoqui > --- > arch/powerpc/mm/hugetlbpage.c |

[GIT PULL] pstore updates for v4.13-rc1

Hi, Please pull these pstore changes for v4.13-rc1. Thanks! -Kees The following changes since commit 5ed02dbb497422bf225783f46e6eadd237d23d6b: Linux 4.12-rc3 (2017-05-28 17:20:53 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git

[GIT PULL] pstore updates for v4.13-rc1

Hi, Please pull these pstore changes for v4.13-rc1. Thanks! -Kees The following changes since commit 5ed02dbb497422bf225783f46e6eadd237d23d6b: Linux 4.12-rc3 (2017-05-28 17:20:53 -0700) are available in the git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/kees/linux.git

Re: [PATCH] powerpc/mm: Implemented default_hugepagesz verification for powerpc

On Tuesday 04 July 2017 01:35 AM, Victor Aoqui wrote: Implemented default hugepage size verification (default_hugepagesz=) in order to allow allocation of defined number of pages (hugepages=) only for supported hugepage sizes. Signed-off-by: Victor Aoqui ---

Re: [PATCH] powerpc/mm: Implemented default_hugepagesz verification for powerpc

On Tuesday 04 July 2017 01:35 AM, Victor Aoqui wrote: Implemented default hugepage size verification (default_hugepagesz=) in order to allow allocation of defined number of pages (hugepages=) only for supported hugepage sizes. Signed-off-by: Victor Aoqui --- arch/powerpc/mm/hugetlbpage.c |

Re: [PATCH v2 3/3] dt-bindings: cpufreq: enhance MediaTek cpufreq dt-binding document

On 05-07-17, 02:55, sean.w...@mediatek.com wrote: > From: Sean Wang > > Update binding document with adding operating-points-v2 as the required > property and the cooling level as the optional properties and adding more > examples guiding people how to use MediaTek

Re: [PATCH v2 0/3] some fixups for MediaTek cpufreq driver

On 05-07-17, 02:55, sean.w...@mediatek.com wrote: > From: Sean Wang > > Changes since v1: > - drop those patches already accepted > - refine the commit messages and Kconfig dependency > - Kconfig menu entry and file name itself are updated with more > generic name to drop

Re: [PATCH v2 3/3] dt-bindings: cpufreq: enhance MediaTek cpufreq dt-binding document

On 05-07-17, 02:55, sean.w...@mediatek.com wrote: > From: Sean Wang > > Update binding document with adding operating-points-v2 as the required > property and the cooling level as the optional properties and adding more > examples guiding people how to use MediaTek cpufreq driver for MediaTek >

Re: [PATCH v2 0/3] some fixups for MediaTek cpufreq driver

On 05-07-17, 02:55, sean.w...@mediatek.com wrote: > From: Sean Wang > > Changes since v1: > - drop those patches already accepted > - refine the commit messages and Kconfig dependency > - Kconfig menu entry and file name itself are updated with more > generic name to drop "MT8173" since this

[PATCH] Revert "f2fs: fix to clean previous mount option when remount_fs"

From: Chao Yu Don't clear old mount option before parse new option during ->remount_fs like other generic filesystems. This reverts commit 2c8a4366debae30ae37d0688b2bec92d196a. Signed-off-by: Chao Yu --- fs/f2fs/super.c | 1 - 1 file changed, 1

[PATCH] Revert "f2fs: fix to clean previous mount option when remount_fs"

From: Chao Yu Don't clear old mount option before parse new option during ->remount_fs like other generic filesystems. This reverts commit 2c8a4366debae30ae37d0688b2bec92d196a. Signed-off-by: Chao Yu --- fs/f2fs/super.c | 1 - 1 file changed, 1 deletion(-) diff --git a/fs/f2fs/super.c

Re: [PATCH v5 3/6] dt-bindings: List devicetree binding for the CCU of Allwinner A20

On Wed, Jul 5, 2017 at 4:04 AM, Priit Laes wrote: > Allwinner A20 is now driven by sunxi-ng CCU driver. > > Add devicetree binding for it. > > Acked-by: Rob Herring > Signed-off-by: Priit Laes Reviewed-by: Chen-Yu Tsai

Re: [PATCH v5 3/6] dt-bindings: List devicetree binding for the CCU of Allwinner A20

On Wed, Jul 5, 2017 at 4:04 AM, Priit Laes wrote: > Allwinner A20 is now driven by sunxi-ng CCU driver. > > Add devicetree binding for it. > > Acked-by: Rob Herring > Signed-off-by: Priit Laes Reviewed-by: Chen-Yu Tsai

Re: [PATCH v5 4/6] dt-bindings: List devicetree binding for the CCU of Allwinner A10

On Wed, Jul 5, 2017 at 4:04 AM, Priit Laes wrote: > Allwinner A10 is now driven by sunxi-ng CCU driver. > > Add devicetree binding for it. > > Acked-by: Rob Herring > Signed-off-by: Priit Laes Reviewed-by: Chen-Yu Tsai

Re: [PATCH v5 1/6] clk: sunxi-ng: div: Add support for fixed post-divider

On Wed, Jul 5, 2017 at 4:04 AM, Priit Laes wrote: > SATA clock on sun4i/sun7i is of type (parent) / M / 6 where > 6 is fixed post-divider. > > Signed-off-by: Priit Laes Reviewed-by: Chen-Yu Tsai

Re: [PATCH v5 4/6] dt-bindings: List devicetree binding for the CCU of Allwinner A10

On Wed, Jul 5, 2017 at 4:04 AM, Priit Laes wrote: > Allwinner A10 is now driven by sunxi-ng CCU driver. > > Add devicetree binding for it. > > Acked-by: Rob Herring > Signed-off-by: Priit Laes Reviewed-by: Chen-Yu Tsai

Re: [PATCH v5 1/6] clk: sunxi-ng: div: Add support for fixed post-divider

On Wed, Jul 5, 2017 at 4:04 AM, Priit Laes wrote: > SATA clock on sun4i/sun7i is of type (parent) / M / 6 where > 6 is fixed post-divider. > > Signed-off-by: Priit Laes Reviewed-by: Chen-Yu Tsai

Re: [PATCH 2/2] f2fs: reuse original mount option in ->remount_fs

On 2017/7/1 15:48, Jaegeuk Kim wrote: > On 06/29, Chao Yu wrote: >> From: Chao Yu >> >> Don't clear old mount option before parse new option during ->remount_fs >> like other generic filesystems. > > So, what happened on your original patch? > > commit

Re: [PATCH 2/2] f2fs: reuse original mount option in ->remount_fs

On 2017/7/1 15:48, Jaegeuk Kim wrote: > On 06/29, Chao Yu wrote: >> From: Chao Yu >> >> Don't clear old mount option before parse new option during ->remount_fs >> like other generic filesystems. > > So, what happened on your original patch? > > commit 2c8a4366debae30ae37d0688b2bec92d196a >

[PATCH] cpufreq: speedstep: remove unnecessary static in speedstep_detect_chipset()

Remove unnecessary static on local variable hostbridge. Such variable is initialized before being used, on every execution path throughout the function. The static has no benefit and, removing it reduces the code size. This issue was detected using Coccinelle and the following semantic patch:

[PATCH] cpufreq: speedstep: remove unnecessary static in speedstep_detect_chipset()

Remove unnecessary static on local variable hostbridge. Such variable is initialized before being used, on every execution path throughout the function. The static has no benefit and, removing it reduces the code size. This issue was detected using Coccinelle and the following semantic patch:

Re: [PATCH] cpufreq: speedstep: remove unnecessary static in speedstep_detect_chipset()

+ Dominic, On 04-07-17, 22:09, Gustavo A. R. Silva wrote: > Remove unnecessary static on local variable hostbridge. > Such variable is initialized before being used, > on every execution path throughout the function. > The static has no benefit and, removing it reduces > the code size. > > This

Re: [PATCH] cpufreq: speedstep: remove unnecessary static in speedstep_detect_chipset()

+ Dominic, On 04-07-17, 22:09, Gustavo A. R. Silva wrote: > Remove unnecessary static on local variable hostbridge. > Such variable is initialized before being used, > on every execution path throughout the function. > The static has no benefit and, removing it reduces > the code size. > > This

Re: [PATCH v4 2/2] PCI: iproc: add device shutdown for PCI RC

Hi Oza, It looks like you missed my comments during the internal review. See my comments inline below. On 7/4/2017 8:08 PM, Oza Pawandeep wrote: PERST must be asserted around ~500ms before the reboot is applied. During soft reset (e.g., "reboot" from Linux) on some iproc based SOCs LCPLL

Re: [PATCH v4 2/2] PCI: iproc: add device shutdown for PCI RC

Hi Oza, It looks like you missed my comments during the internal review. See my comments inline below. On 7/4/2017 8:08 PM, Oza Pawandeep wrote: PERST must be asserted around ~500ms before the reboot is applied. During soft reset (e.g., "reboot" from Linux) on some iproc based SOCs LCPLL

[PATCH v3] perf sort: only insert overhead && overhead_children when no overhead* field given

From: Changbin Du If we always insert 'overhead' and 'overhead_children' as sort keys, this make it impossible to sort as overhead (which displayed as Self) first.Ths will be a problem if the data is collected with call-graph enabled. Then we never can sort the result as

[PATCH v3] perf sort: only insert overhead && overhead_children when no overhead* field given

From: Changbin Du If we always insert 'overhead' and 'overhead_children' as sort keys, this make it impossible to sort as overhead (which displayed as Self) first.Ths will be a problem if the data is collected with call-graph enabled. Then we never can sort the result as self-overhead on this

[PATCH v2] btrfs: Correct assignment of pos

From: Goldwyn Rodrigues Assigning pos for usage early messes up in append mode, where the pos is re-assigned in generic_write_checks(). Assign pos later to get the correct position to write from iocb->ki_pos. Since check_can_nocow also uses the value of pos, we shift

[PATCH v2] btrfs: Correct assignment of pos

From: Goldwyn Rodrigues Assigning pos for usage early messes up in append mode, where the pos is re-assigned in generic_write_checks(). Assign pos later to get the correct position to write from iocb->ki_pos. Since check_can_nocow also uses the value of pos, we shift generic_write_checks()

Re: [f2fs-dev] [PATCH 1/2] f2fs: avoid deadlock caused by lock order of page and lock_op

On 07/05, Chao Yu wrote: > On 2017/7/1 22:27, Jaegeuk Kim wrote: > > On 07/01, Chao Yu wrote: > >> On 2017/7/1 15:28, Jaegeuk Kim wrote: > >>> On 06/26, Chao Yu wrote: > Hi Jaegeuk, > > On 2017/6/26 22:54, Jaegeuk Kim wrote: > > Hi Chao, > > > > On 06/26, Chao Yu wrote:

Re: [f2fs-dev] [PATCH 1/2] f2fs: avoid deadlock caused by lock order of page and lock_op

On 07/05, Chao Yu wrote: > On 2017/7/1 22:27, Jaegeuk Kim wrote: > > On 07/01, Chao Yu wrote: > >> On 2017/7/1 15:28, Jaegeuk Kim wrote: > >>> On 06/26, Chao Yu wrote: > Hi Jaegeuk, > > On 2017/6/26 22:54, Jaegeuk Kim wrote: > > Hi Chao, > > > > On 06/26, Chao Yu wrote:

Re: [PATCH][RFC] x86: Fix the irq affinity in fixup_cpus

On Tue, Jul 04, 2017 at 10:50:33AM +0200, Thomas Gleixner wrote: > On Mon, 3 Jul 2017, Chen Yu wrote: > > On Sun, Jun 04, 2017 at 10:04:53PM +0200, Thomas Gleixner wrote: > > > After looking at the callsites, it's safe to change > > > irq_set_affinity_locked() so that it uses the direct affinity

Re: [PATCH][RFC] x86: Fix the irq affinity in fixup_cpus

On Tue, Jul 04, 2017 at 10:50:33AM +0200, Thomas Gleixner wrote: > On Mon, 3 Jul 2017, Chen Yu wrote: > > On Sun, Jun 04, 2017 at 10:04:53PM +0200, Thomas Gleixner wrote: > > > After looking at the callsites, it's safe to change > > > irq_set_affinity_locked() so that it uses the direct affinity

Re: [PATCH 4/5] mm/memcontrol: allow to uncharge page without using page->lru field

On Tue, Jul 4, 2017 at 10:51 PM, Michal Hocko wrote: > On Mon 03-07-17 17:14:14, Jérôme Glisse wrote: >> HMM pages (private or public device pages) are ZONE_DEVICE page and >> thus you can not use page->lru fields of those pages. This patch >> re-arrange the uncharge to allow

Re: [PATCH 4/5] mm/memcontrol: allow to uncharge page without using page->lru field

On Tue, Jul 4, 2017 at 10:51 PM, Michal Hocko wrote: > On Mon 03-07-17 17:14:14, Jérôme Glisse wrote: >> HMM pages (private or public device pages) are ZONE_DEVICE page and >> thus you can not use page->lru fields of those pages. This patch >> re-arrange the uncharge to allow single page to be

Re: [PATCH] arm64: traps: disable irq in die()

On 2017年07月05日 01:17, Will Deacon wrote: On Wed, Jun 28, 2017 at 05:04:12PM +0800, Qiao Zhou wrote: In current die(), the irq is disabled for __die() handle, not including the possible panic() handling. Since the log in __die() can take several hundreds ms, new irq might come and interrupt

Re: [PATCH] arm64: traps: disable irq in die()

On 2017年07月05日 01:17, Will Deacon wrote: On Wed, Jun 28, 2017 at 05:04:12PM +0800, Qiao Zhou wrote: In current die(), the irq is disabled for __die() handle, not including the possible panic() handling. Since the log in __die() can take several hundreds ms, new irq might come and interrupt

RE: [PATCH] arm64: dts: ls1046a: Add dis_rxdet_inp3_quirk property to USB3 node

Hello Sir, How is the review result of this patch. I am waiting for it be merged, thanks. BR Ran -Original Message- From: Ran Wang [mailto:ran.wan...@nxp.com] Sent: Friday, June 02, 2017 10:30 AM To: Rob Herring ; Mark Rutland ; Catalin

RE: [PATCH] arm64: dts: ls1046a: Add dis_rxdet_inp3_quirk property to USB3 node

Hello Sir, How is the review result of this patch. I am waiting for it be merged, thanks. BR Ran -Original Message- From: Ran Wang [mailto:ran.wan...@nxp.com] Sent: Friday, June 02, 2017 10:30 AM To: Rob Herring ; Mark Rutland ; Catalin Marinas ; Will Deacon Cc: Shawn Guo ; Andy

[PATCH] soc: versatile: remove unnecessary static in realview_soc_probe()

Remove unnecessary static on local variable syscon_regmap. Such variable is initialized before being used, on every execution path throughout the function. The static has no benefit and, removing it reduces the code size. This issue was detected using Coccinelle and the following semantic patch:

[PATCH] soc: versatile: remove unnecessary static in realview_soc_probe()

Remove unnecessary static on local variable syscon_regmap. Such variable is initialized before being used, on every execution path throughout the function. The static has no benefit and, removing it reduces the code size. This issue was detected using Coccinelle and the following semantic patch:

[PATCH] arm64: dts: ls1012a: add USB host controller nodes

LS1012A has one USB 3.0(DWC3) controller and one USB 2.0 controller. Signed-off-by: Ran Wang --- arch/arm64/boot/dts/freescale/fsl-ls1012a.dtsi | 17 + 1 file changed, 17 insertions(+) diff --git a/arch/arm64/boot/dts/freescale/fsl-ls1012a.dtsi

[PATCH] arm64: dts: ls1012a: add USB host controller nodes

LS1012A has one USB 3.0(DWC3) controller and one USB 2.0 controller. Signed-off-by: Ran Wang --- arch/arm64/boot/dts/freescale/fsl-ls1012a.dtsi | 17 + 1 file changed, 17 insertions(+) diff --git a/arch/arm64/boot/dts/freescale/fsl-ls1012a.dtsi

[PATCH v4 1/2] PCI: iproc: Retry request when CRS returned from EP

For Configuration Requests only, following reset it is possible for a device to terminate the request but indicate that it is temporarily unable to process the Request, but will be able to process the Request in the future – in this case, the Configuration Request Retry Status 100 (CRS) Completion

[PATCH v4 2/2] PCI: iproc: add device shutdown for PCI RC

PERST must be asserted around ~500ms before the reboot is applied. During soft reset (e.g., "reboot" from Linux) on some iproc based SOCs LCPLL clock and PERST both goes off simultaneously. This will cause certain Endpoints Intel NVMe not get detected, upon next boot sequence. This is

[PATCH v4 1/2] PCI: iproc: Retry request when CRS returned from EP

For Configuration Requests only, following reset it is possible for a device to terminate the request but indicate that it is temporarily unable to process the Request, but will be able to process the Request in the future – in this case, the Configuration Request Retry Status 100 (CRS) Completion

[PATCH v4 2/2] PCI: iproc: add device shutdown for PCI RC

PERST must be asserted around ~500ms before the reboot is applied. During soft reset (e.g., "reboot" from Linux) on some iproc based SOCs LCPLL clock and PERST both goes off simultaneously. This will cause certain Endpoints Intel NVMe not get detected, upon next boot sequence. This is

[PATCH v4 0/2] PCI: iproc: SOC specific fixes

PCI: iproc: Retry request when CRS returned from EP Above patch adds support for CRS in PCI RC driver, otherwise if not handled at lower level, the user space PMD (poll mode drivers) can timeout. PCI: iproc: add device shutdown for PCI RC This fixes the issue where certian PCI endpoints are not

[PATCH v4 0/2] PCI: iproc: SOC specific fixes

PCI: iproc: Retry request when CRS returned from EP Above patch adds support for CRS in PCI RC driver, otherwise if not handled at lower level, the user space PMD (poll mode drivers) can timeout. PCI: iproc: add device shutdown for PCI RC This fixes the issue where certian PCI endpoints are not

Re: [PATCH v2] perf sort: only insert overhead && overhead_children when no overhead* field given

On Thu, Jun 29, 2017 at 05:22:52PM +0200, Jiri Olsa wrote: > > > --- a/tools/perf/util/sort.c > > > +++ b/tools/perf/util/sort.c > > > @@ -2635,6 +2635,9 @@ static char *setup_overhead(char *keys) > > > if (sort__mode == SORT_MODE__DIFF) > > > return keys; > > > > > > + if

Re: [PATCH v2] perf sort: only insert overhead && overhead_children when no overhead* field given

On Thu, Jun 29, 2017 at 05:22:52PM +0200, Jiri Olsa wrote: > > > --- a/tools/perf/util/sort.c > > > +++ b/tools/perf/util/sort.c > > > @@ -2635,6 +2635,9 @@ static char *setup_overhead(char *keys) > > > if (sort__mode == SORT_MODE__DIFF) > > > return keys; > > > > > > + if

  1   2   3   4   5   6   7   8   9   10   >