[PATCH v2 10/11] iommu/ipmmu-vmsa: Allow two bit SL0

From: Magnus Damm Introduce support for two bit SL0 bitfield in IMTTBCR by using a separate feature flag. Signed-off-by: Magnus Damm --- Changes since V1: - None drivers/iommu/ipmmu-vmsa.c | 15 ++- 1 file changed, 14

[PATCH v2 11/11] iommu/ipmmu-vmsa: Hook up r8a7795 DT matching code

From: Magnus Damm Tie in r8a7795 features and update the IOMMU_OF_DECLARE compat string to hook up the updated compat string. TODO: - Go over init order once more - Consider counting number of IPMMU devices from ->xlate() - Experiment with delaying call to

[PATCH v2 10/11] iommu/ipmmu-vmsa: Allow two bit SL0

From: Magnus Damm Introduce support for two bit SL0 bitfield in IMTTBCR by using a separate feature flag. Signed-off-by: Magnus Damm --- Changes since V1: - None drivers/iommu/ipmmu-vmsa.c | 15 ++- 1 file changed, 14 insertions(+), 1 deletion(-) ---

[PATCH v2 11/11] iommu/ipmmu-vmsa: Hook up r8a7795 DT matching code

From: Magnus Damm Tie in r8a7795 features and update the IOMMU_OF_DECLARE compat string to hook up the updated compat string. TODO: - Go over init order once more - Consider counting number of IPMMU devices from ->xlate() - Experiment with delaying call to bus_set_iommu() Signed-off-by:

[PATCH v2 02/11] iommu/ipmmu-vmsa: Add optional root device feature

From: Magnus Damm Add root device handling to the IPMMU driver by allowing certain DT compat strings to enable has_cache_leaf_nodes that in turn will support both root devices with interrupts and leaf devices that face the actual IPMMU consumer devices.

[PATCH v2 06/11] iommu/ipmmu-vmsa: Teach xlate() to skip disabled iommus

From: Magnus Damm The ->xlate() call gets invoked even though the iommu device has status = "disabled" in DT, so make sure we skip over disabled devices. In my mind it would make sense to have this at some shared level, but I guess some users may want to configure

[PATCH v2 03/11] iommu/ipmmu-vmsa: Enable multi context support

From: Magnus Damm Add support for up to 8 contexts. Each context is mapped to one domain. One domain is associated with each device, however one or more uTLBs for a single device are kept in the same domain. Signed-off-by: Magnus Damm ---

[PATCH v2 02/11] iommu/ipmmu-vmsa: Add optional root device feature

From: Magnus Damm Add root device handling to the IPMMU driver by allowing certain DT compat strings to enable has_cache_leaf_nodes that in turn will support both root devices with interrupts and leaf devices that face the actual IPMMU consumer devices. Signed-off-by: Magnus Damm --- Changes

[PATCH v2 03/11] iommu/ipmmu-vmsa: Enable multi context support

From: Magnus Damm Add support for up to 8 contexts. Each context is mapped to one domain. One domain is associated with each device, however one or more uTLBs for a single device are kept in the same domain. Signed-off-by: Magnus Damm --- Changes since V1: - Support up to 8 contexts instead

[PATCH v2 06/11] iommu/ipmmu-vmsa: Teach xlate() to skip disabled iommus

From: Magnus Damm The ->xlate() call gets invoked even though the iommu device has status = "disabled" in DT, so make sure we skip over disabled devices. In my mind it would make sense to have this at some shared level, but I guess some users may want to configure the iommu regardless of DT

[PATCH v2 05/11] iommu/ipmmu-vmsa: Make use of IOMMU_OF_DECLARE()

From: Magnus Damm Hook up IOMMU_OF_DECLARE() support in case CONFIG_IOMMU_DMA is enabled. The only current supported case for 32-bit ARM is disabled, however for 64-bit ARM this is required. Signed-off-by: Magnus Damm --- Changes since

[PATCH v2 05/11] iommu/ipmmu-vmsa: Make use of IOMMU_OF_DECLARE()

From: Magnus Damm Hook up IOMMU_OF_DECLARE() support in case CONFIG_IOMMU_DMA is enabled. The only current supported case for 32-bit ARM is disabled, however for 64-bit ARM this is required. Signed-off-by: Magnus Damm --- Changes since V1: - Reworked slightly to fit updated patch order and

[PATCH v2 04/11] iommu/ipmmu-vmsa: Reuse iommu groups

From: Magnus Damm Extend the IPMMU driver to group devices together based on the IPMMU device they are connected to. The slave devices are kept on a list which is used to determine if existing groups (and contexts) exist. With this patch the two SYS-DMAC devices

[PATCH v2 09/11] iommu/ipmmu-vmsa: Make IMBUSCTR setup optional

From: Magnus Damm Introduce a feature to allow opt-out of setting up IMBUSCR. The default case is unchanged. Signed-off-by: Magnus Damm --- Changes since V1: - Updated the commit message - Reworked patch to coexist with the multi

[PATCH v2 04/11] iommu/ipmmu-vmsa: Reuse iommu groups

From: Magnus Damm Extend the IPMMU driver to group devices together based on the IPMMU device they are connected to. The slave devices are kept on a list which is used to determine if existing groups (and contexts) exist. With this patch the two SYS-DMAC devices using IPMMU-DS0 on r8a7795 will

[PATCH v2 09/11] iommu/ipmmu-vmsa: Make IMBUSCTR setup optional

From: Magnus Damm Introduce a feature to allow opt-out of setting up IMBUSCR. The default case is unchanged. Signed-off-by: Magnus Damm --- Changes since V1: - Updated the commit message - Reworked patch to coexist with the multi context feature drivers/iommu/ipmmu-vmsa.c | 10

[PATCH v2 00/11] iommu/ipmmu-vmsa: r8a7795 support V2

iommu/ipmmu-vmsa: r8a7795 support V2 [PATCH v2 01/11] iommu/ipmmu-vmsa: Introduce features, break out alias [PATCH v2 02/11] iommu/ipmmu-vmsa: Add optional root device feature [PATCH v2 03/11] iommu/ipmmu-vmsa: Enable multi context support [PATCH v2 04/11] iommu/ipmmu-vmsa: Reuse iommu groups

[PATCH v2 00/11] iommu/ipmmu-vmsa: r8a7795 support V2

iommu/ipmmu-vmsa: r8a7795 support V2 [PATCH v2 01/11] iommu/ipmmu-vmsa: Introduce features, break out alias [PATCH v2 02/11] iommu/ipmmu-vmsa: Add optional root device feature [PATCH v2 03/11] iommu/ipmmu-vmsa: Enable multi context support [PATCH v2 04/11] iommu/ipmmu-vmsa: Reuse iommu groups

[PATCH v2 01/11] iommu/ipmmu-vmsa: Introduce features, break out alias

From: Magnus Damm Introduce struct ipmmu_features to track various hardware and software implementation changes inside the driver for different kinds of IPMMU hardware. Add use_ns_alias_offset as a first example of a feature to control if the secure register bank

[PATCH v2 01/11] iommu/ipmmu-vmsa: Introduce features, break out alias

From: Magnus Damm Introduce struct ipmmu_features to track various hardware and software implementation changes inside the driver for different kinds of IPMMU hardware. Add use_ns_alias_offset as a first example of a feature to control if the secure register bank offset should be used or not.

linux-next: build failure after merge of the akpm-current tree

Hi Andrew, After merging the akpm-current tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: include/linux/kexec.h: In function 'boot_phys_to_virt': include/linux/kexec.h:358:9: error: implicit declaration of function 'phys_to_virt'

linux-next: build failure after merge of the akpm-current tree

Hi Andrew, After merging the akpm-current tree, today's linux-next build (powerpc ppc64_defconfig) failed like this: include/linux/kexec.h: In function 'boot_phys_to_virt': include/linux/kexec.h:358:9: error: implicit declaration of function 'phys_to_virt'

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

Hi Kevin, On Sun, 5 Jun 2016 20:40:28 -0700 Kevin Hilman wrote: > > Not forgotten, but merged through Philip's reset tree, which I thought > was already in linux-next. Sorry about that. It may well be, but we dislike implicit dependencies between trees ... it makes the

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

Hi Kevin, On Sun, 5 Jun 2016 20:40:28 -0700 Kevin Hilman wrote: > > Not forgotten, but merged through Philip's reset tree, which I thought > was already in linux-next. Sorry about that. It may well be, but we dislike implicit dependencies between trees ... it makes the merge order matter :-(

Re: [PATCH V3 6/9] cpufreq: imx: Use 'index' only to index into policy->freq_table

On 03-06-16, 19:05, Viresh Kumar wrote: > Later patches would make changes in cpufreq core, after which > policy->freq_table may be reordered by cpufreq core and it wouldn't be > safe anymore to use 'index' for any other local arrays. > > To prepare for that, use

Re: [PATCH V3 6/9] cpufreq: imx: Use 'index' only to index into policy->freq_table

On 03-06-16, 19:05, Viresh Kumar wrote: > Later patches would make changes in cpufreq core, after which > policy->freq_table may be reordered by cpufreq core and it wouldn't be > safe anymore to use 'index' for any other local arrays. > > To prepare for that, use

Re: [PATCH V3 8/9] cpufreq: Keep policy->freq_table sorted in ascending order

On 03-06-16, 16:48, Steve Muckle wrote: > On Fri, Jun 03, 2016 at 07:05:14PM +0530, Viresh Kumar wrote: > ... > > @@ -468,20 +469,15 @@ unsigned int acpi_cpufreq_fast_switch(struct > > cpufreq_policy *policy, > > struct acpi_cpufreq_data *data = policy->driver_data; > > struct

Re: [PATCH V3 8/9] cpufreq: Keep policy->freq_table sorted in ascending order

On 03-06-16, 16:48, Steve Muckle wrote: > On Fri, Jun 03, 2016 at 07:05:14PM +0530, Viresh Kumar wrote: > ... > > @@ -468,20 +469,15 @@ unsigned int acpi_cpufreq_fast_switch(struct > > cpufreq_policy *policy, > > struct acpi_cpufreq_data *data = policy->driver_data; > > struct

Re: [RFC PATCH v1 4/6] PM / devfreq: event: support rockchip dfi controller

On 2016年06月03日 18:26, Chanwoo Choi wrote: Hi Lin, I add the some comment on below. If you modify it, You can add my acked-by tag. Looks good to me. Thanks for you reviewing, i will update the code folloiwing your comment. Acked-by: Chanwoo Choi Also, I'd like you to

Re: [RFC PATCH v1 4/6] PM / devfreq: event: support rockchip dfi controller

On 2016年06月03日 18:26, Chanwoo Choi wrote: Hi Lin, I add the some comment on below. If you modify it, You can add my acked-by tag. Looks good to me. Thanks for you reviewing, i will update the code folloiwing your comment. Acked-by: Chanwoo Choi Also, I'd like you to add me to mail thread

[PATCH V4 1/8] ARM: davinci: Sort frequency table

This is required for some of the changes in cpufreq core. There was only one function dependent on the order of the table, that is fixed as well. Cc: Sekhar Nori Cc: Kevin Hilman Signed-off-by: Viresh Kumar --- V3->V4: - Fixed an

[PATCH V4 1/8] ARM: davinci: Sort frequency table

This is required for some of the changes in cpufreq core. There was only one function dependent on the order of the table, that is fixed as well. Cc: Sekhar Nori Cc: Kevin Hilman Signed-off-by: Viresh Kumar --- V3->V4: - Fixed an error reported by buildbot, by removing '&' before usage of

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

Hi Stephen, On Sun, Jun 5, 2016 at 4:55 PM, Stephen Rothwell wrote: > Hi Kevin, > > After merging the amlogic tree, today's linux-next build (arm > multi_v7_defconfig) failed like this: > > In file included from arch/arm/boot/dts/meson8b-mxq.dts:48:0: >

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

Hi Stephen, On Sun, Jun 5, 2016 at 4:55 PM, Stephen Rothwell wrote: > Hi Kevin, > > After merging the amlogic tree, today's linux-next build (arm > multi_v7_defconfig) failed like this: > > In file included from arch/arm/boot/dts/meson8b-mxq.dts:48:0: > arch/arm/boot/dts/meson8b.dtsi:49:53:

[PATCH] mailmap: update Matt Ranostay email address

Set current email address to replace previous employers email addresses. Cc: Jonathan Cameron Cc: Daniel Baluta Cc: linux-...@vger.kernel.org Signed-off-by: Matt Ranostay --- .mailmap | 2 ++ 1 file changed, 2 insertions(+) diff

[PATCH] mailmap: update Matt Ranostay email address

Set current email address to replace previous employers email addresses. Cc: Jonathan Cameron Cc: Daniel Baluta Cc: linux-...@vger.kernel.org Signed-off-by: Matt Ranostay --- .mailmap | 2 ++ 1 file changed, 2 insertions(+) diff --git a/.mailmap b/.mailmap index 08b8042..af8631f 100644 ---

Re: [PATCH 3/3] ARM: configs: keystone: Enable PINCTRL_SINGLE Config

On Wednesday 25 May 2016 08:51 AM, Keerthy wrote: Hi Santosh, On Tuesday 24 May 2016 09:59 PM, Santosh Shilimkar wrote: Hi Keerthy, On 5/23/2016 8:56 PM, Keerthy wrote: On Tuesday 24 May 2016 09:07 AM, Lokesh Vutla wrote: On Monday 23 May 2016 05:59 PM, Keerthy wrote: keystone-k2l

Re: [PATCH 3/3] ARM: configs: keystone: Enable PINCTRL_SINGLE Config

On Wednesday 25 May 2016 08:51 AM, Keerthy wrote: Hi Santosh, On Tuesday 24 May 2016 09:59 PM, Santosh Shilimkar wrote: Hi Keerthy, On 5/23/2016 8:56 PM, Keerthy wrote: On Tuesday 24 May 2016 09:07 AM, Lokesh Vutla wrote: On Monday 23 May 2016 05:59 PM, Keerthy wrote: keystone-k2l

Re: [PATCH v3 2/2] mfd: lp873x: Add lp873x PMIC support

Hi Lee Jones, On Tuesday 17 May 2016 04:19 PM, Lee Jones wrote: On Tue, 17 May 2016, Keerthy wrote: On Friday 13 May 2016 09:18 AM, Keerthy wrote: The LP873X chip is a power management IC for Portable Navigation Systems and Tablet Computing devices. It contains the following

Re: [PATCH v3 2/2] mfd: lp873x: Add lp873x PMIC support

Hi Lee Jones, On Tuesday 17 May 2016 04:19 PM, Lee Jones wrote: On Tue, 17 May 2016, Keerthy wrote: On Friday 13 May 2016 09:18 AM, Keerthy wrote: The LP873X chip is a power management IC for Portable Navigation Systems and Tablet Computing devices. It contains the following

Re: [RFC PATCH v1 1/6] rockchip: rockchip: add new clock-type for the ddrclk

Hi Heiko, On 2016年06月03日 20:51, Heiko Stübner wrote: Am Freitag, 3. Juni 2016, 17:55:14 schrieb Lin Huang: On new rockchip platform(rk3399 etc), there have dcf controller to do ddr frequency scaling, and this controller will implement in arm-trust-firmware. We add a special clock-type to

Re: [RFC PATCH v1 1/6] rockchip: rockchip: add new clock-type for the ddrclk

Hi Heiko, On 2016年06月03日 20:51, Heiko Stübner wrote: Am Freitag, 3. Juni 2016, 17:55:14 schrieb Lin Huang: On new rockchip platform(rk3399 etc), there have dcf controller to do ddr frequency scaling, and this controller will implement in arm-trust-firmware. We add a special clock-type to

[PATCH 0/4] Lustre fixes and cleanups

From: Oleg Drokin Here are a few more Lustre fixes and cleanups. Jinshan Xiong (2): staging/lustre/lov: calculate file offset correctly staging/lustre/llite: define per open file cache for ll_cl_context Oleg Drokin (2): staging/lustre/osc: Remove ops_temp from

[PATCH 0/4] Lustre fixes and cleanups

From: Oleg Drokin Here are a few more Lustre fixes and cleanups. Jinshan Xiong (2): staging/lustre/lov: calculate file offset correctly staging/lustre/llite: define per open file cache for ll_cl_context Oleg Drokin (2): staging/lustre/osc: Remove ops_temp from osc_page

[PATCH 1/4] staging/lustre/lov: calculate file offset correctly

From: Jinshan Xiong In lov_stripe_pgoff(), it calls lov_stripe_size() to calculate the file size by ost_size, which will be wrong if the stripe_index happens to be stripe aligned. Signed-off-by: Jinshan Xiong Reviewed-on:

[PATCH 1/4] staging/lustre/lov: calculate file offset correctly

From: Jinshan Xiong In lov_stripe_pgoff(), it calls lov_stripe_size() to calculate the file size by ost_size, which will be wrong if the stripe_index happens to be stripe aligned. Signed-off-by: Jinshan Xiong Reviewed-on: http://review.whamcloud.com/14462 Intel-bug-id:

[PATCH 2/4] staging/lustre/llite: define per open file cache for ll_cl_context

From: Jinshan Xiong In ll_readpage and ll_write_begin, it needs to find out the cl_env and cl_io, a.k.a ll_cl_context, when the IO is initialized. It used to call cl_env_get() to figure it out but turned out to be contended if multiple threads are doing IO. In this

[PATCH 3/4] staging/lustre/osc: Remove ops_temp from osc_page

From: Oleg Drokin It's no longer used and never set anywhere. Signed-off-by: Oleg Drokin --- drivers/staging/lustre/lustre/osc/osc_cl_internal.h | 5 - drivers/staging/lustre/lustre/osc/osc_page.c| 2 +- 2 files changed, 1 insertion(+),

[PATCH 4/4] staging/lustre/osc: Get rid of osc_page_protected()

From: Oleg Drokin There was a proper debugging function by that name that's long gone. The currently remaining shadow that always returns true is not really useful so it could be dropped along with all the asserts it is part of. Signed-off-by: Oleg Drokin

[PATCH 3/4] staging/lustre/osc: Remove ops_temp from osc_page

From: Oleg Drokin It's no longer used and never set anywhere. Signed-off-by: Oleg Drokin --- drivers/staging/lustre/lustre/osc/osc_cl_internal.h | 5 - drivers/staging/lustre/lustre/osc/osc_page.c| 2 +- 2 files changed, 1 insertion(+), 6 deletions(-) diff --git

[PATCH 4/4] staging/lustre/osc: Get rid of osc_page_protected()

From: Oleg Drokin There was a proper debugging function by that name that's long gone. The currently remaining shadow that always returns true is not really useful so it could be dropped along with all the asserts it is part of. Signed-off-by: Oleg Drokin ---

[PATCH 2/4] staging/lustre/llite: define per open file cache for ll_cl_context

From: Jinshan Xiong In ll_readpage and ll_write_begin, it needs to find out the cl_env and cl_io, a.k.a ll_cl_context, when the IO is initialized. It used to call cl_env_get() to figure it out but turned out to be contended if multiple threads are doing IO. In this patch, a per open file

Re: [PATCH v3 06/12] power: pwrseq: simple: Add support for regulator and generic property

On Fri, Jun 03, 2016 at 02:35:08PM +0200, Krzysztof Kozlowski wrote: > On 06/03/2016 04:02 AM, Rob Herring wrote: > > On Wed, Jun 01, 2016 at 10:02:15AM +0200, Krzysztof Kozlowski wrote: > >> Some devices need real hard-reset by cutting the power. During power > >> sequence turn off and on the

Re: [PATCH v3 06/12] power: pwrseq: simple: Add support for regulator and generic property

On Fri, Jun 03, 2016 at 02:35:08PM +0200, Krzysztof Kozlowski wrote: > On 06/03/2016 04:02 AM, Rob Herring wrote: > > On Wed, Jun 01, 2016 at 10:02:15AM +0200, Krzysztof Kozlowski wrote: > >> Some devices need real hard-reset by cutting the power. During power > >> sequence turn off and on the

Re: [RFC PATCH v1 3/6] clk: rockchip: rk3399: add ddrc clock support

Hi Heiko, On 2016年06月03日 20:56, Heiko Stübner wrote: Am Freitag, 3. Juni 2016, 17:55:16 schrieb Lin Huang: add ddrc clock setting, so we can do ddr frequency scaling on rk3399 platform in future. Signed-off-by: Lin Huang --- Changes in v1: - remove ddrc source

Re: [RFC PATCH v1 3/6] clk: rockchip: rk3399: add ddrc clock support

Hi Heiko, On 2016年06月03日 20:56, Heiko Stübner wrote: Am Freitag, 3. Juni 2016, 17:55:16 schrieb Lin Huang: add ddrc clock setting, so we can do ddr frequency scaling on rk3399 platform in future. Signed-off-by: Lin Huang --- Changes in v1: - remove ddrc source CLK_IGNORE_UNUSED flag,

[RFC v2 3/4] ARM: mm: add inner/outer sharing value command line

Adds defsharing=inner|outer as an early command line option. Any such command line option will override a platform's choice. Signed-off-by: Bill Mills --- arch/arm/include/asm/pgtable-hwdef.h | 1 + arch/arm/mm/mmu.c| 36

[RFC v2 3/4] ARM: mm: add inner/outer sharing value command line

Adds defsharing=inner|outer as an early command line option. Any such command line option will override a platform's choice. Signed-off-by: Bill Mills --- arch/arm/include/asm/pgtable-hwdef.h | 1 + arch/arm/mm/mmu.c| 36 2 files

[RFC v2 1/4] ARM: mm: add early page table attribute modification ability

Allow early-init to specify modifications to be made to the boot time page table. Any modifications specified will be done with MMU off at the same time that any Phy<->Virt fixup is done. This ability is enabled with ARM_PV_FIXUP. It is currently only implemented for LPAE mode. Signed-off-by:

[RFC v2 0/4] ARM LPAE Outer Shared v2

This RFC series adds support for outer shared LPAE page table attributes. This attribute is needed by at least keystone to achieve dma coherency. The choice is done at early boot time and can co-exist with other platforms that want only inner shared. v2 addresses the concern about changing the

[RFC v2 1/4] ARM: mm: add early page table attribute modification ability

Allow early-init to specify modifications to be made to the boot time page table. Any modifications specified will be done with MMU off at the same time that any Phy<->Virt fixup is done. This ability is enabled with ARM_PV_FIXUP. It is currently only implemented for LPAE mode. Signed-off-by:

[RFC v2 0/4] ARM LPAE Outer Shared v2

This RFC series adds support for outer shared LPAE page table attributes. This attribute is needed by at least keystone to achieve dma coherency. The choice is done at early boot time and can co-exist with other platforms that want only inner shared. v2 addresses the concern about changing the

[RFC v2 4/4] ARM: keystone: dma-coherent with safe fallback

Keystone2 can do DMA coherency but only if: 1) DDR3A DMA buffers are in high physical addresses (0x8__) (DDR3B does not have this constraint) 2) Memory is marked outer shared 3) DMA Master marks transactions as outer shared (This is taken care of in bootloader) Use outer shared

[RFC v2 4/4] ARM: keystone: dma-coherent with safe fallback

Keystone2 can do DMA coherency but only if: 1) DDR3A DMA buffers are in high physical addresses (0x8__) (DDR3B does not have this constraint) 2) Memory is marked outer shared 3) DMA Master marks transactions as outer shared (This is taken care of in bootloader) Use outer shared

[RFC v2 2/4] ARM: mm: Add LPAE support for outer shared

Support early init selection of inner or outer shared page table attributes. In LPAE shared is 3 valued: non-shared, inner-shared, and outer-shared. Provide a mask and both shared values. Shared value in use is stored in variables. The old constants are eliminated to avoid accidental use.

Re: [PATCH v3 RESEND 0/7] Add MDIO bus multiplexer support for iProc SoCs

From: Andrew Lunn Date: Fri, 3 Jun 2016 18:32:47 +0200 >> Reason for resend: >> -Rebased on v4.7-rc1 > > How do you see this getting merged? Via netdev? If so, you should be > based on net-next/master, not v4.7-rc1. Indeed, please respin. Also, in your Subject lines, always

[PATCH] Staging: comedi: comedi_fops.c: Replaced ACCESS_ONCE with READ/WRITE_ONCE

Replaced ACCESS_ONCE calls with READ/WRITE_ONCE calls. Signed-off-by: Andy Eleftherion --- drivers/staging/comedi/comedi_fops.c | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/drivers/staging/comedi/comedi_fops.c

Re: [PATCH] locking/qspinlock: Use this_cpu_ptr instead of this_cpu_dec

On 2016年06月03日 19:37, Peter Zijlstra wrote: On Fri, Jun 03, 2016 at 05:48:50PM +0800, Pan Xinhui wrote: queued_spin_lock_slowpath should not worry about interrupt change node->count by accident because ->count is inc and dec when we enter/leave queued_spin_lock_slowpath. So this_cpu_dec()

Re: [PATCH v3 RESEND 0/7] Add MDIO bus multiplexer support for iProc SoCs

From: Andrew Lunn Date: Fri, 3 Jun 2016 18:32:47 +0200 >> Reason for resend: >> -Rebased on v4.7-rc1 > > How do you see this getting merged? Via netdev? If so, you should be > based on net-next/master, not v4.7-rc1. Indeed, please respin. Also, in your Subject lines, always have a space after

[PATCH] Staging: comedi: comedi_fops.c: Replaced ACCESS_ONCE with READ/WRITE_ONCE

Replaced ACCESS_ONCE calls with READ/WRITE_ONCE calls. Signed-off-by: Andy Eleftherion --- drivers/staging/comedi/comedi_fops.c | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/drivers/staging/comedi/comedi_fops.c b/drivers/staging/comedi/comedi_fops.c index

Re: [PATCH] locking/qspinlock: Use this_cpu_ptr instead of this_cpu_dec

On 2016年06月03日 19:37, Peter Zijlstra wrote: On Fri, Jun 03, 2016 at 05:48:50PM +0800, Pan Xinhui wrote: queued_spin_lock_slowpath should not worry about interrupt change node->count by accident because ->count is inc and dec when we enter/leave queued_spin_lock_slowpath. So this_cpu_dec()

[RFC v2 2/4] ARM: mm: Add LPAE support for outer shared

Support early init selection of inner or outer shared page table attributes. In LPAE shared is 3 valued: non-shared, inner-shared, and outer-shared. Provide a mask and both shared values. Shared value in use is stored in variables. The old constants are eliminated to avoid accidental use.

Re: [RFC PATCH v1 1/6] rockchip: rockchip: add new clock-type for the ddrclk

Hi Heiko, On 2016年06月03日 20:51, Heiko Stübner wrote: Am Freitag, 3. Juni 2016, 17:55:14 schrieb Lin Huang: On new rockchip platform(rk3399 etc), there have dcf controller to do ddr frequency scaling, and this controller will implement in arm-trust-firmware. We add a special clock-type to

nfs4 infinite loop in rpc_clnt_iterate_for_each_xprt without multipath

Hello! I am hitting a strange problem with 4.7.0-rc1, basically eventually my NFS4 client enters a state where it's stuck in an infinite loop in rpc_clnt_iterate_for_each_xprt() called from nfs4_proc_bind_conn_to_session_callback The whole backtrace looks like this: (gdb) bt #0

Re: [RFC PATCH v1 1/6] rockchip: rockchip: add new clock-type for the ddrclk

Hi Heiko, On 2016年06月03日 20:51, Heiko Stübner wrote: Am Freitag, 3. Juni 2016, 17:55:14 schrieb Lin Huang: On new rockchip platform(rk3399 etc), there have dcf controller to do ddr frequency scaling, and this controller will implement in arm-trust-firmware. We add a special clock-type to

nfs4 infinite loop in rpc_clnt_iterate_for_each_xprt without multipath

Hello! I am hitting a strange problem with 4.7.0-rc1, basically eventually my NFS4 client enters a state where it's stuck in an infinite loop in rpc_clnt_iterate_for_each_xprt() called from nfs4_proc_bind_conn_to_session_callback The whole backtrace looks like this: (gdb) bt #0

Re: [PATCH net-next v2 0/5] hv_netvsc: cleanup after untangling the pointer mess

From: Vitaly Kuznetsov Date: Fri, 3 Jun 2016 17:50:57 +0200 > Changes since v1: > - resend when net-next is open [David Miller] > - rebased to current net-next. > > After we made traveling through our internal structures explicit it became > obvious that some functions

Re: [PATCH net-next v2 0/5] hv_netvsc: cleanup after untangling the pointer mess

From: Vitaly Kuznetsov Date: Fri, 3 Jun 2016 17:50:57 +0200 > Changes since v1: > - resend when net-next is open [David Miller] > - rebased to current net-next. > > After we made traveling through our internal structures explicit it became > obvious that some functions take arguments they

Re: [PATCH] locking/qrwlock: fix write unlock issue in big endian

On 2016年06月04日 04:57, Waiman Long wrote: On 06/03/2016 03:17 AM, xinhui wrote: On 2016年06月02日 19:02, Peter Zijlstra wrote: On Thu, Jun 02, 2016 at 12:44:51PM +0200, Arnd Bergmann wrote: On Thursday, June 2, 2016 6:09:08 PM CEST Pan Xinhui wrote: diff --git a/include/asm-generic/qrwlock.h

Re: [PATCH] locking/qrwlock: fix write unlock issue in big endian

On 2016年06月04日 04:57, Waiman Long wrote: On 06/03/2016 03:17 AM, xinhui wrote: On 2016年06月02日 19:02, Peter Zijlstra wrote: On Thu, Jun 02, 2016 at 12:44:51PM +0200, Arnd Bergmann wrote: On Thursday, June 2, 2016 6:09:08 PM CEST Pan Xinhui wrote: diff --git a/include/asm-generic/qrwlock.h

Re: [PATCH 1/1] net: ethernet: Add TSE PCS support to dwmac-socfpga

From: Date: Fri, 3 Jun 2016 02:07:15 -0700 > From: Tien Hock Loh > > This adds support for TSE PCS that uses SGMII adapter when the phy-mode of > the dwmac is set to sgmii > > Signed-off-by: Tien Hock Loh Please at least make an effort

Re: [PATCH 1/1] net: ethernet: Add TSE PCS support to dwmac-socfpga

From: Date: Fri, 3 Jun 2016 02:07:15 -0700 > From: Tien Hock Loh > > This adds support for TSE PCS that uses SGMII adapter when the phy-mode of > the dwmac is set to sgmii > > Signed-off-by: Tien Hock Loh Please at least make an effort to use consistent coding style. You rework this

[PATCH] mmc: core: add auto bkops support

JEDEC eMMC v5.1 introduce an autonomously initiated method for background operations. Host that wants to enable the device to perform background operations during device idle time, should signal the device by setting AUTO_EN in BKOPS_EN field EXT_CSD[163] to 1b. When this bit is set, the device

[PATCH] mmc: core: add auto bkops support

JEDEC eMMC v5.1 introduce an autonomously initiated method for background operations. Host that wants to enable the device to perform background operations during device idle time, should signal the device by setting AUTO_EN in BKOPS_EN field EXT_CSD[163] to 1b. When this bit is set, the device

Re: [PATCH v10 2/7] usb: mux: add generic code for dual role port mux

Hi Peter, On 06/06/2016 09:25 AM, Peter Chen wrote: > On Sun, Jun 05, 2016 at 02:55:56PM +0800, Lu Baolu wrote: >> Hi Peter, >> >> On 06/04/2016 10:28 AM, Peter Chen wrote: >>> On Sat, Jun 04, 2016 at 12:06:06AM +0800, Lu Baolu wrote: > from my point,it is a dual-role switch > driver too,

Re: [PATCH v10 2/7] usb: mux: add generic code for dual role port mux

Hi Peter, On 06/06/2016 09:25 AM, Peter Chen wrote: > On Sun, Jun 05, 2016 at 02:55:56PM +0800, Lu Baolu wrote: >> Hi Peter, >> >> On 06/04/2016 10:28 AM, Peter Chen wrote: >>> On Sat, Jun 04, 2016 at 12:06:06AM +0800, Lu Baolu wrote: > from my point,it is a dual-role switch > driver too,

Fwd: CONGRATULATIONS

Please find attached Letter confirming your email address as one of Google winners for 2016 annual promotion.

Re: [RFC PATCH 2/3] sched/fair: Sync se with root cfs_rq

On Wed, Jun 01, 2016 at 08:39:21PM +0100, Dietmar Eggemann wrote: > Since task utilization is accrued only on the root cfs_rq, there are a > couple of places where the se has to be synced with the root cfs_rq: > > (1) The root cfs_rq has to be updated in attach_entity_load_avg() for > an se

Fwd: CONGRATULATIONS

Please find attached Letter confirming your email address as one of Google winners for 2016 annual promotion.

Re: [RFC PATCH 2/3] sched/fair: Sync se with root cfs_rq

On Wed, Jun 01, 2016 at 08:39:21PM +0100, Dietmar Eggemann wrote: > Since task utilization is accrued only on the root cfs_rq, there are a > couple of places where the se has to be synced with the root cfs_rq: > > (1) The root cfs_rq has to be updated in attach_entity_load_avg() for > an se

Re: [PATCH net-next] net: disable fragment reassembly if high_thresh is zero

From: Michal Kubecek Date: Fri, 27 May 2016 17:53:52 +0200 > Before commit 6d7b857d541e ("net: use lib/percpu_counter API for > fragmentation mem accounting"), setting the reassembly high threshold > to 0 prevented fragment reassembly as first fragment would be always > evicted

Re: [PATCH net-next] net: disable fragment reassembly if high_thresh is zero

From: Michal Kubecek Date: Fri, 27 May 2016 17:53:52 +0200 > Before commit 6d7b857d541e ("net: use lib/percpu_counter API for > fragmentation mem accounting"), setting the reassembly high threshold > to 0 prevented fragment reassembly as first fragment would be always > evicted before second

Re: [PATCH v10 2/7] usb: mux: add generic code for dual role port mux

Hi Peter, On 06/06/2016 10:05 AM, Peter Chen wrote: > On Sun, Jun 05, 2016 at 04:46:55PM +0800, Lu Baolu wrote: >> Hi, >> >> On 06/05/2016 04:33 PM, Jun Li wrote: Port mux is part of dual role switch, but not the whole thing. > Dual role switch includes at least below things: > - ID

Re: [PATCH v10 2/7] usb: mux: add generic code for dual role port mux

Hi Peter, On 06/06/2016 10:05 AM, Peter Chen wrote: > On Sun, Jun 05, 2016 at 04:46:55PM +0800, Lu Baolu wrote: >> Hi, >> >> On 06/05/2016 04:33 PM, Jun Li wrote: Port mux is part of dual role switch, but not the whole thing. > Dual role switch includes at least below things: > - ID

Re: [PATCH v10 2/7] usb: mux: add generic code for dual role port mux

Hi Jun, On 06/06/2016 09:08 AM, Jun Li wrote: > >> -Original Message- >> From: Lu Baolu [mailto:baolu...@linux.intel.com] >> Sent: Sunday, June 05, 2016 4:47 PM >> To: Jun Li ; Peter Chen >> Cc: felipe.ba...@linux.intel.com; Mathias Nyman

Re: [PATCH v10 2/7] usb: mux: add generic code for dual role port mux

Hi Jun, On 06/06/2016 09:08 AM, Jun Li wrote: > >> -Original Message- >> From: Lu Baolu [mailto:baolu...@linux.intel.com] >> Sent: Sunday, June 05, 2016 4:47 PM >> To: Jun Li ; Peter Chen >> Cc: felipe.ba...@linux.intel.com; Mathias Nyman ; >> Greg Kroah-Hartman ; Lee Jones >> ; Heikki

[lkp] [mm] 5c0a85fad9: unixbench.score -6.3% regression

FYI, we noticed a -6.3% regression of unixbench.score due to commit: commit 5c0a85fad949212b3e059692deecdeed74ae7ec7 ("mm: make faultaround produce old ptes") https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master in testcase: unixbench on test machine: lituya: 16 threads

[lkp] [mm] 5c0a85fad9: unixbench.score -6.3% regression

FYI, we noticed a -6.3% regression of unixbench.score due to commit: commit 5c0a85fad949212b3e059692deecdeed74ae7ec7 ("mm: make faultaround produce old ptes") https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master in testcase: unixbench on test machine: lituya: 16 threads

Re: [PATCH] ext4: mballoc.c: fix ac_g_ex and ac_f_ex misuse bug in EXT4_MB_HINT_TRY_GOAL path

Hi, Am I missing something or it's not important at all? Other things: [linfeng@localhost ext4]$ grep EXT4_MB_HINT_MERGE ./* -rHn ./ext4.h:111:#define EXT4_MB_HINT_MERGE0x0001 ./mballoc.c:1871:} else if (max > 0 && (ac->ac_flags & EXT4_MB_HINT_MERGE)) { EXT4_MB_HINT_MERGE is only

Re: [PATCH] ext4: mballoc.c: fix ac_g_ex and ac_f_ex misuse bug in EXT4_MB_HINT_TRY_GOAL path

Hi, Am I missing something or it's not important at all? Other things: [linfeng@localhost ext4]$ grep EXT4_MB_HINT_MERGE ./* -rHn ./ext4.h:111:#define EXT4_MB_HINT_MERGE0x0001 ./mballoc.c:1871:} else if (max > 0 && (ac->ac_flags & EXT4_MB_HINT_MERGE)) { EXT4_MB_HINT_MERGE is only

<    1   2   3   4   5   6   7   8   9   10   >