[PATCH net-next 2/6] net: dsa: mv88e6xxx: describe Multi-chip registers

Add flags to describe the presence of SMI Command and Data registers used to indirectly access internal SMI devices registers when the switch SMI address is not zero. Signed-off-by: Vivien Didelot --- drivers/net/dsa/mv88e6xxx/chip.c | 2 +-

[PATCH net-next 2/6] net: dsa: mv88e6xxx: describe Multi-chip registers

Add flags to describe the presence of SMI Command and Data registers used to indirectly access internal SMI devices registers when the switch SMI address is not zero. Signed-off-by: Vivien Didelot --- drivers/net/dsa/mv88e6xxx/chip.c | 2 +- drivers/net/dsa/mv88e6xxx/mv88e6xxx.h | 40

[PATCH net-next 1/6] net: dsa: mv88e6xxx: rename _mv88e6xxx_wait

Now that there is no locked version of the wait routine anymore, rename the _ prefixed version and make it use the new read API. Signed-off-by: Vivien Didelot --- drivers/net/dsa/mv88e6xxx/chip.c | 63 +--- 1 file changed,

[PATCH net-next 3/6] net: dsa: mv88e6xxx: rework Global2 SMI PHY access

Describe the presence of the Global2 SMI PHY registers, used to indirectly access the internal SMI devices registers on some chips. Also temporarily forward declare mv88e6xxx_g2_smi_phy_{read,write} to use them in mv88e6xxx_mdio_{read,write}_indirect, before getting rid of the later.

[PATCH net-next 1/6] net: dsa: mv88e6xxx: rename _mv88e6xxx_wait

Now that there is no locked version of the wait routine anymore, rename the _ prefixed version and make it use the new read API. Signed-off-by: Vivien Didelot --- drivers/net/dsa/mv88e6xxx/chip.c | 63 +--- 1 file changed, 33 insertions(+), 30 deletions(-)

[PATCH net-next 3/6] net: dsa: mv88e6xxx: rework Global2 SMI PHY access

Describe the presence of the Global2 SMI PHY registers, used to indirectly access the internal SMI devices registers on some chips. Also temporarily forward declare mv88e6xxx_g2_smi_phy_{read,write} to use them in mv88e6xxx_mdio_{read,write}_indirect, before getting rid of the later.

[PATCH net-next 4/6] net: dsa: mv88e6xxx: abstract PHY ops

Old chips use a direct access to the PHY devices registers. Next chips have a PHY Polling Unit (PPU) which needs to be disabled before accessing PHY registers. Newer chips have an indirect access to the PHY devices so that disabling the PPU is not necessary. Introduce a new phy_ops structure in

[PATCH net-next 4/6] net: dsa: mv88e6xxx: abstract PHY ops

Old chips use a direct access to the PHY devices registers. Next chips have a PHY Polling Unit (PPU) which needs to be disabled before accessing PHY registers. Newer chips have an indirect access to the PHY devices so that disabling the PPU is not necessary. Introduce a new phy_ops structure in

[PATCH net-next 6/6] net: dsa: mv88e6xxx: use the new PHY API

This commit replaces every MDIO direct or indirect access with the new generic mv88e6xxx_phy_* routines. This allows us to get rid of the mv88e6xxx_mdio_{read,write}_{,in}direct and {_,}mv88e6xxx_mdio_page_{read,write} functions. Signed-off-by: Vivien Didelot

[PATCH net-next 6/6] net: dsa: mv88e6xxx: use the new PHY API

This commit replaces every MDIO direct or indirect access with the new generic mv88e6xxx_phy_* routines. This allows us to get rid of the mv88e6xxx_mdio_{read,write}_{,in}direct and {_,}mv88e6xxx_mdio_page_{read,write} functions. Signed-off-by: Vivien Didelot ---

[PATCH net-next 0/6] net: dsa: abstract PHY accesses

The Marvell 88E6xxx switch chips have different way to access the PHY devices registers. Old chips use a direct access to the PHY registers. Next chips have a PHY Polling Unit (PPU) which needs to be disabled before accessing PHY registers. Newer chips have an indirect access to the PHY devices

Re: [PATCH] libnvdimm: Fix nvdimm_probe error on NVDIMM-N

On Mon, Aug 15, 2016 at 10:52 AM, Toshi Kani wrote: > 'ndctl list --buses --dimms' does not list any NVDIMM-Ns since > they are considered as idle. ndctl checks if any driver is > attached to nmem device. nvdimm_probe() always fails in > nvdimm_init_nsarea() since NVDIMM-Ns

[PATCH net-next 0/6] net: dsa: abstract PHY accesses

The Marvell 88E6xxx switch chips have different way to access the PHY devices registers. Old chips use a direct access to the PHY registers. Next chips have a PHY Polling Unit (PPU) which needs to be disabled before accessing PHY registers. Newer chips have an indirect access to the PHY devices

Re: [PATCH] libnvdimm: Fix nvdimm_probe error on NVDIMM-N

On Mon, Aug 15, 2016 at 10:52 AM, Toshi Kani wrote: > 'ndctl list --buses --dimms' does not list any NVDIMM-Ns since > they are considered as idle. ndctl checks if any driver is > attached to nmem device. nvdimm_probe() always fails in > nvdimm_init_nsarea() since NVDIMM-Ns do not implement

[PATCH net-next 5/6] net: dsa: mv88e6xxx: describe PHY page and SerDes

Add mv88e6xxx_phy_page_{read,write} routines and use them to access the SerDes PHY device registers. Signed-off-by: Vivien Didelot --- drivers/net/dsa/mv88e6xxx/chip.c | 95 +-- drivers/net/dsa/mv88e6xxx/mv88e6xxx.h | 27

[PATCH net-next 5/6] net: dsa: mv88e6xxx: describe PHY page and SerDes

Add mv88e6xxx_phy_page_{read,write} routines and use them to access the SerDes PHY device registers. Signed-off-by: Vivien Didelot --- drivers/net/dsa/mv88e6xxx/chip.c | 95 +-- drivers/net/dsa/mv88e6xxx/mv88e6xxx.h | 27 -- 2 files changed, 105

Re: [PATCH 1/1] sbs-battery: add ability to get battery capacity

Hi, On Thu, Aug 11, 2016 at 09:59:12AM -0700, Joshua Clayton wrote: > Battery capacity level is a standard feature of sbs battery > That can be used to tell what the remainig battery capacity is, and > can tell if the battery has not been calibrated/initialized, which makes > the capacity and

Re: [PATCH 1/1] sbs-battery: add ability to get battery capacity

Hi, On Thu, Aug 11, 2016 at 09:59:12AM -0700, Joshua Clayton wrote: > Battery capacity level is a standard feature of sbs battery > That can be used to tell what the remainig battery capacity is, and > can tell if the battery has not been calibrated/initialized, which makes > the capacity and

Re: [PATCH 0/7] re-enable DAX PMD support

On Mon, Aug 15, 2016 at 2:11 PM, Ross Zwisler wrote: > On Mon, Aug 15, 2016 at 01:21:47PM -0700, Dan Williams wrote: >> On Mon, Aug 15, 2016 at 12:09 PM, Ross Zwisler >> wrote: >> > DAX PMDs have been disabled since Jan Kara introduced

Re: [PATCH 0/7] re-enable DAX PMD support

On Mon, Aug 15, 2016 at 2:11 PM, Ross Zwisler wrote: > On Mon, Aug 15, 2016 at 01:21:47PM -0700, Dan Williams wrote: >> On Mon, Aug 15, 2016 at 12:09 PM, Ross Zwisler >> wrote: >> > DAX PMDs have been disabled since Jan Kara introduced DAX radix tree based >> > locking. This series allows DAX

Re: [PATCH 1/2] staging: lustre: Add include path to Makefile

On Mon, 2016-08-15 at 23:04 +0200, Greg Kroah-Hartman wrote: > On Mon, Aug 15, 2016 at 12:33:23PM -0700, Joe Perches wrote: > > Start to rationalize include paths in source code files. [] > > diff --git a/drivers/staging/lustre/Makefile > > b/drivers/staging/lustre/Makefile [] > > @@ -1,2 +1,5 @@

Re: [PATCH 1/2] staging: lustre: Add include path to Makefile

On Mon, 2016-08-15 at 23:04 +0200, Greg Kroah-Hartman wrote: > On Mon, Aug 15, 2016 at 12:33:23PM -0700, Joe Perches wrote: > > Start to rationalize include paths in source code files. [] > > diff --git a/drivers/staging/lustre/Makefile > > b/drivers/staging/lustre/Makefile [] > > @@ -1,2 +1,5 @@

Re: [PATCH 0/7] re-enable DAX PMD support

On Mon, Aug 15, 2016 at 01:21:47PM -0700, Dan Williams wrote: > On Mon, Aug 15, 2016 at 12:09 PM, Ross Zwisler > wrote: > > DAX PMDs have been disabled since Jan Kara introduced DAX radix tree based > > locking. This series allows DAX PMDs to participate in the DAX

Re: [PATCH 0/7] re-enable DAX PMD support

On Mon, Aug 15, 2016 at 01:21:47PM -0700, Dan Williams wrote: > On Mon, Aug 15, 2016 at 12:09 PM, Ross Zwisler > wrote: > > DAX PMDs have been disabled since Jan Kara introduced DAX radix tree based > > locking. This series allows DAX PMDs to participate in the DAX radix tree > > based locking

Re: [PATCH v3 4/6] clk: mvebu Add the time base generator clocks for Armada 3700

On 07/19, Gregory CLEMENT wrote: > These clocks are children of the xtal clock and each one can be selected > as a source for the peripheral clocks. > > According to the datasheet it should be possible to modify their rate, > but currently it is not supported. > > Signed-off-by: Gregory CLEMENT

Re: [PATCH v3 2/6] clk: mvebu: Add the xtal clock for Armada 3700 SoC

On 07/19, Gregory CLEMENT wrote: > This clock is the parent of all the Armada 3700 clocks. It is a fixed > rate clock which depends on the gpio configuration read when resetting > the SoC. > > Signed-off-by: Gregory CLEMENT > --- Applied to clk-next --

Re: [PATCH v3 4/6] clk: mvebu Add the time base generator clocks for Armada 3700

On 07/19, Gregory CLEMENT wrote: > These clocks are children of the xtal clock and each one can be selected > as a source for the peripheral clocks. > > According to the datasheet it should be possible to modify their rate, > but currently it is not supported. > > Signed-off-by: Gregory CLEMENT

Re: [PATCH v3 2/6] clk: mvebu: Add the xtal clock for Armada 3700 SoC

On 07/19, Gregory CLEMENT wrote: > This clock is the parent of all the Armada 3700 clocks. It is a fixed > rate clock which depends on the gpio configuration read when resetting > the SoC. > > Signed-off-by: Gregory CLEMENT > --- Applied to clk-next -- Qualcomm Innovation Center, Inc. is a

Re: [PATCH v3 1/6] dt-bindings: clock: add DT binding for the Xtal clock on Armada 3700

On 07/19, Gregory CLEMENT wrote: > This commit adds the DT binding documentation for the the Xtal clock on > Armada 3700 used in the Marvell Armada 3700 SoCs. > > Signed-off-by: Gregory CLEMENT > Acked-by: Rob Herring > --- Applied to

Re: [PATCH v3 3/6] dt-bindings: clock: add DT binding for the TBG clocks on Armada 3700

On 07/19, Gregory CLEMENT wrote: > This commit adds the DT binding documentation for the Time Base Generator > clock used in the Marvell Armada 3700 SoCs. > > Signed-off-by: Gregory CLEMENT > Acked-by: Rob Herring > --- Applied to clk-next

Re: [PATCH v3 1/6] dt-bindings: clock: add DT binding for the Xtal clock on Armada 3700

On 07/19, Gregory CLEMENT wrote: > This commit adds the DT binding documentation for the the Xtal clock on > Armada 3700 used in the Marvell Armada 3700 SoCs. > > Signed-off-by: Gregory CLEMENT > Acked-by: Rob Herring > --- Applied to clk-next -- Qualcomm Innovation Center, Inc. is a member

Re: [PATCH v3 3/6] dt-bindings: clock: add DT binding for the TBG clocks on Armada 3700

On 07/19, Gregory CLEMENT wrote: > This commit adds the DT binding documentation for the Time Base Generator > clock used in the Marvell Armada 3700 SoCs. > > Signed-off-by: Gregory CLEMENT > Acked-by: Rob Herring > --- Applied to clk-next -- Qualcomm Innovation Center, Inc. is a member of

Re: [lustre-devel] [PATCH 1/2] staging: lustre: Add include path to Makefile

> On Mon, Aug 15, 2016 at 12:33:23PM -0700, Joe Perches wrote: > > Start to rationalize include paths in source code files. > > > > Signed-off-by: Joe Perches > > --- > > drivers/staging/lustre/Makefile | 3 +++ > > 1 file changed, 3 insertions(+) > > > > diff --git

Re: [lustre-devel] [PATCH 1/2] staging: lustre: Add include path to Makefile

> On Mon, Aug 15, 2016 at 12:33:23PM -0700, Joe Perches wrote: > > Start to rationalize include paths in source code files. > > > > Signed-off-by: Joe Perches > > --- > > drivers/staging/lustre/Makefile | 3 +++ > > 1 file changed, 3 insertions(+) > > > > diff --git

Re: [PATCH 1/2] staging: lustre: Add include path to Makefile

On Mon, Aug 15, 2016 at 12:33:23PM -0700, Joe Perches wrote: > Start to rationalize include paths in source code files. > > Signed-off-by: Joe Perches > --- > drivers/staging/lustre/Makefile | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git

Re: [PATCH 1/2] staging: lustre: Add include path to Makefile

On Mon, Aug 15, 2016 at 12:33:23PM -0700, Joe Perches wrote: > Start to rationalize include paths in source code files. > > Signed-off-by: Joe Perches > --- > drivers/staging/lustre/Makefile | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git a/drivers/staging/lustre/Makefile

uprobes: memory leak in enable/disable loop

Hi folks, I think I have come across a memory leak in uprobes, which is fairly easy to reproduce. Using a repeated use of a single uprobe, I am able to run my system out of memory, resulting in system failures and a need to reboot the box. When I first became aware of the failure, I was able to

uprobes: memory leak in enable/disable loop

Hi folks, I think I have come across a memory leak in uprobes, which is fairly easy to reproduce. Using a repeated use of a single uprobe, I am able to run my system out of memory, resulting in system failures and a need to reboot the box. When I first became aware of the failure, I was able to

Re: [PATCH v2] clocksource: sun4i: Clear interrupts after stopping timer in probe function

On Mon, Aug 15, 2016 at 12:57:04PM +0800, Chen-Yu Tsai wrote: > The bootloader (U-boot) sometimes uses this timer for various delays. > It uses it as a ongoing counter, and does comparisons on the current > counter value. The timer counter is never stopped. > > In some cases when the user

Re: [PATCH] tipc: fix NULL pointer dereference in shutdown()

From: Jon Maloy Date: Mon, 15 Aug 2016 19:48:24 + > Sorry, I just came back from vacation today. > > Acked-by: Jon Maloy Applied.

Re: [PATCH v2] clocksource: sun4i: Clear interrupts after stopping timer in probe function

On Mon, Aug 15, 2016 at 12:57:04PM +0800, Chen-Yu Tsai wrote: > The bootloader (U-boot) sometimes uses this timer for various delays. > It uses it as a ongoing counter, and does comparisons on the current > counter value. The timer counter is never stopped. > > In some cases when the user

Re: [PATCH] tipc: fix NULL pointer dereference in shutdown()

From: Jon Maloy Date: Mon, 15 Aug 2016 19:48:24 + > Sorry, I just came back from vacation today. > > Acked-by: Jon Maloy Applied.

[PATCH] leds: make triggers explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/leds/trigger/Kconfig:menuconfig LEDS_TRIGGERS drivers/leds/trigger/Kconfig: bool "LED Trigger support" ...meaning that it currently is not being built as a module by anyone. Lets remove the couple traces of modular

[PATCH] leds: make triggers explicitly non-modular

The Kconfig currently controlling compilation of this code is: drivers/leds/trigger/Kconfig:menuconfig LEDS_TRIGGERS drivers/leds/trigger/Kconfig: bool "LED Trigger support" ...meaning that it currently is not being built as a module by anyone. Lets remove the couple traces of modular

Re: musb: am3358: having performance problem with usb1

On 08/13/2016 01:44 AM, Greg KH wrote: On Sat, Aug 13, 2016 at 12:38:46AM +0800, ayaka wrote: On 08/12/2016 03:40 PM, Greg KH wrote: On Fri, Aug 12, 2016 at 10:23:15AM +0800, ayaka wrote: Hello all: I recently add a support for customize am3358 board using the branch

Re: musb: am3358: having performance problem with usb1

On 08/13/2016 01:44 AM, Greg KH wrote: On Sat, Aug 13, 2016 at 12:38:46AM +0800, ayaka wrote: On 08/12/2016 03:40 PM, Greg KH wrote: On Fri, Aug 12, 2016 at 10:23:15AM +0800, ayaka wrote: Hello all: I recently add a support for customize am3358 board using the branch

Re: [PATCH net v2 0/5] hv_netvsc: fixes for VF removal path

From: Vitaly Kuznetsov Date: Mon, 15 Aug 2016 17:48:38 +0200 > Kernel crash is reported after VF is removed and detached from netvsc > device. Turns out we have multiple different (but related) issues on the > VF removal path which I'm trying to address with PATCHes 2-5 of

Re: [PATCH net v2 0/5] hv_netvsc: fixes for VF removal path

From: Vitaly Kuznetsov Date: Mon, 15 Aug 2016 17:48:38 +0200 > Kernel crash is reported after VF is removed and detached from netvsc > device. Turns out we have multiple different (but related) issues on the > VF removal path which I'm trying to address with PATCHes 2-5 of this > series. PATCH1

Re: [PATCH v6 0/5] /dev/random - a new approach

On 08/11/16 05:24, Stephan Mueller wrote: > * prevent fast noise sources from dominating slow noise sources > in case of /dev/random Can someone please explain if and why this is actually desirable, and if this assessment has been passed to someone who has actual experience with cryptography at

Re: [PATCH v6 0/5] /dev/random - a new approach

On 08/11/16 05:24, Stephan Mueller wrote: > * prevent fast noise sources from dominating slow noise sources > in case of /dev/random Can someone please explain if and why this is actually desirable, and if this assessment has been passed to someone who has actual experience with cryptography at

[PATCH] Try to support analog audio codec at firefly reload

Hello: This patch could enabled the es8328 codec at firefly reload board, but it doesn't not really work. I disable the mute of channel Left mix and Right mix in alsamixer, I could hear the noise from my headphone, but it never be a music. I just send this patch here to see whether somebody

[PATCH] ARM: dts: rockchip: add analog audio support for firefly reload

The ES8323 found on firefly reload board is used to output analog audio to headphone and capture the sound from micphone on board and the one may attach to headphone. It would be also used to capture the sound from HDMI IN. Signed-off-by: Randy Li ---

[PATCH] Try to support analog audio codec at firefly reload

Hello: This patch could enabled the es8328 codec at firefly reload board, but it doesn't not really work. I disable the mute of channel Left mix and Right mix in alsamixer, I could hear the noise from my headphone, but it never be a music. I just send this patch here to see whether somebody

[PATCH] ARM: dts: rockchip: add analog audio support for firefly reload

The ES8323 found on firefly reload board is used to output analog audio to headphone and capture the sound from micphone on board and the one may attach to headphone. It would be also used to capture the sound from HDMI IN. Signed-off-by: Randy Li --- arch/arm/boot/dts/rk3288-firefly-reload.dts

[PATCH] powerpc: mpc8349emitx: Delete unnecessary assignment for the field "owner"

From: Markus Elfring Date: Mon, 15 Aug 2016 22:36:05 +0200 The field "owner" is set by the core. Thus delete an unneeded initialisation. Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci Signed-off-by: Markus Elfring

[PATCH] powerpc: mpc8349emitx: Delete unnecessary assignment for the field "owner"

From: Markus Elfring Date: Mon, 15 Aug 2016 22:36:05 +0200 The field "owner" is set by the core. Thus delete an unneeded initialisation. Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci Signed-off-by: Markus Elfring --- arch/powerpc/platforms/83xx/mcu_mpc8349emitx.c | 1 - 1

Re: [PATCH v3 3/3] ARM64: dts: amlogic: meson-gxbb: Add watchdog node

Kevin Hilman writes: > On Wed, Aug 3, 2016 at 5:27 PM, Kevin Hilman wrote: >> Hi Guenter, >> >> Kevin Hilman writes: >> >>> Guenter Roeck writes: >>> On 07/10/2016 02:11 AM, Neil Armstrong wrote: >

Re: [PATCH v3 3/3] ARM64: dts: amlogic: meson-gxbb: Add watchdog node

Kevin Hilman writes: > On Wed, Aug 3, 2016 at 5:27 PM, Kevin Hilman wrote: >> Hi Guenter, >> >> Kevin Hilman writes: >> >>> Guenter Roeck writes: >>> On 07/10/2016 02:11 AM, Neil Armstrong wrote: > Signed-off-by: Neil Armstrong Reviewed-by: Guenter Roeck Would

Re: BUG and WARN kernel log levels

On Mon, 2016-08-15 at 13:28 -0700, Kees Cook wrote: > On Mon, Aug 15, 2016 at 12:00 PM, Joe Perches wrote: > > On Mon, 2016-08-15 at 11:53 -0700, Kees Cook wrote: > > > So, I noticed that asm-gemeric/bug.h defines BUG() without a log level: > > > > > > #ifndef HAVE_ARCH_BUG > >

Re: BUG and WARN kernel log levels

On Mon, 2016-08-15 at 13:28 -0700, Kees Cook wrote: > On Mon, Aug 15, 2016 at 12:00 PM, Joe Perches wrote: > > On Mon, 2016-08-15 at 11:53 -0700, Kees Cook wrote: > > > So, I noticed that asm-gemeric/bug.h defines BUG() without a log level: > > > > > > #ifndef HAVE_ARCH_BUG > > > #define BUG()

Re: [PATCH] net: hns: mdio->irq is an array, so no need to check if it is null

From: Colin King Date: Mon, 15 Aug 2016 13:55:17 +0100 > From: Colin Ian King > > The null check on mdio->irq is redundant since mdio->irq is an array > of PHY_MAX_ADDR ints and hence can never be null. Remove the redundant > check. > >

Re: [PATCH] net: hns: mdio->irq is an array, so no need to check if it is null

From: Colin King Date: Mon, 15 Aug 2016 13:55:17 +0100 > From: Colin Ian King > > The null check on mdio->irq is redundant since mdio->irq is an array > of PHY_MAX_ADDR ints and hence can never be null. Remove the redundant > check. > > Signed-off-by: Colin Ian King Applied, thanks.

Re: [LKP] [lkp] [xfs] 68a9f5e700: aim7.jobs-per-min -13.6% regression

Christoph Hellwig writes: > Snipping the long contest: > > I think there are three observations here: > > (1) removing the mark_page_accessed (which is the only significant > change in the parent commit) hurts the > aim7/1BRD_48G-xfs-disk_rr-3000-performance/ivb44 test.

Re: [LKP] [lkp] [xfs] 68a9f5e700: aim7.jobs-per-min -13.6% regression

Christoph Hellwig writes: > Snipping the long contest: > > I think there are three observations here: > > (1) removing the mark_page_accessed (which is the only significant > change in the parent commit) hurts the > aim7/1BRD_48G-xfs-disk_rr-3000-performance/ivb44 test. > I'd

Re: spin_lock implicit/explicit memory barrier

On Mon, Aug 15, 2016 at 10:06:39PM +0200, Manfred Spraul wrote: > Hi Paul, > > On 08/10/2016 11:00 PM, Paul E. McKenney wrote: > >On Wed, Aug 10, 2016 at 12:17:57PM -0700, Davidlohr Bueso wrote: > >>[...] > >> CPU0 CPU1 > >> complex_mode = true

Re: BUG and WARN kernel log levels

On Mon, Aug 15, 2016 at 12:00 PM, Joe Perches wrote: > On Mon, 2016-08-15 at 11:53 -0700, Kees Cook wrote: >> Hi, >> >> So, I noticed that asm-gemeric/bug.h defines BUG() without a log level: >> >> #ifndef HAVE_ARCH_BUG >> #define BUG() do { \ >>printk("BUG: failure at

Re: spin_lock implicit/explicit memory barrier

On Mon, Aug 15, 2016 at 10:06:39PM +0200, Manfred Spraul wrote: > Hi Paul, > > On 08/10/2016 11:00 PM, Paul E. McKenney wrote: > >On Wed, Aug 10, 2016 at 12:17:57PM -0700, Davidlohr Bueso wrote: > >>[...] > >> CPU0 CPU1 > >> complex_mode = true

Re: BUG and WARN kernel log levels

On Mon, Aug 15, 2016 at 12:00 PM, Joe Perches wrote: > On Mon, 2016-08-15 at 11:53 -0700, Kees Cook wrote: >> Hi, >> >> So, I noticed that asm-gemeric/bug.h defines BUG() without a log level: >> >> #ifndef HAVE_ARCH_BUG >> #define BUG() do { \ >>printk("BUG: failure at %s:%d/%s()!\n",

Re: [PATCH 0/7] re-enable DAX PMD support

On Mon, Aug 15, 2016 at 12:09 PM, Ross Zwisler wrote: > DAX PMDs have been disabled since Jan Kara introduced DAX radix tree based > locking. This series allows DAX PMDs to participate in the DAX radix tree > based locking scheme so that they can be re-enabled.

Re: [PATCH 0/7] re-enable DAX PMD support

On Mon, Aug 15, 2016 at 12:09 PM, Ross Zwisler wrote: > DAX PMDs have been disabled since Jan Kara introduced DAX radix tree based > locking. This series allows DAX PMDs to participate in the DAX radix tree > based locking scheme so that they can be re-enabled. Looks good to me. > This series

[PATCH] powerpc/512x: Delete unnecessary assignment for the field "owner"

From: Markus Elfring Date: Mon, 15 Aug 2016 22:07:54 +0200 The field "owner" is set by the core. Thus delete an unneeded initialisation. Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci Signed-off-by: Markus Elfring

[PATCH] powerpc/512x: Delete unnecessary assignment for the field "owner"

From: Markus Elfring Date: Mon, 15 Aug 2016 22:07:54 +0200 The field "owner" is set by the core. Thus delete an unneeded initialisation. Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci Signed-off-by: Markus Elfring --- arch/powerpc/platforms/512x/mpc512x_lpbfifo.c | 1 - 1

Re: [PACTH v2 1/3] mm, proc: Implement /proc//totmaps

On 2016-08-15 09:57 AM, Robert Foss wrote: On 2016-08-13 10:39 AM, Jann Horn wrote: On Fri, Aug 12, 2016 at 06:04:20PM -0400, robert.f...@collabora.com wrote: diff --git a/fs/proc/internal.h b/fs/proc/internal.h index aa27810..c55e1fe 100644 --- a/fs/proc/internal.h +++

Re: [PACTH v2 1/3] mm, proc: Implement /proc//totmaps

On 2016-08-15 09:57 AM, Robert Foss wrote: On 2016-08-13 10:39 AM, Jann Horn wrote: On Fri, Aug 12, 2016 at 06:04:20PM -0400, robert.f...@collabora.com wrote: diff --git a/fs/proc/internal.h b/fs/proc/internal.h index aa27810..c55e1fe 100644 --- a/fs/proc/internal.h +++

[PATCH 1/2] kernel: show current values of user namespace counters

Recently Eric added user namespace counters. User namespace counters is a feature that allows to limit the number of various kernel objects a user can create. These limits are set via /proc/sys/user/ sysctls on a per user namespace basis and are applicable to all users in that namespace. This

[PATCH 1/2] kernel: show current values of user namespace counters

Recently Eric added user namespace counters. User namespace counters is a feature that allows to limit the number of various kernel objects a user can create. These limits are set via /proc/sys/user/ sysctls on a per user namespace basis and are applicable to all users in that namespace. This

[PATCH 2/2] Documentation: describe /proc//userns_counts

From: Kirill Kolyshkin This file provides current usage of user namespace counters. Signed-off-by: Kirill Kolyshkin Signed-off-by: Andrei Vagin --- Documentation/filesystems/proc.txt | 30 ++ 1 file changed, 30

[PATCH 2/2] Documentation: describe /proc//userns_counts

From: Kirill Kolyshkin This file provides current usage of user namespace counters. Signed-off-by: Kirill Kolyshkin Signed-off-by: Andrei Vagin --- Documentation/filesystems/proc.txt | 30 ++ 1 file changed, 30 insertions(+) diff --git

[PATCH 0/2 v2] userns: show current values of user namespace counters

Recently Eric added user namespace counters. User namespace counters is a feature that allows to limit the number of various kernel objects a user can create. These limits are set via /proc/sys/user/ sysctls on a per user namespace basis and are applicable to all users in that namespace. User

[PATCH 0/2 v2] userns: show current values of user namespace counters

Recently Eric added user namespace counters. User namespace counters is a feature that allows to limit the number of various kernel objects a user can create. These limits are set via /proc/sys/user/ sysctls on a per user namespace basis and are applicable to all users in that namespace. User

RE: [PATCH] tipc: fix NULL pointer dereference in shutdown()

Sorry, I just came back from vacation today. Acked-by: Jon Maloy > -Original Message- > From: Vegard Nossum [mailto:vegard.nos...@oracle.com] > Sent: Friday, 12 August, 2016 10:38 > To: Ying Xue ; Jon Maloy ; >

RE: [PATCH] tipc: fix NULL pointer dereference in shutdown()

Sorry, I just came back from vacation today. Acked-by: Jon Maloy > -Original Message- > From: Vegard Nossum [mailto:vegard.nos...@oracle.com] > Sent: Friday, 12 August, 2016 10:38 > To: Ying Xue ; Jon Maloy ; > David S. Miller > Cc: net...@vger.kernel.org; Michael Kerrisk ; >

Re: spin_lock implicit/explicit memory barrier

Hi Paul, On 08/10/2016 11:00 PM, Paul E. McKenney wrote: On Wed, Aug 10, 2016 at 12:17:57PM -0700, Davidlohr Bueso wrote: [...] CPU0 CPU1 complex_mode = truespin_lock(l) smp_mb() <--- do we want a smp_mb() here?

Re: spin_lock implicit/explicit memory barrier

Hi Paul, On 08/10/2016 11:00 PM, Paul E. McKenney wrote: On Wed, Aug 10, 2016 at 12:17:57PM -0700, Davidlohr Bueso wrote: [...] CPU0 CPU1 complex_mode = truespin_lock(l) smp_mb() <--- do we want a smp_mb() here?

Re: [PATCH v3 16/51] x86/32: put real return address on stack in entry code

On Mon, Aug 15, 2016 at 12:22:33PM -0700, H. Peter Anvin wrote: > On 08/15/16 11:25, Josh Poimboeuf wrote: > > On Mon, Aug 15, 2016 at 11:04:42AM -0700, H. Peter Anvin wrote: > >> On 08/15/16 08:09, Josh Poimboeuf wrote: > >>> On Sun, Aug 14, 2016 at 12:31:47AM -0700, Andy Lutomirski wrote: >

Re: [PATCH v3 16/51] x86/32: put real return address on stack in entry code

On Mon, Aug 15, 2016 at 12:22:33PM -0700, H. Peter Anvin wrote: > On 08/15/16 11:25, Josh Poimboeuf wrote: > > On Mon, Aug 15, 2016 at 11:04:42AM -0700, H. Peter Anvin wrote: > >> On 08/15/16 08:09, Josh Poimboeuf wrote: > >>> On Sun, Aug 14, 2016 at 12:31:47AM -0700, Andy Lutomirski wrote: >

Re: [ANNOUNCE] git-series: track changes to a patch series over time

On Mon, Aug 15, 2016 at 12:17:11PM -0600, Simon Glass wrote: > On 1 August 2016 at 12:37, Josh Triplett wrote: > > On Mon, Aug 01, 2016 at 09:14:54AM -0600, Stephen Warren wrote: > >> On 07/29/2016 12:40 AM, Josh Triplett wrote: > >> > I'd like to announce a project I've

Re: [ANNOUNCE] git-series: track changes to a patch series over time

On Mon, Aug 15, 2016 at 12:17:11PM -0600, Simon Glass wrote: > On 1 August 2016 at 12:37, Josh Triplett wrote: > > On Mon, Aug 01, 2016 at 09:14:54AM -0600, Stephen Warren wrote: > >> On 07/29/2016 12:40 AM, Josh Triplett wrote: > >> > I'd like to announce a project I've been working on for a

Re: [PATCH v3 09/51] x86/dumpstack: fix x86_32 kernel_stack_pointer() previous stack access

On Mon, Aug 15, 2016 at 10:22 AM, Josh Poimboeuf wrote: > On Mon, Aug 15, 2016 at 10:05:58AM -0500, Josh Poimboeuf wrote: >> On Sun, Aug 14, 2016 at 12:26:29AM -0700, Andy Lutomirski wrote: >> > On Fri, Aug 12, 2016 at 7:28 AM, Josh Poimboeuf >> >

Re: [PATCH v3 09/51] x86/dumpstack: fix x86_32 kernel_stack_pointer() previous stack access

On Mon, Aug 15, 2016 at 10:22 AM, Josh Poimboeuf wrote: > On Mon, Aug 15, 2016 at 10:05:58AM -0500, Josh Poimboeuf wrote: >> On Sun, Aug 14, 2016 at 12:26:29AM -0700, Andy Lutomirski wrote: >> > On Fri, Aug 12, 2016 at 7:28 AM, Josh Poimboeuf >> > wrote: >> > > On x86_32, when an interrupt

[PATCH v12 PATCH 2/5] phy: Add USB Type-C PHY driver for rk3399

Add a PHY provider driver for the rk3399 SoC Type-c PHY. The USB Type-C PHY is designed to support the USB3 and DP applications. The PHY basically has two main components: USB3 and DisplyPort. USB3 operates in SuperSpeed mode and the DP can operate at RBR, HBR and HBR2 data rates. Hence, create 2

[PATCH v12 PATCH 2/5] phy: Add USB Type-C PHY driver for rk3399

Add a PHY provider driver for the rk3399 SoC Type-c PHY. The USB Type-C PHY is designed to support the USB3 and DP applications. The PHY basically has two main components: USB3 and DisplyPort. USB3 operates in SuperSpeed mode and the DP can operate at RBR, HBR and HBR2 data rates. Hence, create 2

[PATCH v12 PATCH 5/5] drm/rockchip: cdn-dp: add cdn DP support for rk3399

Add support for cdn DP controller which is embedded in the rk3399 SoCs. The DP is compliant with DisplayPort Specification, Version 1.3, This IP is compatible with the rockchip type-c PHY IP. There is a uCPU in DP controller, it need a firmware to work, please put the firmware file to

[PATCH v12 PATCH 0/5] Rockchip Type-C and DisplayPort driver

Hi all This series patch is for rockchip Type-C phy and DisplayPort controller driver. The USB Type-C PHY is designed to support the USB3 and DP applications. The PHY basically has two main components: USB3 and DisplyPort. USB3 operates in SuperSpeed mode and the DP can operate at RBR, HBR and

[PATCH v12 PATCH 5/5] drm/rockchip: cdn-dp: add cdn DP support for rk3399

Add support for cdn DP controller which is embedded in the rk3399 SoCs. The DP is compliant with DisplayPort Specification, Version 1.3, This IP is compatible with the rockchip type-c PHY IP. There is a uCPU in DP controller, it need a firmware to work, please put the firmware file to

[PATCH v12 PATCH 0/5] Rockchip Type-C and DisplayPort driver

Hi all This series patch is for rockchip Type-C phy and DisplayPort controller driver. The USB Type-C PHY is designed to support the USB3 and DP applications. The PHY basically has two main components: USB3 and DisplyPort. USB3 operates in SuperSpeed mode and the DP can operate at RBR, HBR and

[PATCH v12 PATCH 1/5] Documentation: bindings: add dt doc for Rockchip USB Type-C PHY

This patch adds a binding that describes the Rockchip USB Type-C PHY for rk3399 Signed-off-by: Chris Zhong Reviewed-by: Tomasz Figa Reviewed-by: Kever Yang Reviewed-by: Guenter Roeck Acked-by: Rob Herring

[PATCH v12 PATCH 4/5] Documentation: bindings: add dt documentation for cdn DP controller

This patch adds a binding that describes the cdn DP controller for rk3399. Signed-off-by: Chris Zhong Acked-by: Rob Herring --- Changes in v12: None Changes in v11: - refer dp phy Changes in v10: - add pclk_vio_grf clock Changes in v9: - modify the

[PATCH v12 PATCH 3/5] arm64: dts: rockchip: add Type-C phy for RK3399

There are 2 Type-C phy on RK3399, they are almost same, except the address of register. They support USB3.0 Type-C and DisplayPort1.3 Alt Mode on USB Type-C. Register a phy, supply it to USB3 controller and DP controller. Signed-off-by: Chris Zhong Reviewed-by: Guenter Roeck

[PATCH v12 PATCH 1/5] Documentation: bindings: add dt doc for Rockchip USB Type-C PHY

This patch adds a binding that describes the Rockchip USB Type-C PHY for rk3399 Signed-off-by: Chris Zhong Reviewed-by: Tomasz Figa Reviewed-by: Kever Yang Reviewed-by: Guenter Roeck Acked-by: Rob Herring --- Changes in v12: None Changes in v11: - make a clearer emarcation between usb phy

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