[PATCH V3 2/5] PCI: exynos: Replace the *_blk/*_phy/*_elb accessors

There is no reason to maintain *_blk/phy/elbi_* as register accessors. It can be replaced to one accessor for maintaining more easier. Signed-off-by: Jaehoon Chung Reviewed-by: Pankaj Dubey Acked-by: Krzysztof Kozlowski ---

[PATCH V3 2/5] PCI: exynos: Replace the *_blk/*_phy/*_elb accessors

There is no reason to maintain *_blk/phy/elbi_* as register accessors. It can be replaced to one accessor for maintaining more easier. Signed-off-by: Jaehoon Chung Reviewed-by: Pankaj Dubey Acked-by: Krzysztof Kozlowski --- Changelog on V3: - Split from previous [PATCH V2 1/4] "PCI:

[PATCH V3 5/5] PCI: exynos: remove the duplicated codes

Removed the duplicated codes. It can use the more simply than now. Signed-off-by: Jaehoon Chung Reviewed-by: Pankaj Dubey Acked-by: Krzysztof Kozlowski --- Changelog on V3: - None Changelog on V2: - None

[PATCH V3 5/5] PCI: exynos: remove the duplicated codes

Removed the duplicated codes. It can use the more simply than now. Signed-off-by: Jaehoon Chung Reviewed-by: Pankaj Dubey Acked-by: Krzysztof Kozlowski --- Changelog on V3: - None Changelog on V2: - None drivers/pci/host/pci-exynos.c | 22 -- 1 file changed, 8

[PATCH V3 1/5] PCI: exynos: Rename all pointer names from "exynos_pcie" to "ep"

Rename the simple pointer name as "ep" instead of "exynos_pcie". After applying this patch, it can save the 10 characthers within one line. Signed-off-by: Jaehoon Chung Reviewed-by: Pankaj Dubey Acked-by: Krzysztof Kozlowski

[PATCH V3 1/5] PCI: exynos: Rename all pointer names from "exynos_pcie" to "ep"

Rename the simple pointer name as "ep" instead of "exynos_pcie". After applying this patch, it can save the 10 characthers within one line. Signed-off-by: Jaehoon Chung Reviewed-by: Pankaj Dubey Acked-by: Krzysztof Kozlowski --- Changelog on V3: - Split from previous [PATCH V2 1/4]

Re: [PATCH v2 1/4] mfd: max77686: Don't attempt to get i2c_device_id .data

Hi, On 2017년 01월 13일 22:34, Javier Martinez Canillas wrote: > The driver is only used in platforms that have DT support so always the > I2C device .data will be get from the matched OF node and never will be > from the I2C device ID table. > > Signed-off-by: Javier Martinez Canillas

Re: [PATCH v2 1/4] mfd: max77686: Don't attempt to get i2c_device_id .data

Hi, On 2017년 01월 13일 22:34, Javier Martinez Canillas wrote: > The driver is only used in platforms that have DT support so always the > I2C device .data will be get from the matched OF node and never will be > from the I2C device ID table. > > Signed-off-by: Javier Martinez Canillas > Acked-by:

Re: [PATCH v19 00/15] acpi, clocksource: add GTDT driver and GTDT support in arm_arch_timer

Hi Mark, This v19 (I have mentioned it in my previous email) is the latest patchset which can be applied on v4.10-rc4 directly. please review this patchset, thanks! :-) On 21 December 2016 at 14:45, wrote: > From: Fu Wei > > This patchset: >

Re: [PATCH v19 00/15] acpi, clocksource: add GTDT driver and GTDT support in arm_arch_timer

Hi Mark, This v19 (I have mentioned it in my previous email) is the latest patchset which can be applied on v4.10-rc4 directly. please review this patchset, thanks! :-) On 21 December 2016 at 14:45, wrote: > From: Fu Wei > > This patchset: > (1)Preparation for adding GTDT support in

Re: [PATCH v2] xen-netfront: Fix Rx stall during network stress and OOM

On 13/01/17 18:55, Remanan Pillai wrote: > From: Vineeth Remanan Pillai > > During an OOM scenario, request slots could not be created as skb > allocation fails. So the netback cannot pass in packets and netfront > wrongly assumes that there is no more work to be done and it

Re: [PATCH v2] xen-netfront: Fix Rx stall during network stress and OOM

On 13/01/17 18:55, Remanan Pillai wrote: > From: Vineeth Remanan Pillai > > During an OOM scenario, request slots could not be created as skb > allocation fails. So the netback cannot pass in packets and netfront > wrongly assumes that there is no more work to be done and it disables > polling.

Re: [PATCH v2] partially revert "xen: Remove event channel notification through Xen PCI platform device"

On 13/01/17 19:44, Boris Ostrovsky wrote: > On 01/13/2017 01:26 PM, Stefano Stabellini wrote: >> On Fri, 13 Jan 2017, Boris Ostrovsky wrote: >>> On 01/12/2017 04:39 PM, Stefano Stabellini wrote: The following commit: commit 72a9b186292d98494f26cfd24a1621796209 Author:

Re: [PATCH v2] partially revert "xen: Remove event channel notification through Xen PCI platform device"

On 13/01/17 19:44, Boris Ostrovsky wrote: > On 01/13/2017 01:26 PM, Stefano Stabellini wrote: >> On Fri, 13 Jan 2017, Boris Ostrovsky wrote: >>> On 01/12/2017 04:39 PM, Stefano Stabellini wrote: The following commit: commit 72a9b186292d98494f26cfd24a1621796209 Author:

[PATCH v2] irqchip: irq-mips-gic:- Avoiding Kernel panics due to Error.

Eliminating kernel panic due to NULL pointer dereferencing and other failure in __gic_init. Here, __gic_init can fail. This error check will avoid NULL pointer dereference and kernel panic. Signed-off-by: Arvind Yadav --- drivers/irqchip/irq-mips-gic.c | 40

[PATCH v2] irqchip: irq-mips-gic:- Avoiding Kernel panics due to Error.

Eliminating kernel panic due to NULL pointer dereferencing and other failure in __gic_init. Here, __gic_init can fail. This error check will avoid NULL pointer dereference and kernel panic. Signed-off-by: Arvind Yadav --- drivers/irqchip/irq-mips-gic.c | 40

Re: [PATCH 36/37] ARM: DRA7: clockdomain: Change the CLKTRCTRL of CM_PCIE_CLKSTCTRL to SW_WKUP

Hi Tony, On Friday 13 January 2017 10:45 PM, Tony Lindgren wrote: > * Kishon Vijay Abraham I [170112 02:35]: >> The PCIe programming sequence in TRM suggests CLKSTCTRL of PCIe should >> be set to SW_WKUP. There are no issues when CLKSTCTRL is set to HW_AUTO >> in RC mode. However

Re: [PATCH 36/37] ARM: DRA7: clockdomain: Change the CLKTRCTRL of CM_PCIE_CLKSTCTRL to SW_WKUP

Hi Tony, On Friday 13 January 2017 10:45 PM, Tony Lindgren wrote: > * Kishon Vijay Abraham I [170112 02:35]: >> The PCIe programming sequence in TRM suggests CLKSTCTRL of PCIe should >> be set to SW_WKUP. There are no issues when CLKSTCTRL is set to HW_AUTO >> in RC mode. However in EP mode, the

Re: [PATCH 16/37] PCI: endpoint: Introduce configfs entry for configuring EP functions

Hi Christoph, On Friday 13 January 2017 11:36 PM, Christoph Hellwig wrote: > Hi Kishon, > > a couple comments on the configfs layout based on my experiments with > your previous drop to implement a NVMe device using it. Thanks for trying it out! > > I don't think most of these configfs files

Re: [PATCH 16/37] PCI: endpoint: Introduce configfs entry for configuring EP functions

Hi Christoph, On Friday 13 January 2017 11:36 PM, Christoph Hellwig wrote: > Hi Kishon, > > a couple comments on the configfs layout based on my experiments with > your previous drop to implement a NVMe device using it. Thanks for trying it out! > > I don't think most of these configfs files

Re: [Lsf-pc] [LSF/MM TOPIC] [LSF/MM ATTEND] md raid general discussion

On Mon, 2017-01-16 at 11:33 +0800, Guoqing Jiang wrote: > > On 01/10/2017 12:38 AM, Coly Li wrote: > > Hi Folks, > > > > I'd like to propose a general md raid discussion, it is quite > > necessary for most of active md raid developers sit together to > > discuss current challenge of Linux

Re: [Lsf-pc] [LSF/MM TOPIC] [LSF/MM ATTEND] md raid general discussion

On Mon, 2017-01-16 at 11:33 +0800, Guoqing Jiang wrote: > > On 01/10/2017 12:38 AM, Coly Li wrote: > > Hi Folks, > > > > I'd like to propose a general md raid discussion, it is quite > > necessary for most of active md raid developers sit together to > > discuss current challenge of Linux

Re: [PATCH 0/6] PM / Domains: Implement domain performance states

On 03-01-17, 16:36, Viresh Kumar wrote: > Hi, > > An earlier series[1] tried to implement bindings for PM domain > performance states. Rob Herring suggested that we can actually write the > supporting code first instead of bindings, as that will make things > easier to understand for all. > >

Re: [PATCH 0/6] PM / Domains: Implement domain performance states

On 03-01-17, 16:36, Viresh Kumar wrote: > Hi, > > An earlier series[1] tried to implement bindings for PM domain > performance states. Rob Herring suggested that we can actually write the > supporting code first instead of bindings, as that will make things > easier to understand for all. > >

Re: [PATCH 11/37] PCI: dwc: Split pcie-designware.c into host and core files

Hi Joao, On Friday 13 January 2017 10:19 PM, Joao Pinto wrote: > Às 10:26 AM de 1/12/2017, Kishon Vijay Abraham I escreveu: >> Split pcie-designware.c into pcie-designware-host.c that contains >> the host specific parts of the driver and pcie-designware.c that >> contains the parts used by both

Re: [PATCH 09/37] PCI: dwc: designware: Parse *num-lanes* property in dw_pcie_setup_rc

Hi, On Friday 13 January 2017 10:43 PM, Joao Pinto wrote: > Hi, > > Às 10:25 AM de 1/12/2017, Kishon Vijay Abraham I escreveu: >> *num-lanes* dt property is parsed in dw_pcie_host_init. However >> *num-lanes* property is applicable to both root complex mode and >> endpoint mode. As a first step,

Re: [PATCH 11/37] PCI: dwc: Split pcie-designware.c into host and core files

Hi Joao, On Friday 13 January 2017 10:19 PM, Joao Pinto wrote: > Às 10:26 AM de 1/12/2017, Kishon Vijay Abraham I escreveu: >> Split pcie-designware.c into pcie-designware-host.c that contains >> the host specific parts of the driver and pcie-designware.c that >> contains the parts used by both

Re: [PATCH 09/37] PCI: dwc: designware: Parse *num-lanes* property in dw_pcie_setup_rc

Hi, On Friday 13 January 2017 10:43 PM, Joao Pinto wrote: > Hi, > > Às 10:25 AM de 1/12/2017, Kishon Vijay Abraham I escreveu: >> *num-lanes* dt property is parsed in dw_pcie_host_init. However >> *num-lanes* property is applicable to both root complex mode and >> endpoint mode. As a first step,

Re: [RFC PATCH 1/3] mmc: sdhci: Add platform_dumpregs callback support to sdhci_ops.

On Mon, Jan 16, 2017 at 07:45:48AM +0530, Ritesh Harjani wrote: > Hi Jeremy, > > Thanks for the review. > > On 1/14/2017 3:51 AM, Jeremy McNicoll wrote: > >On Fri, Dec 30, 2016 at 05:02:09PM +0530, Ritesh Harjani wrote: > >>From: Sahitya Tummala > >> > >>Add new host

Re: [PATCH 12/37] PCI: dwc: Create a new config symbol to enable pci dwc host

Hi Joao, On Friday 13 January 2017 11:20 PM, Joao Pinto wrote: > Hi Kishon, > > Às 10:26 AM de 1/12/2017, Kishon Vijay Abraham I escreveu: >> Now that pci designware host has a separate file, create a new >> config symbol to select the host only driver. This is in preparation >> to enable

Re: [RFC PATCH 1/3] mmc: sdhci: Add platform_dumpregs callback support to sdhci_ops.

On Mon, Jan 16, 2017 at 07:45:48AM +0530, Ritesh Harjani wrote: > Hi Jeremy, > > Thanks for the review. > > On 1/14/2017 3:51 AM, Jeremy McNicoll wrote: > >On Fri, Dec 30, 2016 at 05:02:09PM +0530, Ritesh Harjani wrote: > >>From: Sahitya Tummala > >> > >>Add new host operation

Re: [PATCH 12/37] PCI: dwc: Create a new config symbol to enable pci dwc host

Hi Joao, On Friday 13 January 2017 11:20 PM, Joao Pinto wrote: > Hi Kishon, > > Às 10:26 AM de 1/12/2017, Kishon Vijay Abraham I escreveu: >> Now that pci designware host has a separate file, create a new >> config symbol to select the host only driver. This is in preparation >> to enable

Re: [RFC PATCH 2/3] mmc: sdhci-msm: Implement platform_dumpregs callback in sdhci-msm

On Mon, Jan 16, 2017 at 07:51:40AM +0530, Ritesh Harjani wrote: > Hi Jeremy, > > On 1/14/2017 4:01 AM, Jeremy McNicoll wrote: > >On Fri, Dec 30, 2016 at 05:02:10PM +0530, Ritesh Harjani wrote: > >>From: Sahitya Tummala > >> > >>Implement ->platform_dumpregs host

Re: [RFC PATCH 2/3] mmc: sdhci-msm: Implement platform_dumpregs callback in sdhci-msm

On Mon, Jan 16, 2017 at 07:51:40AM +0530, Ritesh Harjani wrote: > Hi Jeremy, > > On 1/14/2017 4:01 AM, Jeremy McNicoll wrote: > >On Fri, Dec 30, 2016 at 05:02:10PM +0530, Ritesh Harjani wrote: > >>From: Sahitya Tummala > >> > >>Implement ->platform_dumpregs host operation to print the >

Re: [PATCH v7 00/15] ACPI platform MSI support and its example mbigen

Hi Hanjun, On 1/11/2017 10:06 AM, Hanjun Guo wrote: > With platform msi support landed in the kernel, and the introduction > of IORT for GICv3 ITS (PCI MSI) and SMMU, the framework for platform msi > is ready, this patch set add few patches to enable the ACPI platform > msi support. > > For

Re: [PATCH v7 00/15] ACPI platform MSI support and its example mbigen

Hi Hanjun, On 1/11/2017 10:06 AM, Hanjun Guo wrote: > With platform msi support landed in the kernel, and the introduction > of IORT for GICv3 ITS (PCI MSI) and SMMU, the framework for platform msi > is ready, this patch set add few patches to enable the ACPI platform > msi support. > > For

Re: [PATCH] Staging: media: bcm2048: style fix - bare use of unsigned

On Sun, Jan 15, 2017 at 10:40:02PM -0600, Scott Matheina wrote: > > > > On Jan 15, 2017, at 10:30 PM, Derek Robson wrote: > > > > Changed bare use of 'unsigned' to the prefered us of 'unsigned int' > > found using checkpatch > > Just wondering if you compiled? This patch

Re: [PATCH] Staging: media: bcm2048: style fix - bare use of unsigned

On Sun, Jan 15, 2017 at 10:40:02PM -0600, Scott Matheina wrote: > > > > On Jan 15, 2017, at 10:30 PM, Derek Robson wrote: > > > > Changed bare use of 'unsigned' to the prefered us of 'unsigned int' > > found using checkpatch > > Just wondering if you compiled? This patch looks exactly like a

Re: [PATCH] Staging: media: bcm2048: style fix - bare use of unsigned

Hi Derek, [auto build test ERROR on linuxtv-media/master] [also build test ERROR on v4.10-rc4 next-20170113] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH] Staging: media: bcm2048: style fix - bare use of unsigned

Hi Derek, [auto build test ERROR on linuxtv-media/master] [also build test ERROR on v4.10-rc4 next-20170113] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

[PATCH] iio: bmi160: use variable names for sizeof() operator

Replace the types with the actual variable names when using the sizeof() operator. This is kernel preferred style as it protects against future changes to variable type. Signed-off-by: Alison Schofield --- drivers/iio/imu/bmi160/bmi160_core.c | 8 1 file changed,

[PATCH] iio: bmi160: use variable names for sizeof() operator

Replace the types with the actual variable names when using the sizeof() operator. This is kernel preferred style as it protects against future changes to variable type. Signed-off-by: Alison Schofield --- drivers/iio/imu/bmi160/bmi160_core.c | 8 1 file changed, 4 insertions(+), 4

Re: [PATCH 4/4] clk: rockchip: add rk3288 cif_out clock

2017-01-13 21:53 GMT+08:00 Heiko Stuebner : > Hi Jacob, > > Am Dienstag, 10. Januar 2017, 19:59:20 CET schrieb Jacob Chen: >> Add the clocks for the cif block of the rk3288 >> >> Signed-off-by: Jacob Chen >> --- >> drivers/clk/rockchip/clk-rk3288.c | 7

Re: [PATCH 4/4] clk: rockchip: add rk3288 cif_out clock

2017-01-13 21:53 GMT+08:00 Heiko Stuebner : > Hi Jacob, > > Am Dienstag, 10. Januar 2017, 19:59:20 CET schrieb Jacob Chen: >> Add the clocks for the cif block of the rk3288 >> >> Signed-off-by: Jacob Chen >> --- >> drivers/clk/rockchip/clk-rk3288.c | 7 +++ >> 1 file changed, 7 insertions(+)

Re: [PATCH] rcu: Narrow early boot window of illegal synchronous grace periods

On Mon, Jan 16, 2017 at 01:57:25AM +, Zheng, Lv wrote: > Hi, > > > From: Borislav Petkov [mailto:b...@alien8.de] > > Subject: Re: [PATCH] rcu: Narrow early boot window of illegal synchronous > > grace periods > > > > On Sat, Jan 14, 2017 at 01:27:40PM +0100, Rafael J. Wysocki wrote: > > >

Re: [PATCH] rcu: Narrow early boot window of illegal synchronous grace periods

On Mon, Jan 16, 2017 at 01:57:25AM +, Zheng, Lv wrote: > Hi, > > > From: Borislav Petkov [mailto:b...@alien8.de] > > Subject: Re: [PATCH] rcu: Narrow early boot window of illegal synchronous > > grace periods > > > > On Sat, Jan 14, 2017 at 01:27:40PM +0100, Rafael J. Wysocki wrote: > > >

Re: [PATCH] Staging: media: bcm2048: style fix - bare use of unsigned

> On Jan 15, 2017, at 10:30 PM, Derek Robson wrote: > > Changed bare use of 'unsigned' to the prefered us of 'unsigned int' > found using checkpatch Just wondering if you compiled? This patch looks exactly like a patch I tried, but it didn't compile. > Signed-off-by:

Re: [PATCH] Staging: media: bcm2048: style fix - bare use of unsigned

> On Jan 15, 2017, at 10:30 PM, Derek Robson wrote: > > Changed bare use of 'unsigned' to the prefered us of 'unsigned int' > found using checkpatch Just wondering if you compiled? This patch looks exactly like a patch I tried, but it didn't compile. > Signed-off-by: Derek Robson > --- >

Re: [PATCH 1/6] mm: introduce kv[mz]alloc helpers

On 01/12/2017 07:37 AM, Michal Hocko wrote: From: Michal Hocko Using kmalloc with the vmalloc fallback for larger allocations is a common pattern in the kernel code. Yet we do not have any common helper for that and so users have invented their own helpers. Some of them are

Re: [PATCH 1/6] mm: introduce kv[mz]alloc helpers

On 01/12/2017 07:37 AM, Michal Hocko wrote: From: Michal Hocko Using kmalloc with the vmalloc fallback for larger allocations is a common pattern in the kernel code. Yet we do not have any common helper for that and so users have invented their own helpers. Some of them are really creative

[PATCH] Staging: media: bcm2048: style fix - bare use of unsigned

Changed bare use of 'unsigned' to the prefered us of 'unsigned int' found using checkpatch Signed-off-by: Derek Robson --- drivers/staging/media/bcm2048/radio-bcm2048.c | 44 +-- 1 file changed, 22 insertions(+), 22 deletions(-) diff --git

[PATCH] Staging: media: bcm2048: style fix - bare use of unsigned

Changed bare use of 'unsigned' to the prefered us of 'unsigned int' found using checkpatch Signed-off-by: Derek Robson --- drivers/staging/media/bcm2048/radio-bcm2048.c | 44 +-- 1 file changed, 22 insertions(+), 22 deletions(-) diff --git

linux-next: Tree for Jan 16

Hi all, Changes since 20170113: Non-merge commits (relative to Linus' tree): 3275 4116 files changed, 129983 insertions(+), 77532 deletions(-) I have created today's linux-next tree at

linux-next: Tree for Jan 16

Hi all, Changes since 20170113: Non-merge commits (relative to Linus' tree): 3275 4116 files changed, 129983 insertions(+), 77532 deletions(-) I have created today's linux-next tree at

[PATCH v1 3/3] watchdog: zx2967: add watchdog controller driver for ZTE's zx2967 family

This patch adds watchdog controller driver for ZTE's zx2967 family. Signed-off-by: Baoyou Xie --- drivers/watchdog/Kconfig | 10 ++ drivers/watchdog/Makefile | 1 + drivers/watchdog/zx2967_wdt.c | 405 ++ 3 files

[PATCH v1 3/3] watchdog: zx2967: add watchdog controller driver for ZTE's zx2967 family

This patch adds watchdog controller driver for ZTE's zx2967 family. Signed-off-by: Baoyou Xie --- drivers/watchdog/Kconfig | 10 ++ drivers/watchdog/Makefile | 1 + drivers/watchdog/zx2967_wdt.c | 405 ++ 3 files changed, 416 insertions(+)

[PATCH v1 2/3] MAINTAINERS: add zx2967 watchdog controller driver to ARM ZTE architecture

Add the zx2967 watchdog controller driver as maintained by ARM ZTE architecture maintainers, as they're parts of the core IP. Signed-off-by: Baoyou Xie --- MAINTAINERS | 2 ++ 1 file changed, 2 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 08f8155..77f0290

[PATCH v1 1/3] dt: bindings: add documentation for zx2967 family watchdog controller

This patch adds dt-binding documentation for zx2967 family watchdog controller. Signed-off-by: Baoyou Xie --- .../bindings/watchdog/zte,zx2967-wdt.txt | 29 ++ 1 file changed, 29 insertions(+) create mode 100644

[PATCH v1 2/3] MAINTAINERS: add zx2967 watchdog controller driver to ARM ZTE architecture

Add the zx2967 watchdog controller driver as maintained by ARM ZTE architecture maintainers, as they're parts of the core IP. Signed-off-by: Baoyou Xie --- MAINTAINERS | 2 ++ 1 file changed, 2 insertions(+) diff --git a/MAINTAINERS b/MAINTAINERS index 08f8155..77f0290 100644 --- a/MAINTAINERS

[PATCH v1 1/3] dt: bindings: add documentation for zx2967 family watchdog controller

This patch adds dt-binding documentation for zx2967 family watchdog controller. Signed-off-by: Baoyou Xie --- .../bindings/watchdog/zte,zx2967-wdt.txt | 29 ++ 1 file changed, 29 insertions(+) create mode 100644

[PATCH] rtl8188eu: core: Remove NULL test before vfree

vfree frees the virtually continuous block of memory beginning at addr. If addr is NULL, no operation is performed. So, NULL test is not needed before vfree(). Signed-off-by: Shyam Saini --- drivers/staging/rtl8188eu/core/rtw_xmit.c | 3 +-- 1 file changed, 1

[PATCH] rtl8188eu: core: Remove NULL test before vfree

vfree frees the virtually continuous block of memory beginning at addr. If addr is NULL, no operation is performed. So, NULL test is not needed before vfree(). Signed-off-by: Shyam Saini --- drivers/staging/rtl8188eu/core/rtw_xmit.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff

Re: [RFC for GIT] pull-request: add praise to people doing QA

On Sun, Jan 15, 2017 at 4:35 PM, Junio C Hamano wrote: > As to the implementation, I am wondering if we can make this somehow > work well with the "trailers" code we already have, instead of > inventing yet another parser of trailers. > > In its current shape,

Re: [RFC for GIT] pull-request: add praise to people doing QA

On Sun, Jan 15, 2017 at 4:35 PM, Junio C Hamano wrote: > As to the implementation, I am wondering if we can make this somehow > work well with the "trailers" code we already have, instead of > inventing yet another parser of trailers. > > In its current shape, "interpret-trailers" focuses on

Re: [PATCH 2/4] clk: samsung: Remove Exynos4415 driver (SoC not supported anymore)

Hi, On 2017년 01월 14일 21:36, Krzysztof Kozlowski wrote: > Support for Exynos4415 is going away because there are no internal nor > external users. > > Since commit 46dcf0ff0de3 ("ARM: dts: exynos: Remove exynos4415.dtsi"), > the platform cannot be instantiated so remove also the drivers. > >

Re: [PATCH 2/4] clk: samsung: Remove Exynos4415 driver (SoC not supported anymore)

Hi, On 2017년 01월 14일 21:36, Krzysztof Kozlowski wrote: > Support for Exynos4415 is going away because there are no internal nor > external users. > > Since commit 46dcf0ff0de3 ("ARM: dts: exynos: Remove exynos4415.dtsi"), > the platform cannot be instantiated so remove also the drivers. > >

Re: [PATCH 3/4] pinctrl: samsung: Remove support for Exynos4415 (SoC not supported anymore)

On 2017년 01월 14일 21:36, Krzysztof Kozlowski wrote: > Support for Exynos4415 is going away because there are no internal nor > external users. > > Since commit 46dcf0ff0de3 ("ARM: dts: exynos: Remove exynos4415.dtsi"), > the platform cannot be instantiated so remove also the drivers. > >

Re: [PATCH 1/4] ARM: EXYNOS: Remove Exynos4415 driver (SoC not supported anymore)

On 2017년 01월 14일 21:36, Krzysztof Kozlowski wrote: > Support for Exynos4415 is going away because there are no internal nor > external users. > > Since commit 46dcf0ff0de3 ("ARM: dts: exynos: Remove exynos4415.dtsi"), > the platform cannot be instantiated so remove also the mach code. > >

Re: [PATCH 3/4] pinctrl: samsung: Remove support for Exynos4415 (SoC not supported anymore)

On 2017년 01월 14일 21:36, Krzysztof Kozlowski wrote: > Support for Exynos4415 is going away because there are no internal nor > external users. > > Since commit 46dcf0ff0de3 ("ARM: dts: exynos: Remove exynos4415.dtsi"), > the platform cannot be instantiated so remove also the drivers. > >

Re: [PATCH 1/4] ARM: EXYNOS: Remove Exynos4415 driver (SoC not supported anymore)

On 2017년 01월 14일 21:36, Krzysztof Kozlowski wrote: > Support for Exynos4415 is going away because there are no internal nor > external users. > > Since commit 46dcf0ff0de3 ("ARM: dts: exynos: Remove exynos4415.dtsi"), > the platform cannot be instantiated so remove also the mach code. > >

Re: [PATCH 0/4] selftest: cpufreq: Add support for cpufreq framework

On 13-01-17, 15:35, Shuah Khan wrote: > Could you please add .gitignore for generated files. You can > send that as a separate patch and don't have to resend the > series. Hi Shuah, > > tools/testing/selftests/Makefile | 1 + > > tools/testing/selftests/cpufreq/Makefile

Re: [PATCH 0/4] selftest: cpufreq: Add support for cpufreq framework

On 13-01-17, 15:35, Shuah Khan wrote: > Could you please add .gitignore for generated files. You can > send that as a separate patch and don't have to resend the > series. Hi Shuah, > > tools/testing/selftests/Makefile | 1 + > > tools/testing/selftests/cpufreq/Makefile

Re: [PATCH v2 6/6] arm: dts: mt2701: Add thermal device node.

On Mon, 2017-01-16 at 11:44 +0800, Dawei Chien wrote: > On Fri, 2017-01-13 at 16:27 +0100, Matthias Brugger wrote: > > > > On 13/01/17 09:42, Erin Lo wrote: > > > From: Dawei Chien > > > > > > Add thermal controller device nodes for MT2701. > > > > > > Signed-off-by:

Re: [PATCH v2 6/6] arm: dts: mt2701: Add thermal device node.

On Mon, 2017-01-16 at 11:44 +0800, Dawei Chien wrote: > On Fri, 2017-01-13 at 16:27 +0100, Matthias Brugger wrote: > > > > On 13/01/17 09:42, Erin Lo wrote: > > > From: Dawei Chien > > > > > > Add thermal controller device nodes for MT2701. > > > > > > Signed-off-by: Dawei Chien > > >

Re: [PATCH v2 6/6] arm: dts: mt2701: Add thermal device node.

On Fri, 2017-01-13 at 16:27 +0100, Matthias Brugger wrote: > > On 13/01/17 09:42, Erin Lo wrote: > > From: Dawei Chien > > > > Add thermal controller device nodes for MT2701. > > > > Signed-off-by: Dawei Chien > > Signed-off-by: Erin Lo

Re: [PATCH v6 23/25] usb: chipidea: Pullup D+ in device mode via phy APIs

On Fri, Jan 13, 2017 at 12:03:00PM -0800, Stephen Boyd wrote: > Quoting Peter Chen (2017-01-12 19:35:36) > > On Thu, Jan 12, 2017 at 02:49:51PM -0800, Stephen Boyd wrote: > > > > > > With the boards I have, vbus is not routed to the phy. Instead, there's > > > a vbus comparator on the PMIC where

Re: [PATCH v2 6/6] arm: dts: mt2701: Add thermal device node.

On Fri, 2017-01-13 at 16:27 +0100, Matthias Brugger wrote: > > On 13/01/17 09:42, Erin Lo wrote: > > From: Dawei Chien > > > > Add thermal controller device nodes for MT2701. > > > > Signed-off-by: Dawei Chien > > Signed-off-by: Erin Lo > > --- > > arch/arm/boot/dts/mt2701.dtsi | 43 > >

Re: [PATCH v6 23/25] usb: chipidea: Pullup D+ in device mode via phy APIs

On Fri, Jan 13, 2017 at 12:03:00PM -0800, Stephen Boyd wrote: > Quoting Peter Chen (2017-01-12 19:35:36) > > On Thu, Jan 12, 2017 at 02:49:51PM -0800, Stephen Boyd wrote: > > > > > > With the boards I have, vbus is not routed to the phy. Instead, there's > > > a vbus comparator on the PMIC where

Re: [PATCH] virtio_console: fix a crash in config_work_handler

On (Sat) 14 Jan 2017 [11:38:39], G. Campana wrote: > Using control_work instead of config_work as the 3rd argument to > container_of results in an invalid portdev pointer. Indeed, the work > structure is initialized as below: > > INIT_WORK(>config_work, _work_handler); > > It leads to a

Re: [PATCH] virtio_console: fix a crash in config_work_handler

On (Sat) 14 Jan 2017 [11:38:39], G. Campana wrote: > Using control_work instead of config_work as the 3rd argument to > container_of results in an invalid portdev pointer. Indeed, the work > structure is initialized as below: > > INIT_WORK(>config_work, _work_handler); > > It leads to a

Re: [PATCH v2] checkpatch: update $logFunctions

On Mon, 2017-01-16 at 11:25 +0800, miles.c...@mediatek.com wrote: > From: Miles Chen > > Currently checkpatch.pl does not recognize printk_deferred* functions as > log functions and complains about the line length of printk_deferred* > functoins. Add printk_deferred* to

Re: [PATCH v2] checkpatch: update $logFunctions

On Mon, 2017-01-16 at 11:25 +0800, miles.c...@mediatek.com wrote: > From: Miles Chen > > Currently checkpatch.pl does not recognize printk_deferred* functions as > log functions and complains about the line length of printk_deferred* > functoins. Add printk_deferred* to logFunctions to fix it.

Re: [PATCH 1/2] ocfs2/dlmglue: prepare tracking logic to avoid recursive cluster lock

Hi Junxiao, OK, good suggestion. Hrm, but in order to align with "ocfs2_inc_holders", I think it's good to keep those function names as it is;-) that name is also not very clear. Maybe you can make another patch to clear it. Maybe, the name completeness needs to compromise with the name

Re: [PATCH 1/2] ocfs2/dlmglue: prepare tracking logic to avoid recursive cluster lock

Hi Junxiao, OK, good suggestion. Hrm, but in order to align with "ocfs2_inc_holders", I think it's good to keep those function names as it is;-) that name is also not very clear. Maybe you can make another patch to clear it. Maybe, the name completeness needs to compromise with the name

Re: [LSF/MM TOPIC] [LSF/MM ATTEND] md raid general discussion

On 01/10/2017 12:38 AM, Coly Li wrote: Hi Folks, I'd like to propose a general md raid discussion, it is quite necessary for most of active md raid developers sit together to discuss current challenge of Linux software raid and development trends. In the last years, we have many development

Re: [LSF/MM TOPIC] [LSF/MM ATTEND] md raid general discussion

On 01/10/2017 12:38 AM, Coly Li wrote: Hi Folks, I'd like to propose a general md raid discussion, it is quite necessary for most of active md raid developers sit together to discuss current challenge of Linux software raid and development trends. In the last years, we have many development

[PATCH] fix race caused by hyperthreads when online an offline cpu

After online an offline cpu, cpu_hw_events.excl_thread_id will always be set to 1 in intel_pmu_cpu_starting() even when its sibling's excl_thread_id is also 1. Then the two siblings will use the same state in their shared cpu_hw_events.excl_cntrs, it will cause race problem. The race senario is

[PATCH] fix race caused by hyperthreads when online an offline cpu

After online an offline cpu, cpu_hw_events.excl_thread_id will always be set to 1 in intel_pmu_cpu_starting() even when its sibling's excl_thread_id is also 1. Then the two siblings will use the same state in their shared cpu_hw_events.excl_cntrs, it will cause race problem. The race senario is

[PATCH v2] checkpatch: update $logFunctions

From: Miles Chen Currently checkpatch.pl does not recognize printk_deferred* functions as log functions and complains about the line length of printk_deferred* functoins. Add printk_deferred* to logFunctions to fix it. Signed-off-by: Miles Chen

[PATCH v2] checkpatch: update $logFunctions

From: Miles Chen Currently checkpatch.pl does not recognize printk_deferred* functions as log functions and complains about the line length of printk_deferred* functoins. Add printk_deferred* to logFunctions to fix it. Signed-off-by: Miles Chen --- scripts/checkpatch.pl | 2 +- 1 file

Re: [RFC PATCH] ext4: increase the protection of drop nlink and ext4 inode destroy

on 2017/1/11 23:34, Theodore Ts'o wrote: > On Wed, Jan 11, 2017 at 05:07:29PM +0800, zhangyi (F) wrote: >> >> (1) The file we want to unlink have many hard links, but only one dcache >> entry in memory. >> (2) open this file, but it's inode->i_nlink read from disk was 1 (too low). >> (3) some

Re: [RFC PATCH] ext4: increase the protection of drop nlink and ext4 inode destroy

on 2017/1/11 23:34, Theodore Ts'o wrote: > On Wed, Jan 11, 2017 at 05:07:29PM +0800, zhangyi (F) wrote: >> >> (1) The file we want to unlink have many hard links, but only one dcache >> entry in memory. >> (2) open this file, but it's inode->i_nlink read from disk was 1 (too low). >> (3) some

Re: [PATCH 2/2] ocfs2: fix deadlocks when taking inode lock at vfs entry points

On 01/16/2017 11:13 AM, Junxiao Bi wrote: On 01/16/2017 11:06 AM, Eric Ren wrote: Hi Junxiao, On 01/16/2017 10:46 AM, Junxiao Bi wrote: If had_lock==true, it is a bug? I think we should BUG_ON for it, that can help us catch bug at the first time. Good idea! But I'm not sure if

Re: [PATCH 2/2] ocfs2: fix deadlocks when taking inode lock at vfs entry points

On 01/16/2017 11:13 AM, Junxiao Bi wrote: On 01/16/2017 11:06 AM, Eric Ren wrote: Hi Junxiao, On 01/16/2017 10:46 AM, Junxiao Bi wrote: If had_lock==true, it is a bug? I think we should BUG_ON for it, that can help us catch bug at the first time. Good idea! But I'm not sure if

Re: [PATCH v1 00/54] block: support multipage bvec

Hi Guys, On Tue, Dec 27, 2016 at 11:55 PM, Ming Lei wrote: > Hi, > > This patchset brings multipage bvec into block layer. Basic > xfstests(-a auto) over virtio-blk/virtio-scsi have been run > and no regression is found, so it should be good enough > to show the approach

Re: [PATCH v1 00/54] block: support multipage bvec

Hi Guys, On Tue, Dec 27, 2016 at 11:55 PM, Ming Lei wrote: > Hi, > > This patchset brings multipage bvec into block layer. Basic > xfstests(-a auto) over virtio-blk/virtio-scsi have been run > and no regression is found, so it should be good enough > to show the approach now, and any comments

Re: [patch net-next] stmmac: indent an if statement

From: Dan Carpenter Date: Thu, 12 Jan 2017 21:46:32 +0300 > The break statement should be indented one more tab. > > Signed-off-by: Dan Carpenter Applied, but like Julia I think we might have a missing of_node_put() here.

Re: [patch net-next] stmmac: indent an if statement

From: Dan Carpenter Date: Thu, 12 Jan 2017 21:46:32 +0300 > The break statement should be indented one more tab. > > Signed-off-by: Dan Carpenter Applied, but like Julia I think we might have a missing of_node_put() here.

Re: [PATCH] checkpatch: update $logFunctions

On Mon, 2017-01-16 at 10:57 +0800, Miles Chen wrote: > On Fri, 2017-01-13 at 00:14 -0800, Joe Perches wrote: > > On Fri, 2017-01-13 at 15:38 +0800, miles.c...@mediatek.com wrote: > > > From: Miles Chen > > > > > > Currently checkpatch.pl does not recognize

Re: [PATCH] checkpatch: update $logFunctions

On Mon, 2017-01-16 at 10:57 +0800, Miles Chen wrote: > On Fri, 2017-01-13 at 00:14 -0800, Joe Perches wrote: > > On Fri, 2017-01-13 at 15:38 +0800, miles.c...@mediatek.com wrote: > > > From: Miles Chen > > > > > > Currently checkpatch.pl does not recognize printk_deferred* functions as > > > log

<    1   2   3   4   5   6   7   >