[PATCH v4 3/4] dt-bindings: PCI: rockchip: Add support for pcie wake irq

Add an optional interrupt for PCIE_WAKE pin. Signed-off-by: Jeffy Chen --- Changes in v4: None Changes in v3: None Changes in v2: None .../devicetree/bindings/pci/rockchip-pcie.txt| 20 1 file changed, 12 insertions(+), 8 deletions(-) diff --git

[PATCH v4 1/4] PCI: rockchip: Fix error handlings

Fix error handlings in probe & resume. Signed-off-by: Jeffy Chen --- Changes in v4: Rebase on newest for-next branch, also fix error handling by: 1e7f570a1b86 PCI: rockchip: Idle inactive PHY(s) Changes in v3: None Changes in v2: None drivers/pci/host/pcie-rockchip.c | 160

[PATCH v4 0/4] PCI: rockchip: Move PCIE_WAKE handling into rockchip pcie driver

Currently we are handling pcie wake in mrvl wifi driver. But Brian suggests to move it into rockchip pcie driver. Tested on my chromebook bob(with cros 4.4 kernel and mrvl wifi). Changes in v4: Rebase on newest for-next branch, also fix error handling by: 1e7f570a1b86 PCI: rockchip: Idle

[PATCH v4 2/4] PCI: rockchip: Add support for pcie wake irq

Add support for PCIE_WAKE pin in rockchip pcie driver. Signed-off-by: Jeffy Chen --- Changes in v4: None Changes in v3: Fix error handling Changes in v2: Use dev_pm_set_dedicated_wake_irq -- Suggested by Brian Norris

[PATCH v4 0/4] PCI: rockchip: Move PCIE_WAKE handling into rockchip pcie driver

Currently we are handling pcie wake in mrvl wifi driver. But Brian suggests to move it into rockchip pcie driver. Tested on my chromebook bob(with cros 4.4 kernel and mrvl wifi). Changes in v4: Rebase on newest for-next branch, also fix error handling by: 1e7f570a1b86 PCI: rockchip: Idle

[PATCH v4 2/4] PCI: rockchip: Add support for pcie wake irq

Add support for PCIE_WAKE pin in rockchip pcie driver. Signed-off-by: Jeffy Chen --- Changes in v4: None Changes in v3: Fix error handling Changes in v2: Use dev_pm_set_dedicated_wake_irq -- Suggested by Brian Norris drivers/pci/host/pcie-rockchip.c | 21 +++-- 1

[PATCH][v2] PM / Hibernate: Feed the wathdog when creating snapshot

There is a problem that when counting the pages for creating the hibernation snapshot will take significant amount of time, especially on system with large memory. Since the counting job is performed with irq disabled, this might lead to NMI lockup. The following warning were found on a system

[PATCH][v2] PM / Hibernate: Feed the wathdog when creating snapshot

There is a problem that when counting the pages for creating the hibernation snapshot will take significant amount of time, especially on system with large memory. Since the counting job is performed with irq disabled, this might lead to NMI lockup. The following warning were found on a system

Re: [PATCH v2 1/3] media: V3s: Add support for Allwinner CSI.

Hi Hans, On Mon, 21 Aug 2017 16:37:41 +0200 Hans Verkuil wrote: > Hi Yong, > > First two high-level comments before I start the review: > > 1) Can you provide the v4l2-compliance output? I can't merge this unless I >see that it passes the compliance tests. Make sure

Re: [PATCH v2 1/3] media: V3s: Add support for Allwinner CSI.

Hi Hans, On Mon, 21 Aug 2017 16:37:41 +0200 Hans Verkuil wrote: > Hi Yong, > > First two high-level comments before I start the review: > > 1) Can you provide the v4l2-compliance output? I can't merge this unless I >see that it passes the compliance tests. Make sure you compile from the

RE: [PATCH v3 0/5] fs/dcache: Limit # of negative dentries

> -Original Message- > From: Waiman Long [mailto:long...@redhat.com] > Sent: Monday, August 21, 2017 9:35 PM > To: Wangkai (Kevin,C); Alexander Viro; Jonathan Corbet > Cc: linux-kernel@vger.kernel.org; linux-...@vger.kernel.org; > linux-fsde...@vger.kernel.org; Paul E. McKenney; Andrew

RE: [PATCH v3 0/5] fs/dcache: Limit # of negative dentries

> -Original Message- > From: Waiman Long [mailto:long...@redhat.com] > Sent: Monday, August 21, 2017 9:35 PM > To: Wangkai (Kevin,C); Alexander Viro; Jonathan Corbet > Cc: linux-kernel@vger.kernel.org; linux-...@vger.kernel.org; > linux-fsde...@vger.kernel.org; Paul E. McKenney; Andrew

Re: [PATCH] PM / Hibernate: Feed the wathdog when creating snapshot

Hi Andrew, On Mon, Aug 21, 2017 at 01:26:00PM -0700, Andrew Morton wrote: > On Mon, 21 Aug 2017 23:08:18 +0800 Chen Yu wrote: > > > There is a problem that when counting the pages for creating > > the hibernation snapshot will take significant amount of > > time, especially

Re: [PATCH] PM / Hibernate: Feed the wathdog when creating snapshot

Hi Andrew, On Mon, Aug 21, 2017 at 01:26:00PM -0700, Andrew Morton wrote: > On Mon, 21 Aug 2017 23:08:18 +0800 Chen Yu wrote: > > > There is a problem that when counting the pages for creating > > the hibernation snapshot will take significant amount of > > time, especially on system with large

Re: [PATCH v6 1/3] dt-bindings: display: Add Document for Rockchip Soc LVDS

On Fri, Aug 18, 2017 at 04:09:49PM +0800, Sandy Huang wrote: > This patch add Document for Rockchip Soc RK3288 LVDS, > This based on the patches from Mark yao and Heiko Stuebner. > > Signed-off-by: Sandy Huang > Signed-off-by: Mark yao >

Re: [PATCH v6 1/3] dt-bindings: display: Add Document for Rockchip Soc LVDS

On Fri, Aug 18, 2017 at 04:09:49PM +0800, Sandy Huang wrote: > This patch add Document for Rockchip Soc RK3288 LVDS, > This based on the patches from Mark yao and Heiko Stuebner. > > Signed-off-by: Sandy Huang > Signed-off-by: Mark yao > Signed-off-by: Heiko Stuebner > --- > Changes: > -

Re: [PATCH v2 2/2] dt-bindings: input: Add documentation for cyttsp5

On Fri, Aug 18, 2017 at 08:20:45AM +0200, Mylène Josserand wrote: > Add the Cypress TrueTouch Generation 5 touchscreen device tree bindings > documentation. It can use I2C or SPI bus. > This touchscreen can handle some defined zone that are designed and > sent as button. To be able to customize

Re: [PATCH v2 2/2] dt-bindings: input: Add documentation for cyttsp5

On Fri, Aug 18, 2017 at 08:20:45AM +0200, Mylène Josserand wrote: > Add the Cypress TrueTouch Generation 5 touchscreen device tree bindings > documentation. It can use I2C or SPI bus. > This touchscreen can handle some defined zone that are designed and > sent as button. To be able to customize

Re: [PATCH RESEND1 00/12] ALSA: vsnd: Add Xen para-virtualized frontend driver

Hi, On Aug 18 2017 16:23, Oleksandr Andrushchenko wrote: >> You mean that any alsa-lib or libpulse applications run on Dom0 as a >> backend driver for the frontend driver on DomU? >> > No, the sound backend [1] is a user-space application (ALSA/PulseAudio > client) > which runs as a Xen

Re: [PATCH RESEND1 00/12] ALSA: vsnd: Add Xen para-virtualized frontend driver

Hi, On Aug 18 2017 16:23, Oleksandr Andrushchenko wrote: >> You mean that any alsa-lib or libpulse applications run on Dom0 as a >> backend driver for the frontend driver on DomU? >> > No, the sound backend [1] is a user-space application (ALSA/PulseAudio > client) > which runs as a Xen

Re: [PATCH v4 2/9] ASoC: rockchip: Remove obsolete dmic-delay

On Fri, Aug 18, 2017 at 11:11:40AM +0800, Jeffy Chen wrote: > This property is no longer used. > > Signed-off-by: Jeffy Chen > --- > > Changes in v4: None > Changes in v3: None > Changes in v2: None > > .../bindings/sound/rockchip,rk3399-gru-sound.txt | 7

Re: [PATCH v4 2/9] ASoC: rockchip: Remove obsolete dmic-delay

On Fri, Aug 18, 2017 at 11:11:40AM +0800, Jeffy Chen wrote: > This property is no longer used. > > Signed-off-by: Jeffy Chen > --- > > Changes in v4: None > Changes in v3: None > Changes in v2: None > > .../bindings/sound/rockchip,rk3399-gru-sound.txt | 7 --- >

Re: [PATCH 4/6] dt-bindings: host1x: Fix and add Tegra186 information

On Thu, Aug 17, 2017 at 09:54:11PM +0300, Mikko Perttunen wrote: > Add note that address/size-cells should be 2 on 64-bit systems, > and add Tegra186-specific register range properties. Generally the cell sizes have nothing to do with the addressing size of the cpu. They should be as small as

Re: [PATCH 4/6] dt-bindings: host1x: Fix and add Tegra186 information

On Thu, Aug 17, 2017 at 09:54:11PM +0300, Mikko Perttunen wrote: > Add note that address/size-cells should be 2 on 64-bit systems, > and add Tegra186-specific register range properties. Generally the cell sizes have nothing to do with the addressing size of the cpu. They should be as small as

Re: [PATCH v2] KVM: nVMX: Fix trying to cancel vmlauch/vmresume

2017-08-22 7:09 GMT+08:00 Wanpeng Li : > 2017-08-22 6:55 GMT+08:00 Wanpeng Li : >> 2017-08-22 0:20 GMT+08:00 Radim Krčmář : >>> 2017-08-18 07:11-0700, Wanpeng Li: From: Wanpeng Li [

Re: [PATCH v2] KVM: nVMX: Fix trying to cancel vmlauch/vmresume

2017-08-22 7:09 GMT+08:00 Wanpeng Li : > 2017-08-22 6:55 GMT+08:00 Wanpeng Li : >> 2017-08-22 0:20 GMT+08:00 Radim Krčmář : >>> 2017-08-18 07:11-0700, Wanpeng Li: From: Wanpeng Li [ cut here ] WARNING: CPU: 7 PID: 3861 at

[PATCH net-next,4/4] hv_netvsc: Update netvsc Document for UDP hash level setting

From: Haiyang Zhang Update Documentation/networking/netvsc.txt for UDP hash level setting and related info. Signed-off-by: Haiyang Zhang --- Documentation/networking/netvsc.txt | 22 +- 1 files changed, 17 insertions(+), 5

[PATCH net-next,4/4] hv_netvsc: Update netvsc Document for UDP hash level setting

From: Haiyang Zhang Update Documentation/networking/netvsc.txt for UDP hash level setting and related info. Signed-off-by: Haiyang Zhang --- Documentation/networking/netvsc.txt | 22 +- 1 files changed, 17 insertions(+), 5 deletions(-) diff --git

[PATCH net-next,2/4] hv_netvsc: Clean up unused parameter from netvsc_get_rss_hash_opts()

From: Haiyang Zhang The parameter "nvdev" is not in use. Signed-off-by: Haiyang Zhang --- drivers/net/hyperv/netvsc_drv.c |5 ++--- 1 files changed, 2 insertions(+), 3 deletions(-) diff --git a/drivers/net/hyperv/netvsc_drv.c

[PATCH net-next,2/4] hv_netvsc: Clean up unused parameter from netvsc_get_rss_hash_opts()

From: Haiyang Zhang The parameter "nvdev" is not in use. Signed-off-by: Haiyang Zhang --- drivers/net/hyperv/netvsc_drv.c |5 ++--- 1 files changed, 2 insertions(+), 3 deletions(-) diff --git a/drivers/net/hyperv/netvsc_drv.c b/drivers/net/hyperv/netvsc_drv.c index 4677d21..d8612b1

[PATCH net-next,1/4] hv_netvsc: Clean up unused parameter from netvsc_get_hash()

From: Haiyang Zhang The parameter "sk" is not in use. Signed-off-by: Haiyang Zhang --- drivers/net/hyperv/netvsc_drv.c |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/net/hyperv/netvsc_drv.c

[PATCH net-next,1/4] hv_netvsc: Clean up unused parameter from netvsc_get_hash()

From: Haiyang Zhang The parameter "sk" is not in use. Signed-off-by: Haiyang Zhang --- drivers/net/hyperv/netvsc_drv.c |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/net/hyperv/netvsc_drv.c b/drivers/net/hyperv/netvsc_drv.c index b33f050..4677d21 100644

[PATCH net-next,3/4] hv_netvsc: Add ethtool handler to set and get UDP hash levels

From: Haiyang Zhang The patch add the functions to switch UDP hash level between L3 and L4 by ethtool command. UDP over IPv4 and v6 can be set differently. The default hash level is L4. We currently only allow switching TX hash level from within the guests. On Azure,

[PATCH net-next,3/4] hv_netvsc: Add ethtool handler to set and get UDP hash levels

From: Haiyang Zhang The patch add the functions to switch UDP hash level between L3 and L4 by ethtool command. UDP over IPv4 and v6 can be set differently. The default hash level is L4. We currently only allow switching TX hash level from within the guests. On Azure, fragmented UDP packets have

[PATCH net-next,0/4] hv_netvsc: Ethtool handler to change UDP hash levels

From: Haiyang Zhang The patch set adds the functions to switch UDP hash level between L3 and L4 by ethtool command. UDP over IPv4 and v6 can be set differently. The default hash level is L4. We currently only allow switching TX hash level from within the guests. The

[PATCH net-next,0/4] hv_netvsc: Ethtool handler to change UDP hash levels

From: Haiyang Zhang The patch set adds the functions to switch UDP hash level between L3 and L4 by ethtool command. UDP over IPv4 and v6 can be set differently. The default hash level is L4. We currently only allow switching TX hash level from within the guests. The ethtool callback function is

Re: [PATCH v5 14/16] dt-bindings: qcom_nandc: IPQ8074 QPIC NAND documentation

On Thu, Aug 17, 2017 at 05:37:52PM +0530, Abhishek Sahu wrote: > Qualcom IPQ8074 SoC uses QPIC NAND controller version 1.5.0 > which uses BAM DMA Engine. > > Signed-off-by: Abhishek Sahu > --- > > * Changes from v4: None > >

Re: [PATCH v5 14/16] dt-bindings: qcom_nandc: IPQ8074 QPIC NAND documentation

On Thu, Aug 17, 2017 at 05:37:52PM +0530, Abhishek Sahu wrote: > Qualcom IPQ8074 SoC uses QPIC NAND controller version 1.5.0 > which uses BAM DMA Engine. > > Signed-off-by: Abhishek Sahu > --- > > * Changes from v4: None > > Documentation/devicetree/bindings/mtd/qcom_nandc.txt | 2 ++ > 1

Re: [RFC 1/4] dt-bindings: clock: Add Realtek RTD1295

On Thu, Aug 17, 2017 at 01:20:22PM +0200, Andreas Färber wrote: > Naming inspired from Zidoo X9S Device Tree and clk_summary. > > Signed-off-by: Andreas Färber > --- > .../devicetree/bindings/clock/realtek,rtd129x.txt | 20 + > include/dt-bindings/clock/realtek,rtd1295.h

Re: [RFC 1/4] dt-bindings: clock: Add Realtek RTD1295

On Thu, Aug 17, 2017 at 01:20:22PM +0200, Andreas Färber wrote: > Naming inspired from Zidoo X9S Device Tree and clk_summary. > > Signed-off-by: Andreas Färber > --- > .../devicetree/bindings/clock/realtek,rtd129x.txt | 20 + > include/dt-bindings/clock/realtek,rtd1295.h| 99 >

Re: [RFC 1/3] dt-bindings: interrupt-controller: Add Realtek RTD1295

On Thu, Aug 17, 2017 at 12:11:38PM +0200, Andreas Färber wrote: > Add binding for Realtek RTD1295 IRQ mux. > > Signed-off-by: Andreas Färber > --- > .../interrupt-controller/realtek,rtd119x-mux.txt | 28 > ++ > 1 file changed, 28 insertions(+) > create

Re: [RFC 1/3] dt-bindings: interrupt-controller: Add Realtek RTD1295

On Thu, Aug 17, 2017 at 12:11:38PM +0200, Andreas Färber wrote: > Add binding for Realtek RTD1295 IRQ mux. > > Signed-off-by: Andreas Färber > --- > .../interrupt-controller/realtek,rtd119x-mux.txt | 28 > ++ > 1 file changed, 28 insertions(+) > create mode 100644 >

Re: [PATCH 1/7] dt-bindings: usb: Document the STM32F7xx DWC2 USB OTG HS core binding

On Thu, Aug 17, 2017 at 11:33:00AM +0200, Amelie Delaunay wrote: > This patch adds binding documentation for DWC2 controller in HS mode found > on STMicroelectronics STM32F7xx SoC. > > Signed-off-by: Amelie Delaunay > --- > Documentation/devicetree/bindings/usb/dwc2.txt

Re: [PATCH 1/7] dt-bindings: usb: Document the STM32F7xx DWC2 USB OTG HS core binding

On Thu, Aug 17, 2017 at 11:33:00AM +0200, Amelie Delaunay wrote: > This patch adds binding documentation for DWC2 controller in HS mode found > on STMicroelectronics STM32F7xx SoC. > > Signed-off-by: Amelie Delaunay > --- > Documentation/devicetree/bindings/usb/dwc2.txt | 2 ++ > 1 file

[PATCH v4 1/1] pwm: mediatek: add MT2712/MT7622 support

Add support to MT2712 and MT7622. Due to register offset address of pwm7 for MT2712 is not fixed 0x40, add mtk_pwm_reg_offset array for pwm register offset. Signed-off-by: Zhi Mao --- drivers/pwm/pwm-mediatek.c | 51 1 file

[PATCH v4 1/1] pwm: mediatek: add MT2712/MT7622 support

Add support to MT2712 and MT7622. Due to register offset address of pwm7 for MT2712 is not fixed 0x40, add mtk_pwm_reg_offset array for pwm register offset. Signed-off-by: Zhi Mao --- drivers/pwm/pwm-mediatek.c | 51 1 file changed, 42

[PATCH v4 0/1] pwm: mediatek: add MT2712/MT7622 support

change in v4: modify some coding style and naming of variable to make code readable. Zhi Mao (1): pwm: mediatek: add MT2712/MT7622 support drivers/pwm/pwm-mediatek.c | 51 1 file changed, 42 insertions(+), 9 deletions(-)

[PATCH v4 0/1] pwm: mediatek: add MT2712/MT7622 support

change in v4: modify some coding style and naming of variable to make code readable. Zhi Mao (1): pwm: mediatek: add MT2712/MT7622 support drivers/pwm/pwm-mediatek.c | 51 1 file changed, 42 insertions(+), 9 deletions(-)

Re: [PATCH v2] irqchip: uniphier-aidet: add UniPhier AIDET irqchip driver

Hi Mark, 2017-08-21 19:25 GMT+09:00 Marc Zyngier : >> +static struct irq_chip uniphier_aidet_irq_chip = { >> + .name = "AIDET", >> + .irq_mask = irq_chip_mask_parent, >> + .irq_unmask = irq_chip_unmask_parent, >> + .irq_eoi = irq_chip_eoi_parent, >> +

Re: [PATCH v2] irqchip: uniphier-aidet: add UniPhier AIDET irqchip driver

Hi Mark, 2017-08-21 19:25 GMT+09:00 Marc Zyngier : >> +static struct irq_chip uniphier_aidet_irq_chip = { >> + .name = "AIDET", >> + .irq_mask = irq_chip_mask_parent, >> + .irq_unmask = irq_chip_unmask_parent, >> + .irq_eoi = irq_chip_eoi_parent, >> + .irq_set_type =

Re: [PATCH v2 3/4] dt-bindings: mt8173-mtu3: add generic compatible and rename file

On Wed, Aug 16, 2017 at 02:08:12PM +0800, Chunfeng Yun wrote: > The mt8173-mtu3.txt actually holds the bindings for all mediatek > SoCs with usb3 DRD IP, so add a generic compatible and change the > name to mediatek,mtu3.txt. > > Signed-off-by: Chunfeng Yun > --- >

Re: [PATCH v2 3/4] dt-bindings: mt8173-mtu3: add generic compatible and rename file

On Wed, Aug 16, 2017 at 02:08:12PM +0800, Chunfeng Yun wrote: > The mt8173-mtu3.txt actually holds the bindings for all mediatek > SoCs with usb3 DRD IP, so add a generic compatible and change the > name to mediatek,mtu3.txt. > > Signed-off-by: Chunfeng Yun > --- > .../usb/{mt8173-mtu3.txt =>

Re: undefined reference to `_GLOBAL_OFFSET_TABLE_'

Hi Nick, On Sun, Aug 20, 2017 at 01:36:37PM +1000, Nicholas Piggin wrote: On Sun, 20 Aug 2017 08:37:36 +0800 kbuild test robot wrote: Hi Nicholas, FYI, the error/warning still remains. Still same answer as before, i.e., it seems to be this toolchain bug:

Re: undefined reference to `_GLOBAL_OFFSET_TABLE_'

Hi Nick, On Sun, Aug 20, 2017 at 01:36:37PM +1000, Nicholas Piggin wrote: On Sun, 20 Aug 2017 08:37:36 +0800 kbuild test robot wrote: Hi Nicholas, FYI, the error/warning still remains. Still same answer as before, i.e., it seems to be this toolchain bug:

linux-next: manual merge of the l2-mtd tree with the kbuild-current tree

Hi Brian, Today's linux-next merge of the l2-mtd tree got a conflict in: include/asm-generic/vmlinux.lds.h between commit: cb87481ee89d ("kbuild: linker script do not match C names unless LD_DEAD_CODE_DATA_ELIMINATION is configured") from the kbuild-current tree and commit:

linux-next: manual merge of the l2-mtd tree with the kbuild-current tree

Hi Brian, Today's linux-next merge of the l2-mtd tree got a conflict in: include/asm-generic/vmlinux.lds.h between commit: cb87481ee89d ("kbuild: linker script do not match C names unless LD_DEAD_CODE_DATA_ELIMINATION is configured") from the kbuild-current tree and commit:

[PATCH resend] timers: Fix excessive granularity of new timers after a nohz idle

When a timer base is idle, it is forwarded when a new timer is added to ensure that granularity does not become excessive. When not idle, the timer tick is expected to increment the base. However there are several problems: - If an existing timer is modified, the base is forwarded only after

[PATCH resend] timers: Fix excessive granularity of new timers after a nohz idle

When a timer base is idle, it is forwarded when a new timer is added to ensure that granularity does not become excessive. When not idle, the timer tick is expected to increment the base. However there are several problems: - If an existing timer is modified, the base is forwarded only after

RE: [PATCH] RFC: hung task: Check specific tasks for long uninterruptible sleep state

Hi, Imran, I think a "unmonitored list" is better than "monitor list", because we want khungtaskd can find out the "unexpected" hung task, but not few in a list. Then, for the fg tasks, which can put it in the "unmonitored list", for the bg tasks, I think we can tweak the timeout to control the

RE: [PATCH] RFC: hung task: Check specific tasks for long uninterruptible sleep state

Hi, Imran, I think a "unmonitored list" is better than "monitor list", because we want khungtaskd can find out the "unexpected" hung task, but not few in a list. Then, for the fg tasks, which can put it in the "unmonitored list", for the bg tasks, I think we can tweak the timeout to control the

Re: linux-next: build warnings after merge of the staging tree

Hi Mauro, On Wed, 9 Aug 2017 11:25:22 +1000 Stephen Rothwell wrote: > > On Mon, 31 Jul 2017 15:02:27 +1000 Stephen Rothwell > wrote: > > > > After merging the staging tree, today's linux-next build (x86_64 > > allmodconfig) produced this warning:

Re: linux-next: build warnings after merge of the staging tree

Hi Mauro, On Wed, 9 Aug 2017 11:25:22 +1000 Stephen Rothwell wrote: > > On Mon, 31 Jul 2017 15:02:27 +1000 Stephen Rothwell > wrote: > > > > After merging the staging tree, today's linux-next build (x86_64 > > allmodconfig) produced this warning: > > > >

Re: [PATCH v2 17/20] perf: Add a speculative page fault sw event

Anshuman Khandual writes: > On 08/18/2017 03:35 AM, Laurent Dufour wrote: >> Add a new software event to count succeeded speculative page faults. >> >> Signed-off-by: Laurent Dufour > > Should be merged with the next patch. No it

Re: [PATCH v2 17/20] perf: Add a speculative page fault sw event

Anshuman Khandual writes: > On 08/18/2017 03:35 AM, Laurent Dufour wrote: >> Add a new software event to count succeeded speculative page faults. >> >> Signed-off-by: Laurent Dufour > > Should be merged with the next patch. No it shouldn't. cheers

Re: [PATCH 1/2] powerpc/workqueue: update list of possible CPUs

Tejun Heo writes: > On Mon, Aug 21, 2017 at 03:49:50PM +0200, Laurent Vivier wrote: >> In wq_numa_init() a list of NUMA nodes with their list of possible CPUs >> is built. >> >> Unfortunately, on powerpc, the Firmware is only able to provide the >> node of a CPU if the CPU is

Re: [PATCH 1/2] powerpc/workqueue: update list of possible CPUs

Tejun Heo writes: > On Mon, Aug 21, 2017 at 03:49:50PM +0200, Laurent Vivier wrote: >> In wq_numa_init() a list of NUMA nodes with their list of possible CPUs >> is built. >> >> Unfortunately, on powerpc, the Firmware is only able to provide the >> node of a CPU if the CPU is present. So, in

[no subject]

Date: Sun, 20 Aug 2017 13:16:16 +1000 Subject: [PATCH] timers: Fix excessive granularity of new timers after a nohz idle When a timer base is idle, it is forwarded when a new timer is added to ensure that granularity does not become excessive. When not idle, the timer tick is expected to

[no subject]

Date: Sun, 20 Aug 2017 13:16:16 +1000 Subject: [PATCH] timers: Fix excessive granularity of new timers after a nohz idle When a timer base is idle, it is forwarded when a new timer is added to ensure that granularity does not become excessive. When not idle, the timer tick is expected to

Re: [PATCH v5 4/7] support user space to query RAS extension feature

Christoffer, Thanks for the review. On 2017/8/22 5:08, Christoffer Dall wrote: > On Fri, Aug 18, 2017 at 10:11:54PM +0800, Dongjiu Geng wrote: > > You should put KVM and arm64 in the subject here. I will update it in the next version. > >> In armv8.2 RAS extension, it adds virtual SError

Re: [PATCH v5 4/7] support user space to query RAS extension feature

Christoffer, Thanks for the review. On 2017/8/22 5:08, Christoffer Dall wrote: > On Fri, Aug 18, 2017 at 10:11:54PM +0800, Dongjiu Geng wrote: > > You should put KVM and arm64 in the subject here. I will update it in the next version. > >> In armv8.2 RAS extension, it adds virtual SError

Re: [PATCH] perf record: enable multiplexing scaling via -R

On Mon, Aug 21, 2017 at 05:13:29PM -0700, Stephane Eranian wrote: > On Mon, Aug 21, 2017 at 4:02 PM, Andi Kleen wrote: > > > > Stephane Eranian writes: > > > > > > To activate, the user must use: > > > $ perf record -a -R > > > > I don't know why

Re: [PATCH] perf record: enable multiplexing scaling via -R

On Mon, Aug 21, 2017 at 05:13:29PM -0700, Stephane Eranian wrote: > On Mon, Aug 21, 2017 at 4:02 PM, Andi Kleen wrote: > > > > Stephane Eranian writes: > > > > > > To activate, the user must use: > > > $ perf record -a -R > > > > I don't know why you're overloading the existing raw mode? >

linux-next: manual merge of the net-next tree with the rockchip tree

Hi all, Today's linux-next merge of the net-next tree got a conflict in: arch/arm64/boot/dts/rockchip/rk3328-evb.dts between commits: ab78718bda79 ("arm64: dts: rockchip: Enable tsadc module on RK3328 eavluation board") 1e28037ec88e ("arm64: dts: rockchip: add rk805 node for

linux-next: manual merge of the net-next tree with the rockchip tree

Hi all, Today's linux-next merge of the net-next tree got a conflict in: arch/arm64/boot/dts/rockchip/rk3328-evb.dts between commits: ab78718bda79 ("arm64: dts: rockchip: Enable tsadc module on RK3328 eavluation board") 1e28037ec88e ("arm64: dts: rockchip: add rk805 node for

[PATCH] virt/kvm avoids oops by adding parameter checking

The error parameter passed through the external interface causes the system oops. So it is necessary to increase the parameter check for all EXPORT_SYMBOL_GPL example: void kvm_get_kvm(struct kvm *kvm) { refcount_inc(>users_count); /*oops if kvm == NULL */ }

[PATCH] virt/kvm avoids oops by adding parameter checking

The error parameter passed through the external interface causes the system oops. So it is necessary to increase the parameter check for all EXPORT_SYMBOL_GPL example: void kvm_get_kvm(struct kvm *kvm) { refcount_inc(>users_count); /*oops if kvm == NULL */ }

[PATCH] virt/lib avoids oops by adding parameter checking

The error parameter passed through the external interface causes the system oops. So it is necessary to increase the parameter check for all EXPORT_SYMBOL_GPL example: int irq_bypass_register_producer(struct irq_bypass_producer *producer) { if (!producer->token) /* oops if producer ==

[PATCH] virt/lib avoids oops by adding parameter checking

The error parameter passed through the external interface causes the system oops. So it is necessary to increase the parameter check for all EXPORT_SYMBOL_GPL example: int irq_bypass_register_producer(struct irq_bypass_producer *producer) { if (!producer->token) /* oops if producer ==

Re: [PATCH v2 2/3] i2c: davinci: Add PM Runtime Support

On 08/21/2017 04:05 AM, Sekhar Nori wrote: > On Thursday 17 August 2017 03:47 AM, Franklin S Cooper Jr wrote: > >> @@ -802,7 +821,6 @@ static int davinci_i2c_probe(struct platform_device >> *pdev) >> dev->clk = devm_clk_get(>dev, NULL); >> if (IS_ERR(dev->clk)) >> return

Re: [PATCH v2 2/3] i2c: davinci: Add PM Runtime Support

On 08/21/2017 04:05 AM, Sekhar Nori wrote: > On Thursday 17 August 2017 03:47 AM, Franklin S Cooper Jr wrote: > >> @@ -802,7 +821,6 @@ static int davinci_i2c_probe(struct platform_device >> *pdev) >> dev->clk = devm_clk_get(>dev, NULL); >> if (IS_ERR(dev->clk)) >> return

Re: [PATCH 1/3] media: atmel-isc: Not support RBG format from sensor.

Hi Hans, On 2017/8/21 22:07, Hans Verkuil wrote: On 08/17/2017 09:16 AM, Wenyou Yang wrote: The 12-bit parallel interface supports the Raw Bayer, YCbCr, Monochrome and JPEG Compressed pixel formats from the external sensor, not support RBG pixel format. Signed-off-by: Wenyou Yang

Re: [PATCH 1/3] media: atmel-isc: Not support RBG format from sensor.

Hi Hans, On 2017/8/21 22:07, Hans Verkuil wrote: On 08/17/2017 09:16 AM, Wenyou Yang wrote: The 12-bit parallel interface supports the Raw Bayer, YCbCr, Monochrome and JPEG Compressed pixel formats from the external sensor, not support RBG pixel format. Signed-off-by: Wenyou Yang ---

[PATCH] HID: hid-multitouch: forward MSC_TIMESTAMP

Computes and forwards the device timestamp according to the specification. Many devices use a 16-bit timestamp field, with a resolution of 100us, therefore rolling around very frequently (every 6.5 seconds). To make sure there is no ambiguity, the timestamp reported to the input stack reset to 0

[PATCH] HID: hid-multitouch: forward MSC_TIMESTAMP

Computes and forwards the device timestamp according to the specification. Many devices use a 16-bit timestamp field, with a resolution of 100us, therefore rolling around very frequently (every 6.5 seconds). To make sure there is no ambiguity, the timestamp reported to the input stack reset to 0

Re: [PATCH v2 4/4] clk: rockchip: rv1108: fix up the clk_mac sel register description

Am Montag, 21. August 2017, 16:16:07 CEST schrieb Elaine Zhang: > cru_sel24_con[8] > rmii_extclk_sel > clock source select control register > 1'b0: from internal PLL > 1'b1: from external IO > > Signed-off-by: Elaine Zhang applied for 4.14. Thanks Heiko

Re: [PATCH v2 4/4] clk: rockchip: rv1108: fix up the clk_mac sel register description

Am Montag, 21. August 2017, 16:16:07 CEST schrieb Elaine Zhang: > cru_sel24_con[8] > rmii_extclk_sel > clock source select control register > 1'b0: from internal PLL > 1'b1: from external IO > > Signed-off-by: Elaine Zhang applied for 4.14. Thanks Heiko

Re: [PATCH v2 3/4] clk: rockchip: rv1108: rename macphy to mac

Am Montag, 21. August 2017, 16:16:06 CEST schrieb Elaine Zhang: > This MAC has no internal phy for rv1108. > > Signed-off-by: Elaine Zhang applied for 4.14 after adapting the subject and adding a sentence to the commit message that this change is safe due to gmac not

Re: [PATCH v2 3/4] clk: rockchip: rv1108: rename macphy to mac

Am Montag, 21. August 2017, 16:16:06 CEST schrieb Elaine Zhang: > This MAC has no internal phy for rv1108. > > Signed-off-by: Elaine Zhang applied for 4.14 after adapting the subject and adding a sentence to the commit message that this change is safe due to gmac not being used yet. Heiko

linux-next: manual merge of the v4l-dvb tree with the arm-soc tree

Hi all, Today's linux-next merge of the v4l-dvb tree got a conflict in: arch/arm/configs/imx_v6_v7_defconfig between commit: b834bc1c52b8 ("ARM: imx_v6_v7_defconfig: Enable staging video4linux drivers") from the arm-soc tree and commit: b9e1486e0e4b ("media: rc-core: do not depend on

linux-next: manual merge of the v4l-dvb tree with the arm-soc tree

Hi all, Today's linux-next merge of the v4l-dvb tree got a conflict in: arch/arm/configs/imx_v6_v7_defconfig between commit: b834bc1c52b8 ("ARM: imx_v6_v7_defconfig: Enable staging video4linux drivers") from the arm-soc tree and commit: b9e1486e0e4b ("media: rc-core: do not depend on

Re: [PATCH -mm -v2] mm: Clear to access sub-page last when clearing huge page

Michal Hocko writes: > On Tue 15-08-17 09:46:18, Huang, Ying wrote: >> From: Huang Ying >> >> Huge page helps to reduce TLB miss rate, but it has higher cache >> footprint, sometimes this may cause some issue. For example, when >> clearing huge page on

Re: [PATCH -mm -v2] mm: Clear to access sub-page last when clearing huge page

Michal Hocko writes: > On Tue 15-08-17 09:46:18, Huang, Ying wrote: >> From: Huang Ying >> >> Huge page helps to reduce TLB miss rate, but it has higher cache >> footprint, sometimes this may cause some issue. For example, when >> clearing huge page on x86_64 platform, the cache footprint is

Re: [PATCH v2 2/4] clk: rockchip: rv1108: add ACLK_GMAC and PCLK_GMAC clk id

Am Montag, 21. August 2017, 16:16:05 CEST schrieb Elaine Zhang: > Signed-off-by: Elaine Zhang applied for 4.14 after adapting the subject and adding a commit message Heiko

Re: [PATCH v2 2/4] clk: rockchip: rv1108: add ACLK_GMAC and PCLK_GMAC clk id

Am Montag, 21. August 2017, 16:16:05 CEST schrieb Elaine Zhang: > Signed-off-by: Elaine Zhang applied for 4.14 after adapting the subject and adding a commit message Heiko

Re: [PATCH v2 2/2] net: phy: Don't use drv when it is NULL in phy_attached_print

On 08/21/2017 07:24 AM, Andrew Lunn wrote: > On Mon, Aug 21, 2017 at 01:45:30PM +0200, Romain Perier wrote: >> Currently, if this logging function is used prior the phy driver is >> bound to the phy device (that is usually done from .ndo_open), >> 'phydev->drv' might be NULL, resulting in a kernel

Re: [PATCH v2 2/2] net: phy: Don't use drv when it is NULL in phy_attached_print

On 08/21/2017 07:24 AM, Andrew Lunn wrote: > On Mon, Aug 21, 2017 at 01:45:30PM +0200, Romain Perier wrote: >> Currently, if this logging function is used prior the phy driver is >> bound to the phy device (that is usually done from .ndo_open), >> 'phydev->drv' might be NULL, resulting in a kernel

Re: [PATCH v2 1/2] net: stmmac: Delete dead code for MDIO registration

On 08/21/2017 04:45 AM, Romain Perier wrote: > This code is no longer used, the logging function was changed by commit > fbca164776e4 ("net: stmmac: Use the right logging functi"). > > Fixes: fbca164776e4 ("net: stmmac: Use the right logging functi") > Signed-off-by: Romain Perier

Re: [PATCH v2 1/2] net: stmmac: Delete dead code for MDIO registration

On 08/21/2017 04:45 AM, Romain Perier wrote: > This code is no longer used, the logging function was changed by commit > fbca164776e4 ("net: stmmac: Use the right logging functi"). > > Fixes: fbca164776e4 ("net: stmmac: Use the right logging functi") > Signed-off-by: Romain Perier > --- >

Re: [PATCH v2 00/20] Speculative page faults

On Mon, Aug 21, 2017 at 11:58:03AM +0530, Anshuman Khandual wrote: > On 08/18/2017 03:34 AM, Laurent Dufour wrote: > > This is a port on kernel 4.13 of the work done by Peter Zijlstra to > > handle page fault without holding the mm semaphore [1]. > > > > The idea is to try to handle user space

Re: [PATCH v2 00/20] Speculative page faults

On Mon, Aug 21, 2017 at 11:58:03AM +0530, Anshuman Khandual wrote: > On 08/18/2017 03:34 AM, Laurent Dufour wrote: > > This is a port on kernel 4.13 of the work done by Peter Zijlstra to > > handle page fault without holding the mm semaphore [1]. > > > > The idea is to try to handle user space

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