Re: [PATCH 01/50] x86/boot/e820: Introduce arch/x86/include/asm/e820/types.h

* Sam Ravnborg wrote: > On Sat, Jan 28, 2017 at 11:11:22PM +0100, Ingo Molnar wrote: > > > > The plan is to keep the old UAPI header in place but the kernel won't > > use it anymore - and after some time we'll try to remove it. (User-space > > tools better have local copies

Re: [PATCH 01/50] x86/boot/e820: Introduce arch/x86/include/asm/e820/types.h

* Sam Ravnborg wrote: > On Sat, Jan 28, 2017 at 11:11:22PM +0100, Ingo Molnar wrote: > > > > The plan is to keep the old UAPI header in place but the kernel won't > > use it anymore - and after some time we'll try to remove it. (User-space > > tools better have local copies of headers anyway,

[PATCH 6/6] UDC: Add Synopsys UDC Platform driver

This patch adds platform driver support for Synopsys UDC. A new driver file (snps_udc_plat.c) is created for this purpose where the platform driver registration is done based on OF node. Currently, UDC integrated into Broadcom's iProc SoCs (Northstar2 and Cygnus) work with this driver. New

[PATCH 6/6] UDC: Add Synopsys UDC Platform driver

This patch adds platform driver support for Synopsys UDC. A new driver file (snps_udc_plat.c) is created for this purpose where the platform driver registration is done based on OF node. Currently, UDC integrated into Broadcom's iProc SoCs (Northstar2 and Cygnus) work with this driver. New

[PATCH 5/6] DT bindings documentation for Broadcom IPROC USB Device controller.

The device node is used for UDCs integrated into Broadcom's iProc family of SoCs'. The UDC is based on Synopsys Designware Cores AHB Subsystem USB Device Controller IP. Signed-off-by: Raviteja Garimella --- .../bindings/usb/brcm,iproc-snps-udc.txt | 24

[PATCH 5/6] DT bindings documentation for Broadcom IPROC USB Device controller.

The device node is used for UDCs integrated into Broadcom's iProc family of SoCs'. The UDC is based on Synopsys Designware Cores AHB Subsystem USB Device Controller IP. Signed-off-by: Raviteja Garimella --- .../bindings/usb/brcm,iproc-snps-udc.txt | 24 ++ 1 file

Re: [PATCH V2 1/2] ACPI: processor_perflib: Simplify code and stop using CPUFREQ_START

On Mon, Jan 30, 2017 at 8:07 AM, Rafael J. Wysocki wrote: > On Mon, Jan 30, 2017 at 5:29 AM, Viresh Kumar wrote: >> acpi_processor_ppc_notifier() can live without using CPUFREQ_START >> (which is gonna be removed soon), as it is only used while setting

Re: [PATCH V2 1/2] ACPI: processor_perflib: Simplify code and stop using CPUFREQ_START

On Mon, Jan 30, 2017 at 8:07 AM, Rafael J. Wysocki wrote: > On Mon, Jan 30, 2017 at 5:29 AM, Viresh Kumar wrote: >> acpi_processor_ppc_notifier() can live without using CPUFREQ_START >> (which is gonna be removed soon), as it is only used while setting >> ignore_ppc to 0. This can be done with

Re: mm, vmscan: commit makes PAE kernel crash nightly (bisected)

On Sun 29-01-17 16:50:03, Trevor Cordes wrote: > On 2017-01-25 Michal Hocko wrote: > > On Wed 25-01-17 04:02:46, Trevor Cordes wrote: > > > OK, I patched & compiled mhocko's git tree from the other day > > > 4.9.0+. (To confirm, weird, but mhocko's git tree I'm using from a > > > couple of weeks

Re: mm, vmscan: commit makes PAE kernel crash nightly (bisected)

On Sun 29-01-17 16:50:03, Trevor Cordes wrote: > On 2017-01-25 Michal Hocko wrote: > > On Wed 25-01-17 04:02:46, Trevor Cordes wrote: > > > OK, I patched & compiled mhocko's git tree from the other day > > > 4.9.0+. (To confirm, weird, but mhocko's git tree I'm using from a > > > couple of weeks

Re: [PATCH v5 07/11] pwm: imx: Provide atomic PWM support for i.MX PWMv2

On Sun, 29 Jan 2017 22:54:11 +0100 Lukasz Majewski wrote: > This commit provides apply() callback implementation for i.MX's PWMv2. > > Suggested-by: Stefan Agner > Suggested-by: Boris Brezillon > Signed-off-by: Lukasz

Re: [PATCH v5 07/11] pwm: imx: Provide atomic PWM support for i.MX PWMv2

On Sun, 29 Jan 2017 22:54:11 +0100 Lukasz Majewski wrote: > This commit provides apply() callback implementation for i.MX's PWMv2. > > Suggested-by: Stefan Agner > Suggested-by: Boris Brezillon > Signed-off-by: Lukasz Majewski > Reviewed-by: Boris Brezillon > --- > Changes for v5: > -

Re: [RFC PATCH] scsi, block: fix duplicate bdi name registration crashes

On Sun, Jan 29, 2017 at 11:22 PM, Omar Sandoval wrote: > On Mon, Jan 30, 2017 at 08:05:52AM +0100, Hannes Reinecke wrote: >> On 01/29/2017 05:58 AM, Dan Williams wrote: >> > Warnings of the following form occur because scsi reuses a devt number >> > while the block layer

Re: [PATCH v2 1/2] nvmem: sunxi-sid: add support for H3 and A64's SID controller

On Sun, Jan 29, 2017 at 09:56:40AM +0800, Icenowy Zheng wrote: > H3 and A64 SoCs have a bigger SID controller, which has its direct read > address at 0x200 position in the SID block, not 0x0. > > Also, H3 SID controller has some silicon bug that makes the direct read > value wrong at first, add

Re: [RFC PATCH] scsi, block: fix duplicate bdi name registration crashes

On Sun, Jan 29, 2017 at 11:22 PM, Omar Sandoval wrote: > On Mon, Jan 30, 2017 at 08:05:52AM +0100, Hannes Reinecke wrote: >> On 01/29/2017 05:58 AM, Dan Williams wrote: >> > Warnings of the following form occur because scsi reuses a devt number >> > while the block layer still has it referenced

Re: [PATCH v2 1/2] nvmem: sunxi-sid: add support for H3 and A64's SID controller

On Sun, Jan 29, 2017 at 09:56:40AM +0800, Icenowy Zheng wrote: > H3 and A64 SoCs have a bigger SID controller, which has its direct read > address at 0x200 position in the SID block, not 0x0. > > Also, H3 SID controller has some silicon bug that makes the direct read > value wrong at first, add

Re: [PATCH v5 03/11] pwm: imx: Add separate set of pwm ops for PWMv1 and PWMv2

On Mon, Jan 30, 2017 at 08:23:12AM +0100, Thierry Reding wrote: > On Sun, Jan 29, 2017 at 10:54:07PM +0100, Lukasz Majewski wrote: > > From: Lukasz Majewski > > > > This patch provides separate set of pwm ops utilized by > > i.MX's PWMv1 and PWMv2. > > > > Signed-off-by:

Re: [PATCH v5 03/11] pwm: imx: Add separate set of pwm ops for PWMv1 and PWMv2

On Mon, Jan 30, 2017 at 08:23:12AM +0100, Thierry Reding wrote: > On Sun, Jan 29, 2017 at 10:54:07PM +0100, Lukasz Majewski wrote: > > From: Lukasz Majewski > > > > This patch provides separate set of pwm ops utilized by > > i.MX's PWMv1 and PWMv2. > > > > Signed-off-by: Lothar Waßmann > >

Re: [PATCH v2 00/10] clk: sunxi-ng: Add support for A80 CCUs

Hi, On Sat, Jan 28, 2017 at 08:22:29PM +0800, Chen-Yu Tsai wrote: > Hi everyone, > > This is v2 of my A80 CCU clk patches. Changes since v1: > > - Use pre-divider adjusted parent rate for rounding. > > - Use else statement for the case where the PLL lock status bit is > in same

Re: [PATCH v2 00/10] clk: sunxi-ng: Add support for A80 CCUs

Hi, On Sat, Jan 28, 2017 at 08:22:29PM +0800, Chen-Yu Tsai wrote: > Hi everyone, > > This is v2 of my A80 CCU clk patches. Changes since v1: > > - Use pre-divider adjusted parent rate for rounding. > > - Use else statement for the case where the PLL lock status bit is > in same

RE: [PATCH v2 1/2] PCI: Xilinx NWL: Modifying irq chip for legacy interrupts

> The subject line is not very descriptive. How about "Enforce level > triggering for legacy interrupts"? > > On 25/01/17 08:52, Bharat Kumar Gogada wrote: > > - Few wifi end points which only support legacy interrupts, > > performs hardware reset functionalities after disabling interrupts > > by

RE: [PATCH v2 1/2] PCI: Xilinx NWL: Modifying irq chip for legacy interrupts

> The subject line is not very descriptive. How about "Enforce level > triggering for legacy interrupts"? > > On 25/01/17 08:52, Bharat Kumar Gogada wrote: > > - Few wifi end points which only support legacy interrupts, > > performs hardware reset functionalities after disabling interrupts > > by

Re: [RFC PATCH] scsi, block: fix duplicate bdi name registration crashes

On Mon, Jan 30, 2017 at 08:05:52AM +0100, Hannes Reinecke wrote: > On 01/29/2017 05:58 AM, Dan Williams wrote: > > Warnings of the following form occur because scsi reuses a devt number > > while the block layer still has it referenced as the name of the bdi > > [1]: > > > > WARNING: CPU: 1 PID:

Re: [RFC PATCH] scsi, block: fix duplicate bdi name registration crashes

On Mon, Jan 30, 2017 at 08:05:52AM +0100, Hannes Reinecke wrote: > On 01/29/2017 05:58 AM, Dan Williams wrote: > > Warnings of the following form occur because scsi reuses a devt number > > while the block layer still has it referenced as the name of the bdi > > [1]: > > > > WARNING: CPU: 1 PID:

scsi: use-after-free in sg_start_req

Hello, The following program triggers use-after-free in sg_start_req: https://gist.githubusercontent.com/dvyukov/be6561d2819fe30a78711234e53866b8/raw/1d75d4508f7a8ebb0b1ec0d18c0054fbffbc0708/gistfile1.txt BUG: KASAN: use-after-free in bio_copy_user_iov+0xee1/0xf00 block/bio.c:1248 at addr

scsi: use-after-free in sg_start_req

Hello, The following program triggers use-after-free in sg_start_req: https://gist.githubusercontent.com/dvyukov/be6561d2819fe30a78711234e53866b8/raw/1d75d4508f7a8ebb0b1ec0d18c0054fbffbc0708/gistfile1.txt BUG: KASAN: use-after-free in bio_copy_user_iov+0xee1/0xf00 block/bio.c:1248 at addr

Re: [PATCH v5 05/11] pwm: imx: Move PWMv2 software reset code to a separate function

On Sun, Jan 29, 2017 at 10:54:09PM +0100, Lukasz Majewski wrote: > From: Lukasz Majewski > > The software reset code has been extracted from imx_pwm_config_v2 function > and moved to new one - imx_pwm_sw_reset(). > > This change reduces the overall size of

Re: [PATCH v5 05/11] pwm: imx: Move PWMv2 software reset code to a separate function

On Sun, Jan 29, 2017 at 10:54:09PM +0100, Lukasz Majewski wrote: > From: Lukasz Majewski > > The software reset code has been extracted from imx_pwm_config_v2 function > and moved to new one - imx_pwm_sw_reset(). > > This change reduces the overall size of imx_pwm_config_v2() and prepares > it

Re: [PATCH v5 03/11] pwm: imx: Add separate set of pwm ops for PWMv1 and PWMv2

On Sun, Jan 29, 2017 at 10:54:07PM +0100, Lukasz Majewski wrote: > From: Lukasz Majewski > > This patch provides separate set of pwm ops utilized by > i.MX's PWMv1 and PWMv2. > > Signed-off-by: Lothar Waßmann > Signed-off-by: Bhuvanchandra DV

Re: [PATCH v5 03/11] pwm: imx: Add separate set of pwm ops for PWMv1 and PWMv2

On Sun, Jan 29, 2017 at 10:54:07PM +0100, Lukasz Majewski wrote: > From: Lukasz Majewski > > This patch provides separate set of pwm ops utilized by > i.MX's PWMv1 and PWMv2. > > Signed-off-by: Lothar Waßmann > Signed-off-by: Bhuvanchandra DV > Signed-off-by: Lukasz Majewski > Acked-by:

Re: [PATCH v5 2/8] PCI: Allow runtime PM on Thunderbolt ports

On Sat, Jan 28, 2017 at 11:09 PM, Bjorn Helgaas wrote: > On Sun, Jan 15, 2017 at 09:03:45PM +0100, Lukas Wunner wrote: >> Currently PCIe ports are only allowed to go to D3 if the BIOS is dated >> 2015 or newer to avoid potential issues with old chipsets. However for >>

Re: [PATCH v5 2/8] PCI: Allow runtime PM on Thunderbolt ports

On Sat, Jan 28, 2017 at 11:09 PM, Bjorn Helgaas wrote: > On Sun, Jan 15, 2017 at 09:03:45PM +0100, Lukas Wunner wrote: >> Currently PCIe ports are only allowed to go to D3 if the BIOS is dated >> 2015 or newer to avoid potential issues with old chipsets. However for >> Thunderbolt we know that

Re: [PATCH V2 1/2] ACPI: processor_perflib: Simplify code and stop using CPUFREQ_START

On Mon, Jan 30, 2017 at 5:29 AM, Viresh Kumar wrote: > acpi_processor_ppc_notifier() can live without using CPUFREQ_START > (which is gonna be removed soon), as it is only used while setting > ignore_ppc to 0. This can be done with the help of "ignore_ppc < 0" > check

Re: [PATCH V2 1/2] ACPI: processor_perflib: Simplify code and stop using CPUFREQ_START

On Mon, Jan 30, 2017 at 5:29 AM, Viresh Kumar wrote: > acpi_processor_ppc_notifier() can live without using CPUFREQ_START > (which is gonna be removed soon), as it is only used while setting > ignore_ppc to 0. This can be done with the help of "ignore_ppc < 0" > check alone. The notifier function

Re: [PATCH] Usb: host - Fix possible NULL derefrence.

On Mon, Jan 30, 2017 at 07:45:21AM +0100, Greg Kroah-Hartman wrote: > On Mon, Jan 30, 2017 at 10:36:29AM +0530, Shailendra Verma wrote: > > of_device_get_match_data could return NULL, and so can cause > > a NULL pointer dereference later. > > > > Signed-off-by: Shailendra Verma

Re: [PATCH] I2c: busses - Fix possible NULL derefrence.

On Mon, Jan 30, 2017 at 10:33:07AM +0530, Shailendra Verma wrote: > of_device_get_match_data could return NULL, and so can cause > a NULL pointer dereference later. > > Signed-off-by: Shailendra Verma > --- > drivers/i2c/busses/i2c-tegra.c |4 > 1 file

Re: [PATCH] Usb: host - Fix possible NULL derefrence.

On Mon, Jan 30, 2017 at 07:45:21AM +0100, Greg Kroah-Hartman wrote: > On Mon, Jan 30, 2017 at 10:36:29AM +0530, Shailendra Verma wrote: > > of_device_get_match_data could return NULL, and so can cause > > a NULL pointer dereference later. > > > > Signed-off-by: Shailendra Verma > > --- > >

Re: [PATCH] I2c: busses - Fix possible NULL derefrence.

On Mon, Jan 30, 2017 at 10:33:07AM +0530, Shailendra Verma wrote: > of_device_get_match_data could return NULL, and so can cause > a NULL pointer dereference later. > > Signed-off-by: Shailendra Verma > --- > drivers/i2c/busses/i2c-tegra.c |4 > 1 file changed, 4 insertions(+) This

Re: [PATCH v6 3/5] cpuidle:powernv: Add helper function to populate powernv idle states.

On Mon, Jan 30, 2017 at 4:47 AM, Michael Ellerman wrote: > "Gautham R. Shenoy" writes: > >> From: "Gautham R. Shenoy" >> >> In the current code for powernv_add_idle_states, there is a lot of code >> duplication while

Re: [PATCH v6 3/5] cpuidle:powernv: Add helper function to populate powernv idle states.

On Mon, Jan 30, 2017 at 4:47 AM, Michael Ellerman wrote: > "Gautham R. Shenoy" writes: > >> From: "Gautham R. Shenoy" >> >> In the current code for powernv_add_idle_states, there is a lot of code >> duplication while initializing an idle state in powernv_states table. >> >> Add an inline helper

Re: [PATCH] Gpu: drm: tegra - Fix possible NULL derefrence.

On Mon, Jan 30, 2017 at 10:23:45AM +0530, Shailendra Verma wrote: > of_match_device could return NULL, and so can cause a NULL > pointer dereference later. > > Signed-off-by: Shailendra Verma > --- > drivers/gpu/drm/tegra/sor.c |4 > 1 file changed, 4

Re: [PATCH] Gpu: drm: tegra - Fix possible NULL derefrence.

On Mon, Jan 30, 2017 at 10:23:45AM +0530, Shailendra Verma wrote: > of_match_device could return NULL, and so can cause a NULL > pointer dereference later. > > Signed-off-by: Shailendra Verma > --- > drivers/gpu/drm/tegra/sor.c |4 > 1 file changed, 4 insertions(+) No, this will never

Re: [PATCH] pwm - Fix possible NULL derefrence.

On Mon, Jan 30, 2017 at 10:22:33AM +0530, Shailendra Verma wrote: > of_match_device could return NULL, and so can cause a NULL > pointer dereference later. > > Signed-off-by: Shailendra Verma > --- > drivers/pwm/pwm-sun4i.c |4 > drivers/pwm/pwm-tegra.c |5

Re: [PATCH] pwm - Fix possible NULL derefrence.

On Mon, Jan 30, 2017 at 10:22:33AM +0530, Shailendra Verma wrote: > of_match_device could return NULL, and so can cause a NULL > pointer dereference later. > > Signed-off-by: Shailendra Verma > --- > drivers/pwm/pwm-sun4i.c |4 > drivers/pwm/pwm-tegra.c |5 + > 2 files changed,

Re: [RFC PATCH] scsi, block: fix duplicate bdi name registration crashes

On 01/29/2017 05:58 AM, Dan Williams wrote: > Warnings of the following form occur because scsi reuses a devt number > while the block layer still has it referenced as the name of the bdi > [1]: > > WARNING: CPU: 1 PID: 93 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x62/0x80 > sysfs: cannot create

Re: [RFC PATCH] scsi, block: fix duplicate bdi name registration crashes

On 01/29/2017 05:58 AM, Dan Williams wrote: > Warnings of the following form occur because scsi reuses a devt number > while the block layer still has it referenced as the name of the bdi > [1]: > > WARNING: CPU: 1 PID: 93 at fs/sysfs/dir.c:31 sysfs_warn_dup+0x62/0x80 > sysfs: cannot create

linux-next: Tree for Jan 30

Hi all, There will be no linux-next release until Monday (next-20170130). Changes since 20170125: New tree: spi-nor The drm tree lost its build failure. The block tree gained a build failure so I used the version from next-20170125. The tip tree gained a conflict against the drm-misc-fixes

linux-next: Tree for Jan 30

Hi all, There will be no linux-next release until Monday (next-20170130). Changes since 20170125: New tree: spi-nor The drm tree lost its build failure. The block tree gained a build failure so I used the version from next-20170125. The tip tree gained a conflict against the drm-misc-fixes

Re: [GIT PULL 4/4] arm64: dts: exynos: for v4.11, 2nd round

On Mon, Jan 30, 2017 at 7:23 AM, Olof Johansson wrote: > Hi Krzysztof, > > On Sun, Jan 29, 2017 at 10:06:29PM +0200, Krzysztof Kozlowski wrote: >> Hi, >> >> On top of previous pull request. >> >> This adds proper clocks to LPASS node on Exynos5433 which is needed >> by Marek's

Re: [PATCH] Usb: host - Fix possible NULL derefrence.

On Mon, Jan 30, 2017 at 10:36:29AM +0530, Shailendra Verma wrote: > of_device_get_match_data could return NULL, and so can cause > a NULL pointer dereference later. > > Signed-off-by: Shailendra Verma > --- > drivers/usb/host/xhci-tegra.c |4 > 1 file changed,

Re: [GIT PULL 4/4] arm64: dts: exynos: for v4.11, 2nd round

On Mon, Jan 30, 2017 at 7:23 AM, Olof Johansson wrote: > Hi Krzysztof, > > On Sun, Jan 29, 2017 at 10:06:29PM +0200, Krzysztof Kozlowski wrote: >> Hi, >> >> On top of previous pull request. >> >> This adds proper clocks to LPASS node on Exynos5433 which is needed >> by Marek's patchset: >> -

Re: [PATCH] Usb: host - Fix possible NULL derefrence.

On Mon, Jan 30, 2017 at 10:36:29AM +0530, Shailendra Verma wrote: > of_device_get_match_data could return NULL, and so can cause > a NULL pointer dereference later. > > Signed-off-by: Shailendra Verma > --- > drivers/usb/host/xhci-tegra.c |4 > 1 file changed, 4 insertions(+) > > diff

Re: linux-next: Tree for Jan 30

Hi all, On Mon, 30 Jan 2017 17:49:01 +1100 Stephen Rothwell wrote: > > There will be no linux-next release until Monday (next-20170130). Obviously, this is not longer relevant :-) -- Cheers, Stephen Rothwell

Re: linux-next: Tree for Jan 30

Hi all, On Mon, 30 Jan 2017 17:49:01 +1100 Stephen Rothwell wrote: > > There will be no linux-next release until Monday (next-20170130). Obviously, this is not longer relevant :-) -- Cheers, Stephen Rothwell

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

On Sun, Jan 29, 2017 at 06:53:42PM -0700, Jens Axboe wrote: > Huh, I wonder how that snuck past my allmodconfig builds, that looks > like a clear failure. I also did tons of test builds and never saw it, not sure why the NVMe-SCSI code still someone how an implicit include of scsi_cmnd.h. But in

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

On Sun, Jan 29, 2017 at 06:53:42PM -0700, Jens Axboe wrote: > Huh, I wonder how that snuck past my allmodconfig builds, that looks > like a clear failure. I also did tons of test builds and never saw it, not sure why the NVMe-SCSI code still someone how an implicit include of scsi_cmnd.h. But in

Re: [GIT PULL] STi DT update for v4.11 round 2

On Fri, Jan 27, 2017 at 05:15:32PM +, Patrice CHOTARD wrote: > Here is the correct one > > PLease consider this second round of STi dts update for v4.11 : > > The following changes since commit 2016ead446b98c42dffd9b6c03ce813e5cb3b810: > >ARM: dts: STiH407-family: Supply Mailbox

Re: [GIT PULL] STi DT update for v4.11 round 2

On Fri, Jan 27, 2017 at 05:15:32PM +, Patrice CHOTARD wrote: > Here is the correct one > > PLease consider this second round of STi dts update for v4.11 : > > The following changes since commit 2016ead446b98c42dffd9b6c03ce813e5cb3b810: > >ARM: dts: STiH407-family: Supply Mailbox

Re: [PATCH 0/8] staging: lustre: lnet: change wire protocol typedefs to proper structure

On Sun, Jan 29, 2017 at 11:56:38PM +, James Simmons wrote: > > > On Sat, 2017-01-21 at 19:40 -0500, James Simmons wrote: > > > The upstream kernel requires proper structures so > > > convert nearly all the LNet wire protocols typedefs in > > > the LNet core. > > > > Thanks. > > > > Perhaps

Re: [PATCH 0/8] staging: lustre: lnet: change wire protocol typedefs to proper structure

On Sun, Jan 29, 2017 at 11:56:38PM +, James Simmons wrote: > > > On Sat, 2017-01-21 at 19:40 -0500, James Simmons wrote: > > > The upstream kernel requires proper structures so > > > convert nearly all the LNet wire protocols typedefs in > > > the LNet core. > > > > Thanks. > > > > Perhaps

Re: Exynos5422 EHCI (USB 2.0) - Odroid XU4 - port 1 resume error -110

Hi Krzysztof, On 29 January 2017 at 19:05, Krzysztof Kozlowski wrote: > Hi, > > On Odroid XU4 with an external usb2514 hub (evaluation board from SMSC > or TI) connected to the USB2.0 port of EHCI controller, whenever I > plug some USB device into the usb2514 hub I see errors

Re: Exynos5422 EHCI (USB 2.0) - Odroid XU4 - port 1 resume error -110

Hi Krzysztof, On 29 January 2017 at 19:05, Krzysztof Kozlowski wrote: > Hi, > > On Odroid XU4 with an external usb2514 hub (evaluation board from SMSC > or TI) connected to the USB2.0 port of EHCI controller, whenever I > plug some USB device into the usb2514 hub I see errors like: > [

RE: [PATCH v2 2/2] PCI: Xilinx NWL: Fix, proc interrupts for legacy virtual irq shown as edge

> > On 25/01/17 08:52, Bharat Kumar Gogada wrote: > > - Legacy interrupts are level triggered, virtual irq line of End Point > > shows as edge in /proc/interrupts. > > - Setting irq flags of virtual irq line of EP to level triggered at > > the time of mapping. > > > > Signed-off-by: Bharat Kumar

RE: [PATCH v2 2/2] PCI: Xilinx NWL: Fix, proc interrupts for legacy virtual irq shown as edge

> > On 25/01/17 08:52, Bharat Kumar Gogada wrote: > > - Legacy interrupts are level triggered, virtual irq line of End Point > > shows as edge in /proc/interrupts. > > - Setting irq flags of virtual irq line of EP to level triggered at > > the time of mapping. > > > > Signed-off-by: Bharat Kumar

[RFC V2 12/12] mm: Tag VMA with VM_CDM flag explicitly during mbind(MPOL_BIND)

Mark all the applicable VMAs with VM_CDM explicitly during mbind(MPOL_BIND) call if the user provided nodemask has a CDM node. Signed-off-by: Anshuman Khandual --- mm/mempolicy.c | 17 + 1 file changed, 17 insertions(+) diff --git a/mm/mempolicy.c

[RFC V2 12/12] mm: Tag VMA with VM_CDM flag explicitly during mbind(MPOL_BIND)

Mark all the applicable VMAs with VM_CDM explicitly during mbind(MPOL_BIND) call if the user provided nodemask has a CDM node. Signed-off-by: Anshuman Khandual --- mm/mempolicy.c | 17 + 1 file changed, 17 insertions(+) diff --git a/mm/mempolicy.c b/mm/mempolicy.c index

[RFC V2 09/12] mm: Exclude CDM marked VMAs from auto NUMA

Kernel cannot track device memory accesses behind VMAs containing CDM memory. Hence all the VM_CDM marked VMAs should not be part of the auto NUMA migration scheme. This patch also adds a new function is_cdm_vma() to detect any VMA marked with flag VM_CDM. Signed-off-by: Anshuman Khandual

[RFC V2 09/12] mm: Exclude CDM marked VMAs from auto NUMA

Kernel cannot track device memory accesses behind VMAs containing CDM memory. Hence all the VM_CDM marked VMAs should not be part of the auto NUMA migration scheme. This patch also adds a new function is_cdm_vma() to detect any VMA marked with flag VM_CDM. Signed-off-by: Anshuman Khandual ---

[PATCH] Pinctrl: mvebu - Fix possible NULL derefrence.

of_match_device could return NULL, and so can cause a NULL pointer dereference later. Signed-off-by: Shailendra Verma --- drivers/pinctrl/mvebu/pinctrl-dove.c |4 drivers/pinctrl/mvebu/pinctrl-kirkwood.c |4 drivers/pinctrl/mvebu/pinctrl-orion.c

[PATCH] Pinctrl: mvebu - Fix possible NULL derefrence.

of_match_device could return NULL, and so can cause a NULL pointer dereference later. Signed-off-by: Shailendra Verma --- drivers/pinctrl/mvebu/pinctrl-dove.c |4 drivers/pinctrl/mvebu/pinctrl-kirkwood.c |4 drivers/pinctrl/mvebu/pinctrl-orion.c|4 3 files

Re: [PATCH v7 00/20] ILP32 for ARM64

On Mon, Jan 09, 2017 at 04:59:37PM +0530, Yury Norov wrote: > This series enables aarch64 with ilp32 mode. > > As supporting work, it introduces ARCH_32BIT_OFF_T configuration > option that is enabled for existing 32-bit architectures but disabled > for new arches (so 64-bit off_t is is used by

Re: [PATCH v7 00/20] ILP32 for ARM64

On Mon, Jan 09, 2017 at 04:59:37PM +0530, Yury Norov wrote: > This series enables aarch64 with ilp32 mode. > > As supporting work, it introduces ARCH_32BIT_OFF_T configuration > option that is enabled for existing 32-bit architectures but disabled > for new arches (so 64-bit off_t is is used by

[RFC 1/6] mm: add wrap for page accouting index

We calculate page/lru accouting index with checking if the page/lru is file. This will be a problem when we introduce a new LRU list. So add a wrap for the calculation. The patch is based on Minchan's previous patch. Cc: Michal Hocko Cc: Minchan Kim Cc:

[RFC 1/6] mm: add wrap for page accouting index

We calculate page/lru accouting index with checking if the page/lru is file. This will be a problem when we introduce a new LRU list. So add a wrap for the calculation. The patch is based on Minchan's previous patch. Cc: Michal Hocko Cc: Minchan Kim Cc: Hugh Dickins Cc: Johannes Weiner Cc:

[RFC 4/6] mm: move MADV_FREE pages into LRU_LAZYFREE list

Move the MADV_FREE pages into LRU_LAZYFREE list. The reason why we need to do this is described in last patch. Next patch will reclaim the pages. The patch is based on Minchan's previous patch. Cc: Michal Hocko Cc: Minchan Kim Cc: Hugh Dickins

[RFC 6/6] mm: enable MADV_FREE for swapless system

Now MADV_FREE pages can be easily reclaimed even for swapless system. We can safely enable MADV_FREE for all systems. Cc: Michal Hocko Cc: Minchan Kim Cc: Hugh Dickins Cc: Johannes Weiner Cc: Rik van Riel

[RFC 4/6] mm: move MADV_FREE pages into LRU_LAZYFREE list

Move the MADV_FREE pages into LRU_LAZYFREE list. The reason why we need to do this is described in last patch. Next patch will reclaim the pages. The patch is based on Minchan's previous patch. Cc: Michal Hocko Cc: Minchan Kim Cc: Hugh Dickins Cc: Johannes Weiner Cc: Rik van Riel Cc: Mel

[RFC 6/6] mm: enable MADV_FREE for swapless system

Now MADV_FREE pages can be easily reclaimed even for swapless system. We can safely enable MADV_FREE for all systems. Cc: Michal Hocko Cc: Minchan Kim Cc: Hugh Dickins Cc: Johannes Weiner Cc: Rik van Riel Cc: Mel Gorman Signed-off-by: Shaohua Li --- mm/madvise.c | 8 +--- 1 file

[RFC 5/6] mm: reclaim lazyfree pages

When memory pressure is high, we must free lazyfree pages. If we free lazyfree pages, the cost reaccessing the pages is a page fault and page allocation. The cost is much lower than swapin a page or refill a file page cache because refilling anon/file page includes the same cost plus extra IO

[RFC 3/6] mm: add LRU_LAZYFREE lru list

MADV_FREE pages are in anonymous LRU list currently, there are several problems: - Doesn't support system without swap enabled. Because if swap is off, we can't or can't efficiently age anonymous pages. And since MADV_FREE pages are mixed with other anonymous pages, we can't reclaim MADV_FREE

[RFC 2/6] mm: add lazyfree page flag

We are going to add MADV_FREE pages into a new LRU list. Add a new flag to indicate such pages. Note, we are reusing PG_mappedtodisk for the new flag. This is ok because no anonymous pages have this flag set. The patch is based on Minchan's previous patch. Cc: Michal Hocko Cc:

[RFC 5/6] mm: reclaim lazyfree pages

When memory pressure is high, we must free lazyfree pages. If we free lazyfree pages, the cost reaccessing the pages is a page fault and page allocation. The cost is much lower than swapin a page or refill a file page cache because refilling anon/file page includes the same cost plus extra IO

[RFC 3/6] mm: add LRU_LAZYFREE lru list

MADV_FREE pages are in anonymous LRU list currently, there are several problems: - Doesn't support system without swap enabled. Because if swap is off, we can't or can't efficiently age anonymous pages. And since MADV_FREE pages are mixed with other anonymous pages, we can't reclaim MADV_FREE

[RFC 2/6] mm: add lazyfree page flag

We are going to add MADV_FREE pages into a new LRU list. Add a new flag to indicate such pages. Note, we are reusing PG_mappedtodisk for the new flag. This is ok because no anonymous pages have this flag set. The patch is based on Minchan's previous patch. Cc: Michal Hocko Cc: Minchan Kim Cc:

[RFC 0/6]mm: add new LRU list for MADV_FREE pages

Hi, We are trying to use MADV_FREE in jemalloc. Several issues are found. Without solving the issues, jemalloc can't use the MADV_FREE feature. - Doesn't support system without swap enabled. Because if swap is off, we can't or can't efficiently age anonymous pages. And since MADV_FREE pages are

[RFC 0/6]mm: add new LRU list for MADV_FREE pages

Hi, We are trying to use MADV_FREE in jemalloc. Several issues are found. Without solving the issues, jemalloc can't use the MADV_FREE feature. - Doesn't support system without swap enabled. Because if swap is off, we can't or can't efficiently age anonymous pages. And since MADV_FREE pages are

Re: [GIT PULL] STi DT fix for v4.10-rcs???

On Fri, Jan 27, 2017 at 04:10:10PM +, Patrice CHOTARD wrote: > Hi Arnd, Olof, Kevin > > Please consider this set for inclusion into the next v4.10-rc. > > The following changes since commit 7ce7d89f48834cefece7804d38fc5d85382edf77: > >Linux 4.10-rc1 (2016-12-25 16:13:08 -0800) > > are

Re: [GIT PULL] STi DT fix for v4.10-rcs???

On Fri, Jan 27, 2017 at 04:10:10PM +, Patrice CHOTARD wrote: > Hi Arnd, Olof, Kevin > > Please consider this set for inclusion into the next v4.10-rc. > > The following changes since commit 7ce7d89f48834cefece7804d38fc5d85382edf77: > >Linux 4.10-rc1 (2016-12-25 16:13:08 -0800) > > are

Re: [GIT PULL 2/4] soc: samsung: exynos for v4.11, 2nd round

On Sun, Jan 29, 2017 at 10:06:27PM +0200, Krzysztof Kozlowski wrote: > Hi, > > On top of previous pull request (tags/samsung-drivers-soc-pmu-4.11). > > This adds support for Exynos5433 to PMU driver which is needed > by Marek's patchset: > - [PATCH v2 0/8] Pad retentions support for Exynos5433

Re: [GIT PULL] ARM: at91: drivers for 4.11 #2

On Sat, Jan 28, 2017 at 01:45:10AM +0100, Alexandre Belloni wrote: > Arnd, Olof > > The EBI was requiring more fixing than expected in preparation of the > NAND driver rework for 4.12. > > The following changes since commit ee194289502a6901cc77dc9a893bf2afd351ac5e: > > memory/atmel-ebi: Fix

Re: [GIT PULL 2/4] soc: samsung: exynos for v4.11, 2nd round

On Sun, Jan 29, 2017 at 10:06:27PM +0200, Krzysztof Kozlowski wrote: > Hi, > > On top of previous pull request (tags/samsung-drivers-soc-pmu-4.11). > > This adds support for Exynos5433 to PMU driver which is needed > by Marek's patchset: > - [PATCH v2 0/8] Pad retentions support for Exynos5433

Re: [GIT PULL] ARM: at91: drivers for 4.11 #2

On Sat, Jan 28, 2017 at 01:45:10AM +0100, Alexandre Belloni wrote: > Arnd, Olof > > The EBI was requiring more fixing than expected in preparation of the > NAND driver rework for 4.12. > > The following changes since commit ee194289502a6901cc77dc9a893bf2afd351ac5e: > > memory/atmel-ebi: Fix

Re: [RESEND PATCH 0/2] arm64: defconfig: enable some NAND config symbols

On Mon, Jan 30, 2017 at 10:55:45AM +0900, Masahiro Yamada wrote: > I am resending this series to a...@kernel.org > as requested by Olof Johansson. > > No code change since the previous post. > > > > Masahiro Yamada (2): > arm64: defconfig: enable CONFIG_MTD_BLOCK > arm64: defconfig: enable

Re: [RESEND PATCH 0/2] arm64: defconfig: enable some NAND config symbols

On Mon, Jan 30, 2017 at 10:55:45AM +0900, Masahiro Yamada wrote: > I am resending this series to a...@kernel.org > as requested by Olof Johansson. > > No code change since the previous post. > > > > Masahiro Yamada (2): > arm64: defconfig: enable CONFIG_MTD_BLOCK > arm64: defconfig: enable

Re: [GIT PULL 1/4] ARM: mach/soc: exynos for v4.11, 2nd round

On Sun, Jan 29, 2017 at 10:06:30PM +0200, Krzysztof Kozlowski wrote: > > On top of previous pull request. > > > The following changes since commit cda1a52dab50340728e46601e6c9da9fc4beaf1f: > > ARM: s3c64xx: Constify wake_irqs (2016-12-29 15:41:44 +0200) > > are available in the git

Re: [GIT PULL 4/4] arm64: dts: exynos: for v4.11, 2nd round

Hi Krzysztof, On Sun, Jan 29, 2017 at 10:06:29PM +0200, Krzysztof Kozlowski wrote: > Hi, > > On top of previous pull request. > > This adds proper clocks to LPASS node on Exynos5433 which is needed > by Marek's patchset: > - [PATCH v2 0/8] Pad retentions support for Exynos5433 >

Re: [PATCH 0/2] xen/net: limit number of tx/rx queues

On 01/10/2017 08:32 AM, Juergen Gross wrote: The Xen network frontend/backend supports multiple tx/rx queues for one virtual interface. The number of queues supported by the backend is set to the number of cpus of the backend driver domain (usually dom0) and the number of queues requested by

Re: [GIT PULL 1/4] ARM: mach/soc: exynos for v4.11, 2nd round

On Sun, Jan 29, 2017 at 10:06:30PM +0200, Krzysztof Kozlowski wrote: > > On top of previous pull request. > > > The following changes since commit cda1a52dab50340728e46601e6c9da9fc4beaf1f: > > ARM: s3c64xx: Constify wake_irqs (2016-12-29 15:41:44 +0200) > > are available in the git

Re: [GIT PULL 4/4] arm64: dts: exynos: for v4.11, 2nd round

Hi Krzysztof, On Sun, Jan 29, 2017 at 10:06:29PM +0200, Krzysztof Kozlowski wrote: > Hi, > > On top of previous pull request. > > This adds proper clocks to LPASS node on Exynos5433 which is needed > by Marek's patchset: > - [PATCH v2 0/8] Pad retentions support for Exynos5433 >

Re: [PATCH 0/2] xen/net: limit number of tx/rx queues

On 01/10/2017 08:32 AM, Juergen Gross wrote: The Xen network frontend/backend supports multiple tx/rx queues for one virtual interface. The number of queues supported by the backend is set to the number of cpus of the backend driver domain (usually dom0) and the number of queues requested by

  1   2   3   4   5   6   >