Re: [PATCH 0/2] Input-at32psif: Fine-tuning for OOM handling in psif_probe()

2016-07-02 Thread Joe Perches
On Sat, 2016-07-02 at 21:00 +0200, SF Markus Elfring wrote: > From: Markus Elfring > Date: Sat, 2 Jul 2016 20:50:09 +0200 > > A few update suggestions were taken into account > from static source code analysis. > > Markus Elfring (2): >   Return directly after a

Re: [PATCH 0/2] Input-at32psif: Fine-tuning for OOM handling in psif_probe()

2016-07-02 Thread Joe Perches
On Sat, 2016-07-02 at 21:00 +0200, SF Markus Elfring wrote: > From: Markus Elfring > Date: Sat, 2 Jul 2016 20:50:09 +0200 > > A few update suggestions were taken into account > from static source code analysis. > > Markus Elfring (2): >   Return directly after a failed kzalloc() >   Remove two

Re: [PATCH 1/2] iio: sun4i-lradc: Add binding documentation

2016-07-02 Thread Alexandre Belloni
On 02/07/2016 at 21:46:43 +0200, Hans de Goede wrote : > Hi, > > On 02-07-16 15:35, Alexandre Belloni wrote: > > On 02/07/2016 at 17:12:55 +0800, Chen-Yu Tsai wrote : > > > Hi, > > > > > > On Sat, Jul 2, 2016 at 5:00 AM, Alexandre Belloni > > > wrote: > > >

Re: [PATCH 1/2] iio: sun4i-lradc: Add binding documentation

2016-07-02 Thread Alexandre Belloni
On 02/07/2016 at 21:46:43 +0200, Hans de Goede wrote : > Hi, > > On 02-07-16 15:35, Alexandre Belloni wrote: > > On 02/07/2016 at 17:12:55 +0800, Chen-Yu Tsai wrote : > > > Hi, > > > > > > On Sat, Jul 2, 2016 at 5:00 AM, Alexandre Belloni > > > wrote: > > > > Document the bindings for the

Re: [PATCH] net-next: mediatek: fix compile error inside mtk_poll_controller()

2016-07-02 Thread David Miller
From: John Crispin Date: Sat, 2 Jul 2016 08:00:50 +0200 > commit 8067302973a1 ("net-next: mediatek: add support for IRQ grouping") > failed to properly update the irq handling inside mtk_poll_controller() > causing compile errors if netconsole was enabled. Fix this by updating

Re: [PATCH] net-next: mediatek: fix compile error inside mtk_poll_controller()

2016-07-02 Thread David Miller
From: John Crispin Date: Sat, 2 Jul 2016 08:00:50 +0200 > commit 8067302973a1 ("net-next: mediatek: add support for IRQ grouping") > failed to properly update the irq handling inside mtk_poll_controller() > causing compile errors if netconsole was enabled. Fix this by updating > the code to use

Re: [PATCH 5/9] perf, tools: Compute IPC and basic block cycles for annotate

2016-07-02 Thread Andi Kleen
> I'm looking at basic block support, but this all seems to depend on the > cycles stuff. Can we get the basic block stuff without that? Not sure what you mean with basic block stuff, but ... > > I'm looking to plot the hottest path through a branchy function. Use --branch-history to get a

Re: [PATCH 5/9] perf, tools: Compute IPC and basic block cycles for annotate

2016-07-02 Thread Andi Kleen
> I'm looking at basic block support, but this all seems to depend on the > cycles stuff. Can we get the basic block stuff without that? Not sure what you mean with basic block stuff, but ... > > I'm looking to plot the hottest path through a branchy function. Use --branch-history to get a

Re: [PATCH] net/mlx4: Fix some indent inconsistancy

2016-07-02 Thread Leon Romanovsky
On Sat, Jul 02, 2016 at 02:31:05PM +0200, Christophe JAILLET wrote: > Silent a few smatch warnings about indentation. > This include the removal of a 'return' statement in 'resource_tracker.c'. > This 'return' will still be performed when breaking out of the > corresponding 'switch' block. > >

Re: [PATCH] net/mlx4: Fix some indent inconsistancy

2016-07-02 Thread Leon Romanovsky
On Sat, Jul 02, 2016 at 02:31:05PM +0200, Christophe JAILLET wrote: > Silent a few smatch warnings about indentation. > This include the removal of a 'return' statement in 'resource_tracker.c'. > This 'return' will still be performed when breaking out of the > corresponding 'switch' block. > >

Re: [PATCH RFC 6/7] clk: imx: pllv3: convert to prepare_hw and set_rate_hw

2016-07-02 Thread Fabio Estevam
Hi Dong, On Wed, Jun 29, 2016 at 10:52 AM, Dong Aisheng wrote: Thanks for working on this series. Tested the whole series on a mx7d-sdb and it does fix the several clk warnings that we currently have. > +static int clk_pllv3_set_rate_done(struct clk_hw *hw) > +{ > +

Re: [PATCH RFC 6/7] clk: imx: pllv3: convert to prepare_hw and set_rate_hw

2016-07-02 Thread Fabio Estevam
Hi Dong, On Wed, Jun 29, 2016 at 10:52 AM, Dong Aisheng wrote: Thanks for working on this series. Tested the whole series on a mx7d-sdb and it does fix the several clk warnings that we currently have. > +static int clk_pllv3_set_rate_done(struct clk_hw *hw) > +{ > + struct clk_pllv3

Linux 4.7: Reported regressions as of Saturday, 2016-07-02

2016-07-02 Thread Thorsten Leemhuis
Hi! Here is my fourth regression report for Linux 4.7; a day earlier then usual. It has 14 entries; * 2 of them are new * 9 regressions (not included here) were fixed since the last report(¹) * 1 made it to the list after last Sunday (thx for telling me about it Kalle!), but was fixed before

Re: [PATCH 1/2] iio: sun4i-lradc: Add binding documentation

2016-07-02 Thread Hans de Goede
Hi, On 02-07-16 15:35, Alexandre Belloni wrote: On 02/07/2016 at 17:12:55 +0800, Chen-Yu Tsai wrote : Hi, On Sat, Jul 2, 2016 at 5:00 AM, Alexandre Belloni wrote: Document the bindings for the Allwinner LRADC. We already have

Linux 4.7: Reported regressions as of Saturday, 2016-07-02

2016-07-02 Thread Thorsten Leemhuis
Hi! Here is my fourth regression report for Linux 4.7; a day earlier then usual. It has 14 entries; * 2 of them are new * 9 regressions (not included here) were fixed since the last report(¹) * 1 made it to the list after last Sunday (thx for telling me about it Kalle!), but was fixed before

Re: [PATCH 1/2] iio: sun4i-lradc: Add binding documentation

2016-07-02 Thread Hans de Goede
Hi, On 02-07-16 15:35, Alexandre Belloni wrote: On 02/07/2016 at 17:12:55 +0800, Chen-Yu Tsai wrote : Hi, On Sat, Jul 2, 2016 at 5:00 AM, Alexandre Belloni wrote: Document the bindings for the Allwinner LRADC. We already have Documentation/devicetree/bindings/input/sun4i-lradc-keys.txt

Re: [PATCH 2/2] Input-at32psif: Remove OOM messages in psif_probe()

2016-07-02 Thread Julia Lawall
On Sat, 2 Jul 2016, SF Markus Elfring wrote: > From: Markus Elfring > Date: Sat, 2 Jul 2016 20:34:18 +0200 > > Delete two debug messages because Linux will usually provide > an appropriate information for a memory allocation failure. > > Signed-off-by: Markus

Re: [PATCH 2/2] Input-at32psif: Remove OOM messages in psif_probe()

2016-07-02 Thread Julia Lawall
On Sat, 2 Jul 2016, SF Markus Elfring wrote: > From: Markus Elfring > Date: Sat, 2 Jul 2016 20:34:18 +0200 > > Delete two debug messages because Linux will usually provide > an appropriate information for a memory allocation failure. > > Signed-off-by: Markus Elfring > --- >

[PATCH 2/2] Input-at32psif: Remove OOM messages in psif_probe()

2016-07-02 Thread SF Markus Elfring
From: Markus Elfring Date: Sat, 2 Jul 2016 20:34:18 +0200 Delete two debug messages because Linux will usually provide an appropriate information for a memory allocation failure. Signed-off-by: Markus Elfring ---

[PATCH 2/2] Input-at32psif: Remove OOM messages in psif_probe()

2016-07-02 Thread SF Markus Elfring
From: Markus Elfring Date: Sat, 2 Jul 2016 20:34:18 +0200 Delete two debug messages because Linux will usually provide an appropriate information for a memory allocation failure. Signed-off-by: Markus Elfring --- drivers/input/serio/at32psif.c | 6 ++ 1 file changed, 2 insertions(+), 4

[PATCH 1/2] Input-at32psif: Return directly after a failed kzalloc() in psif_probe()

2016-07-02 Thread SF Markus Elfring
From: Markus Elfring Date: Sat, 2 Jul 2016 18:34:43 +0200 Return directly after a memory allocation failed at the beginning. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

[PATCH 1/2] Input-at32psif: Return directly after a failed kzalloc() in psif_probe()

2016-07-02 Thread SF Markus Elfring
From: Markus Elfring Date: Sat, 2 Jul 2016 18:34:43 +0200 Return directly after a memory allocation failed at the beginning. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring --- drivers/input/serio/at32psif.c | 4 +--- 1 file changed, 1 insertion(+), 3

Re: [PATCHv3] mvsas:Fix possible NULL pointer deference in mvs_dev_found_notify

2016-07-02 Thread James Bottomley
On Sat, 2016-07-02 at 19:16 +0100, Luis de Bethencourt wrote: > On 02/07/16 18:00, Nicholas Krause wrote: > > This adds properly checking after the call to mvs_find_dev_mvi > > due to this function being able to return a NULL pointer and > > if this does arise we will deference it in

Re: [PATCHv3] mvsas:Fix possible NULL pointer deference in mvs_dev_found_notify

2016-07-02 Thread James Bottomley
On Sat, 2016-07-02 at 19:16 +0100, Luis de Bethencourt wrote: > On 02/07/16 18:00, Nicholas Krause wrote: > > This adds properly checking after the call to mvs_find_dev_mvi > > due to this function being able to return a NULL pointer and > > if this does arise we will deference it in

[PATCH 0/2] Input-at32psif: Fine-tuning for OOM handling in psif_probe()

2016-07-02 Thread SF Markus Elfring
From: Markus Elfring Date: Sat, 2 Jul 2016 20:50:09 +0200 A few update suggestions were taken into account from static source code analysis. Markus Elfring (2): Return directly after a failed kzalloc() Remove two OOM messages drivers/input/serio/at32psif.c |

[PATCH 0/2] Input-at32psif: Fine-tuning for OOM handling in psif_probe()

2016-07-02 Thread SF Markus Elfring
From: Markus Elfring Date: Sat, 2 Jul 2016 20:50:09 +0200 A few update suggestions were taken into account from static source code analysis. Markus Elfring (2): Return directly after a failed kzalloc() Remove two OOM messages drivers/input/serio/at32psif.c | 10 +++--- 1 file changed,

Re: [PATCH 1/2] net: ethernet: davinci_emac: use phydev from struct net_device

2016-07-02 Thread David Miller
From: Philippe Reynes Date: Sat, 2 Jul 2016 00:02:34 +0200 > The private structure contain a pointer to phydev, but the structure > net_device already contain such pointer. So we can remove the pointer > phy in the private structure, and update the driver to use the > one

Re: [PATCH 2/2] net: ethernet: davinci_emac: use phy_ethtool_{get|set}_link_ksettings

2016-07-02 Thread David Miller
From: Philippe Reynes Date: Sat, 2 Jul 2016 00:02:35 +0200 > There are two generics functions phy_ethtool_{get|set}_link_ksettings, > so we can use them instead of defining the same code in the driver. > > Signed-off-by: Philippe Reynes Applied.

Re: [PATCH] Fix race condition in enc28j60 driver

2016-07-02 Thread David Miller
From: Sergio Valverde < sergio.valve...@hpe.com > Date: Fri, 1 Jul 2016 11:44:30 -0600 > From: Sergio Valverde > > The interrupt worker code for the enc28j60 relies only on the TXIF flag to > determinate if the packet transmission was completed. However the datasheet >

Re: [PATCH 1/2] net: ethernet: davinci_emac: use phydev from struct net_device

2016-07-02 Thread David Miller
From: Philippe Reynes Date: Sat, 2 Jul 2016 00:02:34 +0200 > The private structure contain a pointer to phydev, but the structure > net_device already contain such pointer. So we can remove the pointer > phy in the private structure, and update the driver to use the > one contained in struct

Re: [PATCH 2/2] net: ethernet: davinci_emac: use phy_ethtool_{get|set}_link_ksettings

2016-07-02 Thread David Miller
From: Philippe Reynes Date: Sat, 2 Jul 2016 00:02:35 +0200 > There are two generics functions phy_ethtool_{get|set}_link_ksettings, > so we can use them instead of defining the same code in the driver. > > Signed-off-by: Philippe Reynes Applied.

Re: [PATCH] Fix race condition in enc28j60 driver

2016-07-02 Thread David Miller
From: Sergio Valverde < sergio.valve...@hpe.com > Date: Fri, 1 Jul 2016 11:44:30 -0600 > From: Sergio Valverde > > The interrupt worker code for the enc28j60 relies only on the TXIF flag to > determinate if the packet transmission was completed. However the datasheet > specifies in section

[PATCH] clk: imx7d: do not set parent of ethernet time clocks

2016-07-02 Thread Stefan Agner
All device trees currently in mainline specify the time clock parent using the assigned-clocks/assigned-clock-parents method, there is no need to statically assign the parent in the core clock driver. Furthermore, and the actual driver of this patch, specify parents at that early point in boot

[PATCH] clk: imx7d: do not set parent of ethernet time clocks

2016-07-02 Thread Stefan Agner
All device trees currently in mainline specify the time clock parent using the assigned-clocks/assigned-clock-parents method, there is no need to statically assign the parent in the core clock driver. Furthermore, and the actual driver of this patch, specify parents at that early point in boot

Re: [PATCH v4 10/29] x86/die: Don't try to recover from an OOPS on a non-default stack

2016-07-02 Thread Josh Poimboeuf
On Sat, Jul 02, 2016 at 07:24:41PM +0200, Borislav Petkov wrote: > On Sun, Jun 26, 2016 at 02:55:32PM -0700, Andy Lutomirski wrote: > > It's not going to work, because the scheduler will explode if we try > > to schedule when running on an IST stack or similar. > > > > This will matter when we

Re: [PATCH v4 10/29] x86/die: Don't try to recover from an OOPS on a non-default stack

2016-07-02 Thread Josh Poimboeuf
On Sat, Jul 02, 2016 at 07:24:41PM +0200, Borislav Petkov wrote: > On Sun, Jun 26, 2016 at 02:55:32PM -0700, Andy Lutomirski wrote: > > It's not going to work, because the scheduler will explode if we try > > to schedule when running on an IST stack or similar. > > > > This will matter when we

Re: [PATCHv3] mvsas:Fix possible NULL pointer deference in mvs_dev_found_notify

2016-07-02 Thread Luis de Bethencourt
On 02/07/16 18:00, Nicholas Krause wrote: > This adds properly checking after the call to mvs_find_dev_mvi > due to this function being able to return a NULL pointer and > if this does arise we will deference it in mvs_alloc_dev due > to this function never checking if a NULL pointer is given as

Re: [PATCHv3] mvsas:Fix possible NULL pointer deference in mvs_dev_found_notify

2016-07-02 Thread Luis de Bethencourt
On 02/07/16 18:00, Nicholas Krause wrote: > This adds properly checking after the call to mvs_find_dev_mvi > due to this function being able to return a NULL pointer and > if this does arise we will deference it in mvs_alloc_dev due > to this function never checking if a NULL pointer is given as

[PATCH 2/2] net: ethernet: arc: emac: use phy_ethtool_{get|set}_link_ksettings

2016-07-02 Thread Philippe Reynes
There are two generics functions phy_ethtool_{get|set}_link_ksettings, so we can use them instead of defining the same code in the driver. Signed-off-by: Philippe Reynes --- drivers/net/ethernet/arc/emac_main.c | 40 + 1 files changed, 2

[PATCH 2/2] net: ethernet: arc: emac: use phy_ethtool_{get|set}_link_ksettings

2016-07-02 Thread Philippe Reynes
There are two generics functions phy_ethtool_{get|set}_link_ksettings, so we can use them instead of defining the same code in the driver. Signed-off-by: Philippe Reynes --- drivers/net/ethernet/arc/emac_main.c | 40 + 1 files changed, 2 insertions(+), 38

[PATCH 1/2] net: ethernet: arc: emac: use phydev from struct net_device

2016-07-02 Thread Philippe Reynes
The private structure contain a pointer to phydev, but the structure net_device already contain such pointer. So we can remove the pointer phy in the private structure, and update the driver to use the one contained in struct net_device. Signed-off-by: Philippe Reynes ---

[PATCH 1/2] net: ethernet: arc: emac: use phydev from struct net_device

2016-07-02 Thread Philippe Reynes
The private structure contain a pointer to phydev, but the structure net_device already contain such pointer. So we can remove the pointer phy in the private structure, and update the driver to use the one contained in struct net_device. Signed-off-by: Philippe Reynes ---

Re: [PATCH v5 2/3] LSM: module hierarchy in /proc/.../attr

2016-07-02 Thread John Johansen
On 06/29/2016 10:03 AM, Paul Moore wrote: > On Fri, Jun 24, 2016 at 7:29 PM, Casey Schaufler > wrote: >> Subject: [PATCH v5 2/3] LSM: module hierarchy in /proc/.../attr >> >> Back in 2007 I made what turned out to be a rather serious >> mistake in the implementation of

Re: [PATCH v5 2/3] LSM: module hierarchy in /proc/.../attr

2016-07-02 Thread John Johansen
On 06/29/2016 10:03 AM, Paul Moore wrote: > On Fri, Jun 24, 2016 at 7:29 PM, Casey Schaufler > wrote: >> Subject: [PATCH v5 2/3] LSM: module hierarchy in /proc/.../attr >> >> Back in 2007 I made what turned out to be a rather serious >> mistake in the implementation of the Smack security module.

Re: [PATCH v4 10/29] x86/die: Don't try to recover from an OOPS on a non-default stack

2016-07-02 Thread Borislav Petkov
On Sun, Jun 26, 2016 at 02:55:32PM -0700, Andy Lutomirski wrote: > It's not going to work, because the scheduler will explode if we try > to schedule when running on an IST stack or similar. > > This will matter when we let kernel stack overflows (which are #DF) > call die(). > > Signed-off-by:

Re: [PATCH v4 3/3] LSM: Add context interface for proc attrs

2016-07-02 Thread John Johansen
On 06/29/2016 10:04 AM, Paul Moore wrote: > On Fri, Jun 24, 2016 at 7:29 PM, Casey Schaufler > wrote: >> Subject: [PATCH v4 3/3] LSM: Add context interface for proc attrs >> >> The /proc/.../attr/current interface is used by all three >> Linux security modules (SELinux,

Re: [PATCH v4 10/29] x86/die: Don't try to recover from an OOPS on a non-default stack

2016-07-02 Thread Borislav Petkov
On Sun, Jun 26, 2016 at 02:55:32PM -0700, Andy Lutomirski wrote: > It's not going to work, because the scheduler will explode if we try > to schedule when running on an IST stack or similar. > > This will matter when we let kernel stack overflows (which are #DF) > call die(). > > Signed-off-by:

Re: [PATCH v4 3/3] LSM: Add context interface for proc attrs

2016-07-02 Thread John Johansen
On 06/29/2016 10:04 AM, Paul Moore wrote: > On Fri, Jun 24, 2016 at 7:29 PM, Casey Schaufler > wrote: >> Subject: [PATCH v4 3/3] LSM: Add context interface for proc attrs >> >> The /proc/.../attr/current interface is used by all three >> Linux security modules (SELinux, Smack and AppArmor) to >>

Re: [PATCH v5 1/3] LSM: Add /sys/kernel/security/lsm

2016-07-02 Thread John Johansen
On 06/29/2016 10:01 AM, Paul Moore wrote: > On Fri, Jun 24, 2016 at 7:27 PM, Casey Schaufler > wrote: >> Subject: [PATCH v5 1/3] LSM: Add /sys/kernel/security/lsm >> >> I got tired of having to find indirect ways to >> determine what security modules are active on a

Re: [PATCH v5 1/3] LSM: Add /sys/kernel/security/lsm

2016-07-02 Thread John Johansen
On 06/29/2016 10:01 AM, Paul Moore wrote: > On Fri, Jun 24, 2016 at 7:27 PM, Casey Schaufler > wrote: >> Subject: [PATCH v5 1/3] LSM: Add /sys/kernel/security/lsm >> >> I got tired of having to find indirect ways to >> determine what security modules are active on a system. >> I have added

Re: EXT: Re: [PATCH RFC 1/4] dma: imx-sdma - reduce transfer latency for DMA cyclic clients

2016-07-02 Thread Vinod Koul
On Fri, Jul 01, 2016 at 05:59:30PM +0300, Nandor Han wrote: > > > On 28/06/16 17:34, Vinod Koul wrote: > >On Thu, Jun 09, 2016 at 03:16:30PM +0300, Nandor Han wrote: > >>Having the SDMA driver use a tasklet for running the clients > >>callback introduce some issues: > >> - probability to have

Re: EXT: Re: [PATCH RFC 1/4] dma: imx-sdma - reduce transfer latency for DMA cyclic clients

2016-07-02 Thread Vinod Koul
On Fri, Jul 01, 2016 at 05:59:30PM +0300, Nandor Han wrote: > > > On 28/06/16 17:34, Vinod Koul wrote: > >On Thu, Jun 09, 2016 at 03:16:30PM +0300, Nandor Han wrote: > >>Having the SDMA driver use a tasklet for running the clients > >>callback introduce some issues: > >> - probability to have

Re: [PATCH v2 02/15] [media] lirc_dev: allow bufferless driver registration

2016-07-02 Thread Sean Young
On Fri, Jul 01, 2016 at 05:01:25PM +0900, Andi Shyti wrote: > Some drivers don't necessarily need to have a FIFO managed buffer > for their transfers. Drivers now should call > lirc_register_bufferless_driver in order to handle the buffer > themselves. > > The function works exaclty like

Re: [PATCH v2 02/15] [media] lirc_dev: allow bufferless driver registration

2016-07-02 Thread Sean Young
On Fri, Jul 01, 2016 at 05:01:25PM +0900, Andi Shyti wrote: > Some drivers don't necessarily need to have a FIFO managed buffer > for their transfers. Drivers now should call > lirc_register_bufferless_driver in order to handle the buffer > themselves. > > The function works exaclty like

[RFC PATCH] dt/bindings: Add bindings for JC-42.4 compatible temperature sensors

2016-07-02 Thread Guenter Roeck
Provide generic bindings for all Jedec JC-42.4 compatible temperature sensor chips. Signed-off-by: Guenter Roeck --- RFC to address: - Is "jc-42-4" ok to use for JC-42.4 ? - JC42.4 really specifies an SPD EEPROM with included temperature sensor. Is "jedec,jc42-4"

[RFC PATCH] dt/bindings: Add bindings for JC-42.4 compatible temperature sensors

2016-07-02 Thread Guenter Roeck
Provide generic bindings for all Jedec JC-42.4 compatible temperature sensor chips. Signed-off-by: Guenter Roeck --- RFC to address: - Is "jc-42-4" ok to use for JC-42.4 ? - JC42.4 really specifies an SPD EEPROM with included temperature sensor. Is "jedec,jc42-4" appropriate, or should it

Re: [PATCH v7 4/4] soc: mediatek: Add MT2701 scpsys driver

2016-07-02 Thread Matthias Brugger
On 05/16/2016 11:28 AM, James Liao wrote: From: Shunli Wang Add scpsys driver for MT2701. mtk-scpsys now supports MT8173 (arm64) and MT2701 (arm). So it should be enabled on both arm64 and arm platforms. Signed-off-by: Shunli Wang

Re: [PATCH v7 4/4] soc: mediatek: Add MT2701 scpsys driver

2016-07-02 Thread Matthias Brugger
On 05/16/2016 11:28 AM, James Liao wrote: From: Shunli Wang Add scpsys driver for MT2701. mtk-scpsys now supports MT8173 (arm64) and MT2701 (arm). So it should be enabled on both arm64 and arm platforms. Signed-off-by: Shunli Wang Signed-off-by: James Liao Reviewed-by: Kevin Hilman ---

Re: [PATCH] perf: fix pmu::filter_match for SW-led groups

2016-07-02 Thread Peter Zijlstra
On Tue, Jun 14, 2016 at 04:10:41PM +0100, Mark Rutland wrote: > However, pmu::filter_match is only called for the leader of each event > group. When the leader is a SW event, we do not filter the groups, and > may fail at pmu::add time, and when this happens we'll give up on > scheduling any event

Re: [PATCH] perf: fix pmu::filter_match for SW-led groups

2016-07-02 Thread Peter Zijlstra
On Tue, Jun 14, 2016 at 04:10:41PM +0100, Mark Rutland wrote: > However, pmu::filter_match is only called for the leader of each event > group. When the leader is a SW event, we do not filter the groups, and > may fail at pmu::add time, and when this happens we'll give up on > scheduling any event

Re: [PATCH v7 2/4] soc: mediatek: Init MT8173 scpsys driver earlier

2016-07-02 Thread Matthias Brugger
On 05/16/2016 11:28 AM, James Liao wrote: Some power domain comsumers may init before module_init. So the power domain provider (scpsys) need to be initialized earlier too. Take an example for our IOMMU (M4U) and SMI. SMI is a bridge between IOMMU and multimedia HW. SMI is responsible to

Re: [PATCH v7 2/4] soc: mediatek: Init MT8173 scpsys driver earlier

2016-07-02 Thread Matthias Brugger
On 05/16/2016 11:28 AM, James Liao wrote: Some power domain comsumers may init before module_init. So the power domain provider (scpsys) need to be initialized earlier too. Take an example for our IOMMU (M4U) and SMI. SMI is a bridge between IOMMU and multimedia HW. SMI is responsible to

Re: [PATCH v7 1/4] soc: mediatek: Refine scpsys to support multiple platform

2016-07-02 Thread Matthias Brugger
On 05/16/2016 11:28 AM, James Liao wrote: Refine scpsys driver common code to support multiple SoC / platform. Signed-off-by: James Liao Reviewed-by: Kevin Hilman --- drivers/soc/mediatek/mtk-scpsys.c | 363

Re: [PATCH v7 1/4] soc: mediatek: Refine scpsys to support multiple platform

2016-07-02 Thread Matthias Brugger
On 05/16/2016 11:28 AM, James Liao wrote: Refine scpsys driver common code to support multiple SoC / platform. Signed-off-by: James Liao Reviewed-by: Kevin Hilman --- drivers/soc/mediatek/mtk-scpsys.c | 363 +++--- 1 file changed, 220 insertions(+), 143

[PATCH 1/3] mm/page_owner: rename page_owner functions

2016-07-02 Thread Sergey Senozhatsky
A cosmetic change: rename set_page_owner() and reset_page_owner() functions to page_owner_alloc_pages()/page_owner_free_pages(). This is sort of a preparation step for PAGE_OWNER_TRACK_FREE patch. Signed-off-by: Sergey Senozhatsky --- include/linux/page_owner.h |

[PATCH 1/3] mm/page_owner: rename page_owner functions

2016-07-02 Thread Sergey Senozhatsky
A cosmetic change: rename set_page_owner() and reset_page_owner() functions to page_owner_alloc_pages()/page_owner_free_pages(). This is sort of a preparation step for PAGE_OWNER_TRACK_FREE patch. Signed-off-by: Sergey Senozhatsky --- include/linux/page_owner.h | 16

[PATCH 3/3] mm/page_owner: track page free call chain

2016-07-02 Thread Sergey Senozhatsky
Introduce PAGE_OWNER_TRACK_FREE config option to extend page owner with free_pages() tracking functionality. This adds to the dump_page_owner() output an additional backtrace, that tells us what path has freed the page. Aa a trivial example, let's assume that do_some_foo() has an error - extra

[PATCH 3/3] mm/page_owner: track page free call chain

2016-07-02 Thread Sergey Senozhatsky
Introduce PAGE_OWNER_TRACK_FREE config option to extend page owner with free_pages() tracking functionality. This adds to the dump_page_owner() output an additional backtrace, that tells us what path has freed the page. Aa a trivial example, let's assume that do_some_foo() has an error - extra

[PATCH 2/3] mm/page_owner: rename PAGE_EXT_OWNER flag

2016-07-02 Thread Sergey Senozhatsky
A cosmetic change: PAGE_OWNER_TRACK_FREE will introduce one more page_owner flag: PAGE_EXT_OWNER_FREE. To make names symmetrical, rename PAGE_EXT_OWNER to PAGE_EXT_OWNER_ALLOC. Signed-off-by: Sergey Senozhatsky --- include/linux/page_ext.h | 2 +- mm/page_owner.c

[PATCH 0/3][RFC] mm/page:_owner: track page free call chain

2016-07-02 Thread Sergey Senozhatsky
Hello, RFC Page owner tracks a call chain that has allocated a page, this patch set extends it with a PAGE_OWNER_TRACK_FREE functionality, that now also tracks a call chain that has freed the page. Page dump, thus, now has the following format: a) page allocated backtrace

[PATCH 2/3] mm/page_owner: rename PAGE_EXT_OWNER flag

2016-07-02 Thread Sergey Senozhatsky
A cosmetic change: PAGE_OWNER_TRACK_FREE will introduce one more page_owner flag: PAGE_EXT_OWNER_FREE. To make names symmetrical, rename PAGE_EXT_OWNER to PAGE_EXT_OWNER_ALLOC. Signed-off-by: Sergey Senozhatsky --- include/linux/page_ext.h | 2 +- mm/page_owner.c | 12 ++--

[PATCH 0/3][RFC] mm/page:_owner: track page free call chain

2016-07-02 Thread Sergey Senozhatsky
Hello, RFC Page owner tracks a call chain that has allocated a page, this patch set extends it with a PAGE_OWNER_TRACK_FREE functionality, that now also tracks a call chain that has freed the page. Page dump, thus, now has the following format: a) page allocated backtrace

Re: [PATCH] regulator: pwm: Fix regulator ramp delay for continuous mode

2016-07-02 Thread Boris Brezillon
+Thierry Hi Doug, On Fri, 1 Jul 2016 13:17:48 -0700 Doug Anderson wrote: > Mark, > > On Fri, Jul 1, 2016 at 1:06 AM, Mark Brown wrote: > > On Mon, Jun 27, 2016 at 09:53:11PM -0700, Douglas Anderson wrote: > > > >> Note that this patch is atop

Re: [PATCH] regulator: pwm: Fix regulator ramp delay for continuous mode

2016-07-02 Thread Boris Brezillon
+Thierry Hi Doug, On Fri, 1 Jul 2016 13:17:48 -0700 Doug Anderson wrote: > Mark, > > On Fri, Jul 1, 2016 at 1:06 AM, Mark Brown wrote: > > On Mon, Jun 27, 2016 at 09:53:11PM -0700, Douglas Anderson wrote: > > > >> Note that this patch is atop Boris's recent PWM regulator fixes. If > >>

Re: [Nouveau] [PATCH 2/6] drm/nouveau/core: make use of new strtolower() function

2016-07-02 Thread Markus Mayer
On 1 July 2016 at 18:18, Alexandre Courbot wrote: > On Fri, Jul 1, 2016 at 8:50 AM, Markus Mayer wrote: >> Call strtolower() rather than walking the string explicitly to convert >> it to lowercase. >> >> Signed-off-by: Markus Mayer >>

Re: [Nouveau] [PATCH 2/6] drm/nouveau/core: make use of new strtolower() function

2016-07-02 Thread Markus Mayer
On 1 July 2016 at 18:18, Alexandre Courbot wrote: > On Fri, Jul 1, 2016 at 8:50 AM, Markus Mayer wrote: >> Call strtolower() rather than walking the string explicitly to convert >> it to lowercase. >> >> Signed-off-by: Markus Mayer >> --- >> drivers/gpu/drm/nouveau/nvkm/core/firmware.c | 7

Re: [PATCH] scsi: replace broken specification URL

2016-07-02 Thread James Bottomley
On Sat, 2016-07-02 at 08:56 +0200, Michael Opdenacker wrote: > The t10.org website containing SCSI-2 draft specifications now > requires to be from a member company to access the documents. > > This replaces the now broken link with another public resource > where the specifications can be

Re: [PATCH] scsi: replace broken specification URL

2016-07-02 Thread James Bottomley
On Sat, 2016-07-02 at 08:56 +0200, Michael Opdenacker wrote: > The t10.org website containing SCSI-2 draft specifications now > requires to be from a member company to access the documents. > > This replaces the now broken link with another public resource > where the specifications can be

Re: [PATCH 1/4] fs: befs: Remove redundant validation from befs_find_brun_direct

2016-07-02 Thread Luis de Bethencourt
On 02/07/16 14:34, Salah Triki wrote: > On Sat, Jul 02, 2016 at 12:38:18PM +0100, Luis de Bethencourt wrote: >> On 02/07/16 09:05, Salah Triki wrote: >>> The only caller of befs_find_brun_direct is befs_fblock2brun, which >>> already validates that the block is within the range of direct blocks.

Re: [PATCH 1/4] fs: befs: Remove redundant validation from befs_find_brun_direct

2016-07-02 Thread Luis de Bethencourt
On 02/07/16 14:34, Salah Triki wrote: > On Sat, Jul 02, 2016 at 12:38:18PM +0100, Luis de Bethencourt wrote: >> On 02/07/16 09:05, Salah Triki wrote: >>> The only caller of befs_find_brun_direct is befs_fblock2brun, which >>> already validates that the block is within the range of direct blocks.

Re: [PATCH] [media] hdpvr: Remove deprecated create_singlethread_workqueue

2016-07-02 Thread Tejun Heo
On Sat, Jul 02, 2016 at 04:17:31PM +0530, Bhaktipriya Shridhar wrote: > The workqueue "workqueue" is involved in tranmitting hdpvr buffers. > It has a single work item(>worker) and hence doesn't require > ordering. Also, it is not being used on a memory reclaim path. Hence, > the singlethreaded

Re: [PATCH] [media] hdpvr: Remove deprecated create_singlethread_workqueue

2016-07-02 Thread Tejun Heo
On Sat, Jul 02, 2016 at 04:17:31PM +0530, Bhaktipriya Shridhar wrote: > The workqueue "workqueue" is involved in tranmitting hdpvr buffers. > It has a single work item(>worker) and hence doesn't require > ordering. Also, it is not being used on a memory reclaim path. Hence, > the singlethreaded

Re: [PATCH 1/4] fs: befs: Remove redundant validation from befs_find_brun_direct

2016-07-02 Thread Salah Triki
On Sat, Jul 02, 2016 at 12:38:18PM +0100, Luis de Bethencourt wrote: > On 02/07/16 09:05, Salah Triki wrote: > > The only caller of befs_find_brun_direct is befs_fblock2brun, which > > already validates that the block is within the range of direct blocks. > > So remove the duplicate validation. >

Re: [PATCH 1/4] fs: befs: Remove redundant validation from befs_find_brun_direct

2016-07-02 Thread Salah Triki
On Sat, Jul 02, 2016 at 12:38:18PM +0100, Luis de Bethencourt wrote: > On 02/07/16 09:05, Salah Triki wrote: > > The only caller of befs_find_brun_direct is befs_fblock2brun, which > > already validates that the block is within the range of direct blocks. > > So remove the duplicate validation. >

Re: [PATCH] drm/radeon: Remove deprecated create_singlethread_workqueue

2016-07-02 Thread Tejun Heo
On Sat, Jul 02, 2016 at 04:33:50PM +0530, Bhaktipriya Shridhar wrote: > alloc_workqueue replaces deprecated create_singlethread_workqueue(). > > A dedicated workqueue has been used since work items need to be flushed > as a group rather than individually. > > Since the flip_queue workqueue is

Re: [PATCH] drm/radeon: Remove deprecated create_singlethread_workqueue

2016-07-02 Thread Tejun Heo
On Sat, Jul 02, 2016 at 04:33:50PM +0530, Bhaktipriya Shridhar wrote: > alloc_workqueue replaces deprecated create_singlethread_workqueue(). > > A dedicated workqueue has been used since work items need to be flushed > as a group rather than individually. > > Since the flip_queue workqueue is

Re: [PATCH 1/2] iio: sun4i-lradc: Add binding documentation

2016-07-02 Thread Maxime Ripard
On Sat, Jul 02, 2016 at 03:32:43PM +0200, Alexandre Belloni wrote: > > > > I believe that the best way to deal with this is to add an > > > > "allwinner,general-purpose-mode" flag to the existing binding > > > > (as well as document general purpose mode in the existing > > > > binding rather then

Re: [PATCH 1/2] iio: sun4i-lradc: Add binding documentation

2016-07-02 Thread Maxime Ripard
On Sat, Jul 02, 2016 at 03:32:43PM +0200, Alexandre Belloni wrote: > > > > I believe that the best way to deal with this is to add an > > > > "allwinner,general-purpose-mode" flag to the existing binding > > > > (as well as document general purpose mode in the existing > > > > binding rather then

Re: [PATCH] drm/qxl: Remove deprecated create_singlethread_workqueue

2016-07-02 Thread Tejun Heo
On Sat, Jul 02, 2016 at 04:32:09PM +0530, Bhaktipriya Shridhar wrote: > System workqueues have been able to handle high level of concurrency > for a long time now and there's no reason to use dedicated workqueues > just to gain concurrency. Since the workqueue in the QXL graphics device > driver

Re: [PATCH] drm/qxl: Remove deprecated create_singlethread_workqueue

2016-07-02 Thread Tejun Heo
On Sat, Jul 02, 2016 at 04:32:09PM +0530, Bhaktipriya Shridhar wrote: > System workqueues have been able to handle high level of concurrency > for a long time now and there's no reason to use dedicated workqueues > just to gain concurrency. Since the workqueue in the QXL graphics device > driver

Re: [PATCH] [media] tc358743: Remove deprecated create_singlethread_workqueue

2016-07-02 Thread Tejun Heo
On Sat, Jul 02, 2016 at 04:11:53PM +0530, Bhaktipriya Shridhar wrote: > The workqueue "work_queues" enables hotplugging. > It has a single work item(>delayed_work_enable_hotplug) and hence > doesn't require ordering. Also, it is not being used on a memory > reclaim path. Hence, the singlethreaded

Re: [PATCH] [media] tc358743: Remove deprecated create_singlethread_workqueue

2016-07-02 Thread Tejun Heo
On Sat, Jul 02, 2016 at 04:11:53PM +0530, Bhaktipriya Shridhar wrote: > The workqueue "work_queues" enables hotplugging. > It has a single work item(>delayed_work_enable_hotplug) and hence > doesn't require ordering. Also, it is not being used on a memory > reclaim path. Hence, the singlethreaded

Re: [PATCH] [media] sn9c20x: Remove deprecated create_singlethread_workqueue

2016-07-02 Thread Tejun Heo
On Sat, Jul 02, 2016 at 04:21:22PM +0530, Bhaktipriya Shridhar wrote: > The workqueue "work_thread" is involved in JPEG quality update. > It has a single work item(>work) and hence doesn't require ordering. > Also, it is not being used on a memory reclaim path. Hence, the > singlethreaded

Re: [PATCH] [media] sn9c20x: Remove deprecated create_singlethread_workqueue

2016-07-02 Thread Tejun Heo
On Sat, Jul 02, 2016 at 04:21:22PM +0530, Bhaktipriya Shridhar wrote: > The workqueue "work_thread" is involved in JPEG quality update. > It has a single work item(>work) and hence doesn't require ordering. > Also, it is not being used on a memory reclaim path. Hence, the > singlethreaded

Re: [PATCH] [media] zc3xx: Remove deprecated create_singlethread_workqueue

2016-07-02 Thread Tejun Heo
On Sat, Jul 02, 2016 at 04:19:28PM +0530, Bhaktipriya Shridhar wrote: > The workqueue "work_thread" is involved in updating parameters for > transfers. It has a single work item(>work) and hence > doesn't require ordering. Also, it is not being used on a memory > reclaim path. Hence, the

Re: [PATCH] [media] zc3xx: Remove deprecated create_singlethread_workqueue

2016-07-02 Thread Tejun Heo
On Sat, Jul 02, 2016 at 04:19:28PM +0530, Bhaktipriya Shridhar wrote: > The workqueue "work_thread" is involved in updating parameters for > transfers. It has a single work item(>work) and hence > doesn't require ordering. Also, it is not being used on a memory > reclaim path. Hence, the

Re: [PATCH 1/2] iio: sun4i-lradc: Add binding documentation

2016-07-02 Thread Alexandre Belloni
On 02/07/2016 at 17:12:55 +0800, Chen-Yu Tsai wrote : > Hi, > > On Sat, Jul 2, 2016 at 5:00 AM, Alexandre Belloni > wrote: > > Document the bindings for the Allwinner LRADC. > > We already have Documentation/devicetree/bindings/input/sun4i-lradc-keys.txt >

Re: [PATCH 1/2] iio: sun4i-lradc: Add binding documentation

2016-07-02 Thread Alexandre Belloni
On 02/07/2016 at 17:12:55 +0800, Chen-Yu Tsai wrote : > Hi, > > On Sat, Jul 2, 2016 at 5:00 AM, Alexandre Belloni > wrote: > > Document the bindings for the Allwinner LRADC. > > We already have Documentation/devicetree/bindings/input/sun4i-lradc-keys.txt > and I'm pretty sure Hans (CC-ed)

Re: [PATCH 1/2] iio: sun4i-lradc: Add binding documentation

2016-07-02 Thread Alexandre Belloni
On 02/07/2016 at 13:45:18 +0200, Hans de Goede wrote : > Hi, > > On 02-07-16 13:02, Maxime Ripard wrote: > > On Sat, Jul 02, 2016 at 11:32:07AM +0200, Hans de Goede wrote: > > > Hi, > > > > > > On 02-07-16 11:12, Chen-Yu Tsai wrote: > > > > Hi, > > > > > > > > On Sat, Jul 2, 2016 at 5:00 AM,

Re: [PATCH 1/2] iio: sun4i-lradc: Add binding documentation

2016-07-02 Thread Alexandre Belloni
On 02/07/2016 at 13:45:18 +0200, Hans de Goede wrote : > Hi, > > On 02-07-16 13:02, Maxime Ripard wrote: > > On Sat, Jul 02, 2016 at 11:32:07AM +0200, Hans de Goede wrote: > > > Hi, > > > > > > On 02-07-16 11:12, Chen-Yu Tsai wrote: > > > > Hi, > > > > > > > > On Sat, Jul 2, 2016 at 5:00 AM,

<    1   2   3   4   >