Re: [PATCH v5 2/2] staging: ion: create one device entry per heap

On 10/05/2017 06:06 AM, Benjamin Gaignard wrote: > 2017-10-04 12:17 GMT+02:00 Mark Brown : >> On Tue, Oct 03, 2017 at 04:08:30PM -0700, Sandeep Patil wrote: >> >>> It is entirely possible and easy in android/ueventd to create those nodes >>> under "/dev/ion/". (assuming the

Re: [PATCH v5 2/2] staging: ion: create one device entry per heap

On 10/05/2017 06:06 AM, Benjamin Gaignard wrote: > 2017-10-04 12:17 GMT+02:00 Mark Brown : >> On Tue, Oct 03, 2017 at 04:08:30PM -0700, Sandeep Patil wrote: >> >>> It is entirely possible and easy in android/ueventd to create those nodes >>> under "/dev/ion/". (assuming the heap 'subsystem' for

Re: [PATCH 1/2] crypto: lrw - Fix an error handling path in 'create()'

Am 08.10.2017 11:39, schrieb Christophe JAILLET: > All error handling paths 'goto err_drop_spawn' except this one. > In order to avoid some resources leak, we should do it as well here. > > Fixes: 700cb3f5fe75 ("crypto: lrw - Convert to skcipher") > Signed-off-by: Christophe JAILLET

Re: [PATCH 1/2] crypto: lrw - Fix an error handling path in 'create()'

Am 08.10.2017 11:39, schrieb Christophe JAILLET: > All error handling paths 'goto err_drop_spawn' except this one. > In order to avoid some resources leak, we should do it as well here. > > Fixes: 700cb3f5fe75 ("crypto: lrw - Convert to skcipher") > Signed-off-by: Christophe JAILLET > --- >

Re: [PATCH v2 15/16] gpio: tegra: Use banked GPIO infrastructure

On 09/28/2017 04:56 AM, Thierry Reding wrote: > From: Thierry Reding > > Convert the Tegra GPIO driver to use the banked GPIO infrastructure, > which simplifies some parts of the driver. > > Signed-off-by: Thierry Reding > --- > drivers/gpio/Kconfig

Re: [PATCH v2 15/16] gpio: tegra: Use banked GPIO infrastructure

On 09/28/2017 04:56 AM, Thierry Reding wrote: > From: Thierry Reding > > Convert the Tegra GPIO driver to use the banked GPIO infrastructure, > which simplifies some parts of the driver. > > Signed-off-by: Thierry Reding > --- > drivers/gpio/Kconfig | 1 + >

linux-next: Tree for Oct 9th

For my birthday I've gone and got myself a linux-next tree: Changes since 20170929: The net-next and drm trees lost their build failures but the rcu tree gained one. I have created today's linux-next tree at git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git (patches at

linux-next: Tree for Oct 9th

For my birthday I've gone and got myself a linux-next tree: Changes since 20170929: The net-next and drm trees lost their build failures but the rcu tree gained one. I have created today's linux-next tree at git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git (patches at

null dereference in binfmt misc

Hi, It looks like eb23aa031 ("exec: binfmt_misc: remove the confusing e->interp_file != NULL checks") uncovered a bug for me (see the trace below, which I'm afraid isn't very helpful). I have a fairly reliable reproducer, but before I dig in, I figured I'd ping and see if anyone has any pointers

null dereference in binfmt misc

Hi, It looks like eb23aa031 ("exec: binfmt_misc: remove the confusing e->interp_file != NULL checks") uncovered a bug for me (see the trace below, which I'm afraid isn't very helpful). I have a fairly reliable reproducer, but before I dig in, I figured I'd ping and see if anyone has any pointers

Re: [PATCH v2 0/5] Switch arm64 over to qrwlock

On 10/06/2017 09:34 AM, Will Deacon wrote: > Hi all, > > This is version two of the patches I posted yesterday: > > > http://lists.infradead.org/pipermail/linux-arm-kernel/2017-October/534666.html > > I'd normally leave it longer before posting again, but Peter had a good > suggestion to rework

Re: [PATCH v2 0/5] Switch arm64 over to qrwlock

On 10/06/2017 09:34 AM, Will Deacon wrote: > Hi all, > > This is version two of the patches I posted yesterday: > > > http://lists.infradead.org/pipermail/linux-arm-kernel/2017-October/534666.html > > I'd normally leave it longer before posting again, but Peter had a good > suggestion to rework

Re: [PATCHv2 1/1] [tools]: android/ion: userspace test utility for ion buffer sharing

On 10/09/2017 07:17 AM, Pintu Kumar wrote: > On Fri, Oct 6, 2017 at 7:58 PM, Pintu Kumar wrote: + + heap_type = ion_info->heap_type; + heap_size = ion_info->heap_size; + flag_type = ion_info->flag_type; + alloc_data.len = heap_size;

Re: [PATCHv2 1/1] [tools]: android/ion: userspace test utility for ion buffer sharing

On 10/09/2017 07:17 AM, Pintu Kumar wrote: > On Fri, Oct 6, 2017 at 7:58 PM, Pintu Kumar wrote: + + heap_type = ion_info->heap_type; + heap_size = ion_info->heap_size; + flag_type = ion_info->flag_type; + alloc_data.len = heap_size; +

[PATCH] Staging: rtlwifi: Remove NULL pointer dereference

Remove NULL pointer dereference as it results in undefined behaviour, and will usually lead to a runtime error. Signed-off-by: Shreeya Patel --- drivers/staging/rtlwifi/base.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH] Staging: rtlwifi: Remove NULL pointer dereference

Remove NULL pointer dereference as it results in undefined behaviour, and will usually lead to a runtime error. Signed-off-by: Shreeya Patel --- drivers/staging/rtlwifi/base.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/staging/rtlwifi/base.c

Re: [PATCH 3.16 000/192] 3.16.49-rc1 review

On Mon, 2017-10-09 at 13:13 -0700, Guenter Roeck wrote: > On Mon, Oct 09, 2017 at 01:44:23PM +0100, Ben Hutchings wrote: > > This is the start of the stable review cycle for the 3.16.49 release. > > There are 192 patches in this series, which will be posted as responses > > to this one. If anyone

Re: [PATCH 3.16 000/192] 3.16.49-rc1 review

On Mon, 2017-10-09 at 13:13 -0700, Guenter Roeck wrote: > On Mon, Oct 09, 2017 at 01:44:23PM +0100, Ben Hutchings wrote: > > This is the start of the stable review cycle for the 3.16.49 release. > > There are 192 patches in this series, which will be posted as responses > > to this one. If anyone

Re: [PATCH] usb: musb: sunxi: Explicitly release USB PHY on exit

Hi, On 10 October 2017 at 01:23, Bin Liu wrote: > Hi, > > On Tue, Sep 26, 2017 at 09:39:23PM +1000, Jonathan Liu wrote: >> This fixes a kernel oops when unloading the driver due to usb_put_phy >> being called after usb_phy_generic_unregister when the device is >> detached. Calling

Re: [PATCH] usb: musb: sunxi: Explicitly release USB PHY on exit

Hi, On 10 October 2017 at 01:23, Bin Liu wrote: > Hi, > > On Tue, Sep 26, 2017 at 09:39:23PM +1000, Jonathan Liu wrote: >> This fixes a kernel oops when unloading the driver due to usb_put_phy >> being called after usb_phy_generic_unregister when the device is >> detached. Calling

Re: [PATCH] once: switch to new jump label API

From: Daniel Borkmann Date: Mon, 09 Oct 2017 23:14:42 +0200 > Given original code was accepted against net-next tree as major > users of the api are networking related anyway, it should be fine > here as well to route through this tree. Maybe resend the patch with > a

Re: [PATCH] once: switch to new jump label API

From: Daniel Borkmann Date: Mon, 09 Oct 2017 23:14:42 +0200 > Given original code was accepted against net-next tree as major > users of the api are networking related anyway, it should be fine > here as well to route through this tree. Maybe resend the patch with > a [PATCH net-next] in the

Re: [ANNOUNCE] fsperf: a simple fs/block performance testing framework

On Tue, Oct 10, 2017 at 08:09:20AM +1100, Dave Chinner wrote: > On Mon, Oct 09, 2017 at 09:00:51AM -0400, Josef Bacik wrote: > > On Mon, Oct 09, 2017 at 04:17:31PM +1100, Dave Chinner wrote: > > > On Sun, Oct 08, 2017 at 10:25:10PM -0400, Josef Bacik wrote: > > > > > Integrating into fstests means

Re: [ANNOUNCE] fsperf: a simple fs/block performance testing framework

On Tue, Oct 10, 2017 at 08:09:20AM +1100, Dave Chinner wrote: > On Mon, Oct 09, 2017 at 09:00:51AM -0400, Josef Bacik wrote: > > On Mon, Oct 09, 2017 at 04:17:31PM +1100, Dave Chinner wrote: > > > On Sun, Oct 08, 2017 at 10:25:10PM -0400, Josef Bacik wrote: > > > > > Integrating into fstests means

Re: [PATCH] once: switch to new jump label API

On 10/09/2017 10:27 PM, Eric Biggers wrote: On Fri, Sep 15, 2017 at 09:07:51PM -0700, Eric Biggers wrote: On Tue, Aug 22, 2017 at 02:44:41PM -0400, Hannes Frederic Sowa wrote: Eric Biggers writes: From: Eric Biggers Switch the DO_ONCE() macro from

Re: [PATCH] once: switch to new jump label API

On 10/09/2017 10:27 PM, Eric Biggers wrote: On Fri, Sep 15, 2017 at 09:07:51PM -0700, Eric Biggers wrote: On Tue, Aug 22, 2017 at 02:44:41PM -0400, Hannes Frederic Sowa wrote: Eric Biggers writes: From: Eric Biggers Switch the DO_ONCE() macro from the deprecated jump label API to the new

[PATCH v4 2/2] pid: Remove pidhash

pidhash is no longer required as all the information can be looked up from idr tree. nr_hashed represented the number of pids that had been hashed. Since, nr_hashed and PIDNS_HASH_ADDING are no longer relevant, it has been renamed to pid_allocated and PIDNS_ADDING respectively. Signed-off-by:

[PATCH v4 2/2] pid: Remove pidhash

pidhash is no longer required as all the information can be looked up from idr tree. nr_hashed represented the number of pids that had been hashed. Since, nr_hashed and PIDNS_HASH_ADDING are no longer relevant, it has been renamed to pid_allocated and PIDNS_ADDING respectively. Signed-off-by:

[PATCH v4 1/2] pid: Replace pid bitmap implementation with IDR API

This patch replaces the current bitmap implemetation for Process ID allocation. Functions that are no longer required, for example, free_pidmap(), alloc_pidmap(), etc. are removed. The rest of the functions are modified to use the IDR API. The change was made to make the PID allocation less

[PATCH v4 1/2] pid: Replace pid bitmap implementation with IDR API

This patch replaces the current bitmap implemetation for Process ID allocation. Functions that are no longer required, for example, free_pidmap(), alloc_pidmap(), etc. are removed. The rest of the functions are modified to use the IDR API. The change was made to make the PID allocation less

[PATCH v4 0/2] Replacing PID bitmap implementation with IDR API

This patch series replaces kernel bitmap implementation of PID allocation with IDR API. These patches are written to simplify the kernel by replacing custom code with calls to generic code. The following are the stats for pid and pid_namespace object files before and after the replacement. There

[PATCH v4 0/2] Replacing PID bitmap implementation with IDR API

This patch series replaces kernel bitmap implementation of PID allocation with IDR API. These patches are written to simplify the kernel by replacing custom code with calls to generic code. The following are the stats for pid and pid_namespace object files before and after the replacement. There

Re: [PATCH 1/2] MIPS: math-emu: Update debugfs FP exception stats for certain instructions

On Fri, Oct 06, 2017 at 07:29:00PM +0200, Aleksandar Markovic wrote: > From: Aleksandar Markovic > > Fix omission of updating of debugfs FP exception stats for > instructions .. > > CLASS. can generate Unimplemented

Re: [PATCH 1/2] MIPS: math-emu: Update debugfs FP exception stats for certain instructions

On Fri, Oct 06, 2017 at 07:29:00PM +0200, Aleksandar Markovic wrote: > From: Aleksandar Markovic > > Fix omission of updating of debugfs FP exception stats for > instructions .. > > CLASS. can generate Unimplemented Operation FP exception. > >. can generate Inexact, nit: s/>>/>/ >

Re: [v11 2/6] mm: implement mem_cgroup_scan_tasks() for the root memory cgroup

On Thu, 5 Oct 2017, Roman Gushchin wrote: > Implement mem_cgroup_scan_tasks() functionality for the root > memory cgroup to use this function for looking for a OOM victim > task in the root memory cgroup by the cgroup-ware OOM killer. > > The root memory cgroup is treated as a leaf cgroup, so

Re: [v11 2/6] mm: implement mem_cgroup_scan_tasks() for the root memory cgroup

On Thu, 5 Oct 2017, Roman Gushchin wrote: > Implement mem_cgroup_scan_tasks() functionality for the root > memory cgroup to use this function for looking for a OOM victim > task in the root memory cgroup by the cgroup-ware OOM killer. > > The root memory cgroup is treated as a leaf cgroup, so

Re: [PATCH 0/4] Add support for muxing individual pins

On Fri, Sep 29, 2017 at 12:14 PM, Charles Keepax wrote: > This series add support for muxing individual pins within > pin mux, rather than just whole groups. Mainly, I had two > motivations here, one to avoid the need to add loads of groups > containing individual

Re: [PATCH 0/4] Add support for muxing individual pins

On Fri, Sep 29, 2017 at 12:14 PM, Charles Keepax wrote: > This series add support for muxing individual pins within > pin mux, rather than just whole groups. Mainly, I had two > motivations here, one to avoid the need to add loads of groups > containing individual pins and hardware that actually

[PATCH] power: supply: replace pr_* with dev_*

Use kernel preferred dev_* family of functions in place of pr_*, wherever a device object is present. Done with the help of coccinelle. Signed-off-by: Aishwarya Pant --- The following cocci script was used to make the patch: @r exists@ identifier f, s, x; position p; @@

[PATCH] power: supply: replace pr_* with dev_*

Use kernel preferred dev_* family of functions in place of pr_*, wherever a device object is present. Done with the help of coccinelle. Signed-off-by: Aishwarya Pant --- The following cocci script was used to make the patch: @r exists@ identifier f, s, x; position p; @@ f(..., struct s *x,...)

Re: [ANNOUNCE] fsperf: a simple fs/block performance testing framework

On Mon, Oct 09, 2017 at 09:00:51AM -0400, Josef Bacik wrote: > On Mon, Oct 09, 2017 at 04:17:31PM +1100, Dave Chinner wrote: > > On Sun, Oct 08, 2017 at 10:25:10PM -0400, Josef Bacik wrote: > > > > Integrating into fstests means it will be immediately available to > > > > all fs developers, it'll

Re: [ANNOUNCE] fsperf: a simple fs/block performance testing framework

On Mon, Oct 09, 2017 at 09:00:51AM -0400, Josef Bacik wrote: > On Mon, Oct 09, 2017 at 04:17:31PM +1100, Dave Chinner wrote: > > On Sun, Oct 08, 2017 at 10:25:10PM -0400, Josef Bacik wrote: > > > > Integrating into fstests means it will be immediately available to > > > > all fs developers, it'll

Re: [PATCH v6 05/11] dt-bindings: net: dwmac-sun8i: update documentation about integrated PHY

On Sun, Oct 08, 2017 at 06:33:40PM +, Corentin Labbe wrote: > On Thu, Sep 28, 2017 at 09:37:08AM +0200, Corentin Labbe wrote: > > On Wed, Sep 27, 2017 at 04:02:10PM +0200, Andrew Lunn wrote: > > > Hi Corentin > > > > > > > +Required properties for the mdio-mux node: > > > > + - compatible =

Re: [PATCH v6 05/11] dt-bindings: net: dwmac-sun8i: update documentation about integrated PHY

On Sun, Oct 08, 2017 at 06:33:40PM +, Corentin Labbe wrote: > On Thu, Sep 28, 2017 at 09:37:08AM +0200, Corentin Labbe wrote: > > On Wed, Sep 27, 2017 at 04:02:10PM +0200, Andrew Lunn wrote: > > > Hi Corentin > > > > > > > +Required properties for the mdio-mux node: > > > > + - compatible =

PROBLEM: general protection fault after s2disk

Hello, 1. After waking up from hibernation my computer immediately went black with a hidden kernel panic. 2. After waking up from hibernation (s2disk) my computer did 3 different beeps immediately went black with a hidden kernel panic. I was forced to use SysRq to issue a saK request and then

PROBLEM: general protection fault after s2disk

Hello, 1. After waking up from hibernation my computer immediately went black with a hidden kernel panic. 2. After waking up from hibernation (s2disk) my computer did 3 different beeps immediately went black with a hidden kernel panic. I was forced to use SysRq to issue a saK request and then

Re: [PATCH] Input: atmel_mxt_ts - Remove unnecessary byte_offset check

On 09/10/17 10:38:55 -0700, Dmitry Torokhov wrote: > On Sun, Oct 08, 2017 at 08:41:16PM +0100, Nick Dyer wrote: > > On Sun, Oct 08, 2017 at 07:44:18PM +0100, Christos Gkekas wrote: > > > Variable byte_offset is unsigned so checking whether it is greater or > > > equal to zero is redundant. > > >

Re: [PATCH] Input: atmel_mxt_ts - Remove unnecessary byte_offset check

On 09/10/17 10:38:55 -0700, Dmitry Torokhov wrote: > On Sun, Oct 08, 2017 at 08:41:16PM +0100, Nick Dyer wrote: > > On Sun, Oct 08, 2017 at 07:44:18PM +0100, Christos Gkekas wrote: > > > Variable byte_offset is unsigned so checking whether it is greater or > > > equal to zero is redundant. > > >

Re: [PATCH 3/6] ARM: sun8i: r40: add 5V regulator for Banana Pi M2 Ultra

On Sun, Oct 08, 2017 at 04:29:03AM +, Icenowy Zheng wrote: > On newer revisions of the Banana Pi M2 Ultra boards, the 5V power output > (used by HDMI, SATA and USB) is controller via a GPIO. > > Add the regulator node for it. > > Older revisions just have the 5V power output always on, and

Re: [PATCH 3/6] ARM: sun8i: r40: add 5V regulator for Banana Pi M2 Ultra

On Sun, Oct 08, 2017 at 04:29:03AM +, Icenowy Zheng wrote: > On newer revisions of the Banana Pi M2 Ultra boards, the 5V power output > (used by HDMI, SATA and USB) is controller via a GPIO. > > Add the regulator node for it. > > Older revisions just have the 5V power output always on, and

Re: [PATCH 2/6] ARM: sun8i: r40: add USB host port nodes for R40

On Sun, Oct 08, 2017 at 04:29:02AM +, Icenowy Zheng wrote: > From: Icenowy Zheng > > Allwinner R40 SoC features a USB OTG port and two USB HOST ports. > > Add support for the host ports in the DTSI file. > > The OTG controller still cannot work with existing compatibles,

Re: [PATCH 2/6] ARM: sun8i: r40: add USB host port nodes for R40

On Sun, Oct 08, 2017 at 04:29:02AM +, Icenowy Zheng wrote: > From: Icenowy Zheng > > Allwinner R40 SoC features a USB OTG port and two USB HOST ports. > > Add support for the host ports in the DTSI file. > > The OTG controller still cannot work with existing compatibles, and needs > more

Re: [PATCH] pinctrl: sx150x: make struct sx150x_regmap_config static

On Thu, Oct 5, 2017 at 12:23 PM, Colin King wrote: > From: Colin Ian King > > The structure sx150x_regmap_config is local to the source and does not > need to be in global scope, so make it static. > > Cleans up sparse warning: > symbol

Re: [PATCH] pinctrl: sx150x: make struct sx150x_regmap_config static

On Thu, Oct 5, 2017 at 12:23 PM, Colin King wrote: > From: Colin Ian King > > The structure sx150x_regmap_config is local to the source and does not > need to be in global scope, so make it static. > > Cleans up sparse warning: > symbol 'sx150x_regmap_config' was not declared. Should it be

Re: [PATCH] pinctrl: ingenic: make function ingenic_pinctrl_probe static

On Thu, Oct 5, 2017 at 12:11 PM, Colin King wrote: > From: Colin Ian King > > The function ingenic_pinctrl_probe is local to the source and does > not need to be in global scope, so make it static. > > Cleans up sparse warnings > symbol

Re: [PATCH] pinctrl: ingenic: make function ingenic_pinctrl_probe static

On Thu, Oct 5, 2017 at 12:11 PM, Colin King wrote: > From: Colin Ian King > > The function ingenic_pinctrl_probe is local to the source and does > not need to be in global scope, so make it static. > > Cleans up sparse warnings > symbol 'ingenic_pinctrl_probe' was not declared. Should it be

Re: [PATCH 3/3] mm: oom: show unreclaimable slab info when unreclaimable slabs > user memory

On 10/9/17 11:53 AM, Yang Shi wrote: On 10/8/17 11:36 PM, Michal Hocko wrote: On Mon 09-10-17 08:33:16, Michal Hocko wrote: On Sat 07-10-17 00:37:55, Yang Shi wrote: On 10/6/17 2:37 AM, Michal Hocko wrote: On Thu 05-10-17 05:29:10, Yang Shi wrote: [...] +

Re: [PATCH 3/3] mm: oom: show unreclaimable slab info when unreclaimable slabs > user memory

On 10/9/17 11:53 AM, Yang Shi wrote: On 10/8/17 11:36 PM, Michal Hocko wrote: On Mon 09-10-17 08:33:16, Michal Hocko wrote: On Sat 07-10-17 00:37:55, Yang Shi wrote: On 10/6/17 2:37 AM, Michal Hocko wrote: On Thu 05-10-17 05:29:10, Yang Shi wrote: [...] +

Re: [PATCH 1/6] phy: sun4i-usb: add support for R40 USB PHY

On Sun, Oct 08, 2017 at 04:29:01AM +, Icenowy Zheng wrote: > Allwinner R40 features a USB PHY like the one in A64, but with 3 PHYs. > > Add support for it. > > Signed-off-by: Icenowy Zheng Acked-by: Maxime Ripard Maxime -- Maxime

Re: [PATCH 1/6] phy: sun4i-usb: add support for R40 USB PHY

On Sun, Oct 08, 2017 at 04:29:01AM +, Icenowy Zheng wrote: > Allwinner R40 features a USB PHY like the one in A64, but with 3 PHYs. > > Add support for it. > > Signed-off-by: Icenowy Zheng Acked-by: Maxime Ripard Maxime -- Maxime Ripard, Free Electrons Embedded Linux and Kernel

[PATCH v2 3/3] pinctrl: sunxi: Enforce the strict mode by default

The strict mode should always have been enabled on our driver, and leaving it unchecked just makes it harder to find a migration path as time passes. Let's enable it by default now so that hopefully the new SoCs should be safe. Acked-by: Chen-Yu Tsai Signed-off-by: Maxime Ripard

[PATCH v2 3/3] pinctrl: sunxi: Enforce the strict mode by default

The strict mode should always have been enabled on our driver, and leaving it unchecked just makes it harder to find a migration path as time passes. Let's enable it by default now so that hopefully the new SoCs should be safe. Acked-by: Chen-Yu Tsai Signed-off-by: Maxime Ripard ---

[PATCH v2 0/3] pinctrl: sunxi: Start to enforce the strict mode

Hi, Here is an attempt to enable pinctrl's strict mode on our pinctrl drivers. Indeed, our controllers should have had that mode enabled since its introduction. However, there's a number of issues with old device trees that prevent from just enabling it for all the devices. There's basically two

[PATCH v2 1/3] pinctrl: sunxi: Introduce the strict flag

Our pinctrl device should have had strict set all along. However, it wasn't the case, and most of our old device trees also have a pinctrl group in addition to the GPIOs properties, which mean that we can't really turn it on now. All our new SoCs don't have that group, so we should still enable

[PATCH v2 0/3] pinctrl: sunxi: Start to enforce the strict mode

Hi, Here is an attempt to enable pinctrl's strict mode on our pinctrl drivers. Indeed, our controllers should have had that mode enabled since its introduction. However, there's a number of issues with old device trees that prevent from just enabling it for all the devices. There's basically two

[PATCH v2 1/3] pinctrl: sunxi: Introduce the strict flag

Our pinctrl device should have had strict set all along. However, it wasn't the case, and most of our old device trees also have a pinctrl group in addition to the GPIOs properties, which mean that we can't really turn it on now. All our new SoCs don't have that group, so we should still enable

[PATCH v2 2/3] pinctrl: sunxi: Disable strict mode for old pinctrl drivers

Old pinctrl drivers will need to disable strict mode for various reasons, among which: - Some DT will still have a pinctrl group for each GPIO used, which will be rejected by pin_request. While we could remove those nodes, we still have to deal with old DTs. - Some GPIOs on these

[PATCH v2 2/3] pinctrl: sunxi: Disable strict mode for old pinctrl drivers

Old pinctrl drivers will need to disable strict mode for various reasons, among which: - Some DT will still have a pinctrl group for each GPIO used, which will be rejected by pin_request. While we could remove those nodes, we still have to deal with old DTs. - Some GPIOs on these

Re: [PATCH] fscrypt: lock mutex before checking for bounce page pool

On Tue, Sep 12, 2017 at 10:22:52PM -0700, Eric Biggers wrote: > On Thu, Jul 06, 2017 at 10:57:48AM -0700, Eric Biggers wrote: > > fscrypt_initialize(), which allocates the global bounce page pool when > > an encrypted file is first accessed, uses "double-checked locking" to > > try to avoid

[PATCH 3/3] net/atm: Adjust 121 checks for null pointers

From: Markus Elfring Date: Mon, 9 Oct 2017 22:22:45 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The script “checkpatch.pl” pointed information out like the following. Comparison to NULL could be written … Thus

Re: [PATCH] fscrypt: lock mutex before checking for bounce page pool

On Tue, Sep 12, 2017 at 10:22:52PM -0700, Eric Biggers wrote: > On Thu, Jul 06, 2017 at 10:57:48AM -0700, Eric Biggers wrote: > > fscrypt_initialize(), which allocates the global bounce page pool when > > an encrypted file is first accessed, uses "double-checked locking" to > > try to avoid

[PATCH 3/3] net/atm: Adjust 121 checks for null pointers

From: Markus Elfring Date: Mon, 9 Oct 2017 22:22:45 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The script “checkpatch.pl” pointed information out like the following. Comparison to NULL could be written … Thus fix the affected source code

[PATCH 2/3] net/atm: Improve a size determination in 12 functions

From: Markus Elfring Date: Mon, 9 Oct 2017 22:00:19 +0200 Replace the specification of data structures by pointer dereferences as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style

[PATCH 2/3] net/atm: Improve a size determination in 12 functions

From: Markus Elfring Date: Mon, 9 Oct 2017 22:00:19 +0200 Replace the specification of data structures by pointer dereferences as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style convention. This issue was

[PATCH 1/3] net/atm: Delete an error message for a failed memory allocation in five functions

From: Markus Elfring Date: Mon, 9 Oct 2017 21:34:35 +0200 Omit extra messages for a memory allocation failure in these functions. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

[PATCH 1/3] net/atm: Delete an error message for a failed memory allocation in five functions

From: Markus Elfring Date: Mon, 9 Oct 2017 21:34:35 +0200 Omit extra messages for a memory allocation failure in these functions. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring --- net/atm/lec.c | 5 ++--- net/atm/mpc.c | 8 ++--

[PATCH 0/3] net-ATM: Adjustments for several function implementations

From: Markus Elfring Date: Mon, 9 Oct 2017 22:30:33 +0200 Some update suggestions were taken into account from static source code analysis. Markus Elfring (3): Delete an error message for a failed memory allocation in five functions Improve a size

[PATCH 0/3] net-ATM: Adjustments for several function implementations

From: Markus Elfring Date: Mon, 9 Oct 2017 22:30:33 +0200 Some update suggestions were taken into account from static source code analysis. Markus Elfring (3): Delete an error message for a failed memory allocation in five functions Improve a size determination in 12 functions Adjust 121

Re: [PATCH] intel-oaktrail: Clean up dead code

On 09/10/17 13:21:17 +0300, Andy Shevchenko wrote: > On Mon, Oct 9, 2017 at 1:57 AM, Christos Gkekas wrote: > > A couple of macros are unused and need to be removed. > > Also variable percent is unsigned so checking whether it is less than > > zero is redundant. > > >

Re: [PATCH] intel-oaktrail: Clean up dead code

On 09/10/17 13:21:17 +0300, Andy Shevchenko wrote: > On Mon, Oct 9, 2017 at 1:57 AM, Christos Gkekas wrote: > > A couple of macros are unused and need to be removed. > > Also variable percent is unsigned so checking whether it is less than > > zero is redundant. > > > -#define OT_EC_CAMERA_MASK

Re: mmotm 2017-10-03-17-08 uploaded

On Tue, Oct 03, 2017 at 05:08:44PM -0700, a...@linux-foundation.org wrote: > You will need quilt to apply these patches to the latest Linus release (4.x > or 4.x-rcY). The series file is in broken-out.tar.gz and is duplicated in > http://ozlabs.org/~akpm/mmotm/series I'm getting several merge

Re: mmotm 2017-10-03-17-08 uploaded

On Tue, Oct 03, 2017 at 05:08:44PM -0700, a...@linux-foundation.org wrote: > You will need quilt to apply these patches to the latest Linus release (4.x > or 4.x-rcY). The series file is in broken-out.tar.gz and is duplicated in > http://ozlabs.org/~akpm/mmotm/series I'm getting several merge

[PATCH v5 00/16] generate full callchain cursor entries for inlined frames

This series of patches completely reworks the way inline frames are handled. Instead of querying for the inline nodes on-demand in the individual tools, we now create proper callchain nodes for inlined frames. The advantages this approach brings are numerous: - less duplicated code in the

[PATCH v5 00/16] generate full callchain cursor entries for inlined frames

This series of patches completely reworks the way inline frames are handled. Instead of querying for the inline nodes on-demand in the individual tools, we now create proper callchain nodes for inlined frames. The advantages this approach brings are numerous: - less duplicated code in the

Re: [PATCH 4.9 000/104] 4.9.54-stable review

Hi Greg, On Sun, Oct 8, 2017 at 2:23 AM, Greg Kroah-Hartman wrote: > On Sat, Oct 07, 2017 at 11:56:17AM -0500, Tom Gall wrote: >> >> > On Oct 6, 2017, at 3:50 AM, Greg Kroah-Hartman >> > wrote: >> > >> > This is the start of the stable

Re: [PATCH 4.9 000/104] 4.9.54-stable review

Hi Greg, On Sun, Oct 8, 2017 at 2:23 AM, Greg Kroah-Hartman wrote: > On Sat, Oct 07, 2017 at 11:56:17AM -0500, Tom Gall wrote: >> >> > On Oct 6, 2017, at 3:50 AM, Greg Kroah-Hartman >> > wrote: >> > >> > This is the start of the stable review cycle for the 4.9.54 release. >> > There are 104

[PATCH v5 03/16] perf util: refactor inline_list to operate on symbols

This is a requirement to create real callchain entries for inlined frames. Since the list of inlines usually contains the target symbol too, i.e. the location where the frames get inlined to, we alias that symbol and reuse it as-is is. This ensures that other dependent functionality keeps

[PATCH v5 03/16] perf util: refactor inline_list to operate on symbols

This is a requirement to create real callchain entries for inlined frames. Since the list of inlines usually contains the target symbol too, i.e. the location where the frames get inlined to, we alias that symbol and reuse it as-is is. This ensures that other dependent functionality keeps

[PATCH v5 04/16] perf util: refactor inline_list to store srcline string directly

This is a preparation for the creation of real callchain entries for inlined frames. The rest of the perf code uses the srcline string. As such, using that also for the srcline API allows us to simplify some of the upcoming code. Most notably, it will allow us to cache the srcline for a given

[PATCH v5 01/16] perf report: remove code to handle inline frames from browsers

The follow-up commits will make inline frames first-class citizens in the callchain, thereby obsoleting all of this special code. Cc: Arnaldo Carvalho de Melo Cc: David Ahern Cc: Namhyung Kim Cc: Peter Zijlstra

[PATCH v5 04/16] perf util: refactor inline_list to store srcline string directly

This is a preparation for the creation of real callchain entries for inlined frames. The rest of the perf code uses the srcline string. As such, using that also for the srcline API allows us to simplify some of the upcoming code. Most notably, it will allow us to cache the srcline for a given

[PATCH v5 01/16] perf report: remove code to handle inline frames from browsers

The follow-up commits will make inline frames first-class citizens in the callchain, thereby obsoleting all of this special code. Cc: Arnaldo Carvalho de Melo Cc: David Ahern Cc: Namhyung Kim Cc: Peter Zijlstra Cc: Yao Jin Signed-off-by: Milian Wolff --- tools/perf/ui/browsers/hists.c |

[PATCH v5 05/16] perf report: create real callchain entries for inlined frames

The inline_node structs are maintained by the new dso->inlines tree. This in turn keeps ownership of the fake symbols and srcline string representing an inline frame. This tree is sorted by address to allow quick lookups. All other entries of the symbol beside the function name are unused for

[PATCH v5 08/16] perf script: mark inlined frames and do not print DSO for them

Instead of showing the (repeated) DSO name of the non-inlined frame, we now show the "(inlined)" suffix instead. Before: 214f7 __hypot_finite (/usr/lib/libm-2.25.so) ace3 hypot (/usr/lib/libm-2.25.so) a4a std::__complex_abs

[PATCH v5 05/16] perf report: create real callchain entries for inlined frames

The inline_node structs are maintained by the new dso->inlines tree. This in turn keeps ownership of the fake symbols and srcline string representing an inline frame. This tree is sorted by address to allow quick lookups. All other entries of the symbol beside the function name are unused for

[PATCH v5 08/16] perf script: mark inlined frames and do not print DSO for them

Instead of showing the (repeated) DSO name of the non-inlined frame, we now show the "(inlined)" suffix instead. Before: 214f7 __hypot_finite (/usr/lib/libm-2.25.so) ace3 hypot (/usr/lib/libm-2.25.so) a4a std::__complex_abs

[PATCH v5 02/16] perf util: store srcline in callchain_cursor_node

This is mostly a preparation to enable the creation of full callchain nodes for inline frames. Such frames will reference the IP of the non-inlined frame, but hold the symbol and srcline for an inlined location. As such, we won't be able to query the srcline on-demand based on the IP alone.

[PATCH v5 02/16] perf util: store srcline in callchain_cursor_node

This is mostly a preparation to enable the creation of full callchain nodes for inline frames. Such frames will reference the IP of the non-inlined frame, but hold the symbol and srcline for an inlined location. As such, we won't be able to query the srcline on-demand based on the IP alone.

[PATCH v5 06/16] perf report: fall-back to function name comparison for -g srcline

When a callchain entry has no srcline available, we ended up comparing the instruction pointer. I consider this to be not too useful. Rather, I think we should group the entries by function name, which this patch adds. For people who want to split the data on the IP boundary, using `-g address` is

[PATCH v5 06/16] perf report: fall-back to function name comparison for -g srcline

When a callchain entry has no srcline available, we ended up comparing the instruction pointer. I consider this to be not too useful. Rather, I think we should group the entries by function name, which this patch adds. For people who want to split the data on the IP boundary, using `-g address` is

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