Re: [PATCH v3 2/8] coccicheck: make SPFLAGS more useful

Le 21/06/16 à 21:21, Luis R. Rodriguez a écrit : SPFLAGS is set early, it means that any heuristics done on coccicheck cannot be overridden currently. Move SPFLAGS after OPTIONS and set this at the end. This lets you override any heuristics as coccinelle treats conflicts by only listening to the

Re: [PATCH v3 2/8] coccicheck: make SPFLAGS more useful

Le 21/06/16 à 21:21, Luis R. Rodriguez a écrit : SPFLAGS is set early, it means that any heuristics done on coccicheck cannot be overridden currently. Move SPFLAGS after OPTIONS and set this at the end. This lets you override any heuristics as coccinelle treats conflicts by only listening to the

Re: linux-next: Tree for Jun 21

On 6/21/2016 5:14 PM, Arnd Bergmann wrote: On Tuesday, June 21, 2016 8:50:48 PM CEST Peter Zijlstra wrote: So what's your build process for the cross tools, by the way? I'm assuming you're not doing a total bootstrap cross-tool build since you'd need minimal kernel headers (linux/errno.h or

Re: linux-next: Tree for Jun 21

On 6/21/2016 5:14 PM, Arnd Bergmann wrote: On Tuesday, June 21, 2016 8:50:48 PM CEST Peter Zijlstra wrote: So what's your build process for the cross tools, by the way? I'm assuming you're not doing a total bootstrap cross-tool build since you'd need minimal kernel headers (linux/errno.h or

Re: [PATCH v2] pwm: improve args checking in pwm_apply_state()

On Wed, 22 Jun 2016 12:16:59 -0700 Brian Norris wrote: > On Wed, Jun 22, 2016 at 10:04:22AM +0200, Boris Brezillon wrote: > > From 0610f7e24976e176054bce20445ff42d8aea9513 Mon Sep 17 00:00:00 2001 > > From: Boris Brezillon > > Date:

Re: [PATCH v2] pwm: improve args checking in pwm_apply_state()

On Wed, 22 Jun 2016 12:16:59 -0700 Brian Norris wrote: > On Wed, Jun 22, 2016 at 10:04:22AM +0200, Boris Brezillon wrote: > > From 0610f7e24976e176054bce20445ff42d8aea9513 Mon Sep 17 00:00:00 2001 > > From: Boris Brezillon > > Date: Wed, 22 Jun 2016 09:25:14 +0200 > > Subject: [PATCH] pwm: Fix

Re: [PATCH] mellanox: mlx5: Use logging functions to reduce text ~10k/5%

On Wed, Jun 22, 2016 at 11:23:59AM -0700, Joe Perches wrote: > The output changes now do not include line #, but do include the > function offset. I've been using a technique like this in some code with good results: struct source_location { const char *file; const char *func; const

Re: linux-next: Tree for Jun 21

On 6/22/2016 5:16 AM, Peter Zijlstra wrote: On Tue, Jun 21, 2016 at 02:36:34PM -0400, Chris Metcalf wrote: >On 6/21/2016 2:28 PM, Peter Zijlstra wrote: > >On Tue, Jun 21, 2016 at 07:29:18PM +0200, Peter Zijlstra wrote: > > > >>>OK, I seem to have a tilepro-linux-gcc-6.1.1 build done. Lets see

Re: [PATCH] mellanox: mlx5: Use logging functions to reduce text ~10k/5%

On Wed, Jun 22, 2016 at 11:23:59AM -0700, Joe Perches wrote: > The output changes now do not include line #, but do include the > function offset. I've been using a technique like this in some code with good results: struct source_location { const char *file; const char *func; const

Re: linux-next: Tree for Jun 21

On 6/22/2016 5:16 AM, Peter Zijlstra wrote: On Tue, Jun 21, 2016 at 02:36:34PM -0400, Chris Metcalf wrote: >On 6/21/2016 2:28 PM, Peter Zijlstra wrote: > >On Tue, Jun 21, 2016 at 07:29:18PM +0200, Peter Zijlstra wrote: > > > >>>OK, I seem to have a tilepro-linux-gcc-6.1.1 build done. Lets see

Re: [PATCH v4 2/9] [media] v4l2-core: Add VFL_TYPE_TOUCH_SENSOR

On Wed, 22 Jun 2016, Nick Dyer wrote: On 22/06/2016 12:48, Florian Echtler wrote: On 20.06.2016 14:00, Hans Verkuil wrote: On 06/17/2016 04:16 PM, Nick Dyer wrote: Use a new device prefix v4l-touch for these devices, to stop generic capture software from treating them as webcams. Come to

Re: [PATCH v4 2/9] [media] v4l2-core: Add VFL_TYPE_TOUCH_SENSOR

On Wed, 22 Jun 2016, Nick Dyer wrote: On 22/06/2016 12:48, Florian Echtler wrote: On 20.06.2016 14:00, Hans Verkuil wrote: On 06/17/2016 04:16 PM, Nick Dyer wrote: Use a new device prefix v4l-touch for these devices, to stop generic capture software from treating them as webcams. Come to

Re: [PATCH] can: only call can_stat_update with procfs

On 06/20/2016 05:51 PM, Arnd Bergmann wrote: > The change to leave out procfs support in CAN when CONFIG_PROC_FS > is not set was incomplete and leads to a build error: > > net/built-in.o: In function `can_init': > :(.init.text+0x9858): undefined reference to `can_stat_update' > ERROR:

Re: [PATCH] can: only call can_stat_update with procfs

On 06/20/2016 05:51 PM, Arnd Bergmann wrote: > The change to leave out procfs support in CAN when CONFIG_PROC_FS > is not set was incomplete and leads to a build error: > > net/built-in.o: In function `can_init': > :(.init.text+0x9858): undefined reference to `can_stat_update' > ERROR:

Re: [PATCH 1/2] net: ethernet: sun4i-emac: use phydev from struct net_device

From: Philippe Reynes Date: Sat, 18 Jun 2016 15:15:39 +0200 > The private structure contain a pointer to phydev, but the structure > net_device already contain such pointer. So we can remove the pointer > phydev in the private structure, and update the driver to use the > one

Re: [PATCH 1/2] net: ethernet: sun4i-emac: use phydev from struct net_device

From: Philippe Reynes Date: Sat, 18 Jun 2016 15:15:39 +0200 > The private structure contain a pointer to phydev, but the structure > net_device already contain such pointer. So we can remove the pointer > phydev in the private structure, and update the driver to use the > one contained in struct

Re: [PATCH] kcm: fix /proc memory leak

From: Jiri Slaby Date: Mon, 20 Jun 2016 11:36:28 +0200 > Every open of /proc/net/kcm leaks 16 bytes of memory as is reported by > kmemleak: > unreferenced object 0x88059c0e3458 (size 192): > comm "cat", pid 1401, jiffies 4294935742 (age 310.720s) > hex dump (first 32

[PATCH v2] staging/android: prepare sw_sync files for de-staging

From: Gustavo Padovan remove file paths in the comments and add short description about each file. v2: remove file paths instead of just change them. Signed-off-by: Gustavo Padovan --- drivers/staging/android/sw_sync.c| 2

Re: [PATCH 1/8] vfs: new d_allocate method

On Wed, Jun 22, 2016 at 7:02 PM, Al Viro wrote: > On Wed, Jun 22, 2016 at 04:35:03PM +0200, Miklos Szeredi wrote: >> Allow filesystem to initialize dentry (->d_fsdata to be explicit) at >> allocation time. > > Something similar had been discussed a while ago (I don't

Re: [PATCH] kcm: fix /proc memory leak

From: Jiri Slaby Date: Mon, 20 Jun 2016 11:36:28 +0200 > Every open of /proc/net/kcm leaks 16 bytes of memory as is reported by > kmemleak: > unreferenced object 0x88059c0e3458 (size 192): > comm "cat", pid 1401, jiffies 4294935742 (age 310.720s) > hex dump (first 32 bytes): > 28 45

[PATCH v2] staging/android: prepare sw_sync files for de-staging

From: Gustavo Padovan remove file paths in the comments and add short description about each file. v2: remove file paths instead of just change them. Signed-off-by: Gustavo Padovan --- drivers/staging/android/sw_sync.c| 2 +- drivers/staging/android/sync_debug.c | 2 +-

Re: [PATCH 1/8] vfs: new d_allocate method

On Wed, Jun 22, 2016 at 7:02 PM, Al Viro wrote: > On Wed, Jun 22, 2016 at 04:35:03PM +0200, Miklos Szeredi wrote: >> Allow filesystem to initialize dentry (->d_fsdata to be explicit) at >> allocation time. > > Something similar had been discussed a while ago (I don't remember whether > you'd been

[PATCH v3] cgroup: Disable IRQs while holding css_set_lock

While testing the deadline scheduler + cgroup setup I hit this warning. [ 132.612935] [ cut here ] [ 132.612951] WARNING: CPU: 5 PID: 0 at kernel/softirq.c:150 __local_bh_enable_ip+0x6b/0x80 [ 132.612952] Modules linked in: (a ton of modules...) [ 132.612981] CPU: 5

[PATCH v3] cgroup: Disable IRQs while holding css_set_lock

While testing the deadline scheduler + cgroup setup I hit this warning. [ 132.612935] [ cut here ] [ 132.612951] WARNING: CPU: 5 PID: 0 at kernel/softirq.c:150 __local_bh_enable_ip+0x6b/0x80 [ 132.612952] Modules linked in: (a ton of modules...) [ 132.612981] CPU: 5

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

From: Philippe Reynes Date: Sun, 19 Jun 2016 22:37:06 +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 2/2] net: ethernet: altera_tse: use phy_ethtool_{get|set}_link_ksettings

From: Philippe Reynes Date: Sat, 18 Jun 2016 16:37:21 +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 1/2] net: ethernet: bgmac: use phydev from struct net_device

From: Philippe Reynes Date: Sun, 19 Jun 2016 22:37:05 +0200 > The private structure contain a pointer to phydev, but the structure > net_device already contain such pointer. So we can remove the pointer > phydev in the private structure, and update the driver to use the > one

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

From: Philippe Reynes Date: Sun, 19 Jun 2016 22:37:06 +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 2/2] net: ethernet: altera_tse: use phy_ethtool_{get|set}_link_ksettings

From: Philippe Reynes Date: Sat, 18 Jun 2016 16:37:21 +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 1/2] net: ethernet: bgmac: use phydev from struct net_device

From: Philippe Reynes Date: Sun, 19 Jun 2016 22:37:05 +0200 > The private structure contain a pointer to phydev, but the structure > net_device already contain such pointer. So we can remove the pointer > phydev in the private structure, and update the driver to use the > one contained in struct

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

From: Philippe Reynes Date: Sat, 18 Jun 2016 15:15:40 +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 2/2] net: ethernet: sun4i-emac: use phy_ethtool_{get|set}_link_ksettings

From: Philippe Reynes Date: Sat, 18 Jun 2016 15:15:40 +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 1/2] net: ethernet: altera_tse: use phydev from struct net_device

From: Philippe Reynes Date: Sat, 18 Jun 2016 16:37:20 +0200 > The private structure contain a pointer to phydev, but the structure > net_device already contain such pointer. So we can remove the pointer > phydev in the private structure, and update the driver to use the > one

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

From: Philippe Reynes Date: Sat, 18 Jun 2016 16:37:20 +0200 > The private structure contain a pointer to phydev, but the structure > net_device already contain such pointer. So we can remove the pointer > phydev in the private structure, and update the driver to use the > one contained in struct

Re: [PATCH] net: cavium: liquidio: Use vzalloc instead of vmalloc

From: Amitoj Kaur Chawla Date: Sat, 18 Jun 2016 12:23:20 +0530 > vzalloc combines vmalloc and memset 0. > > The Coccinelle semantic patch used to make this change is as follows: > @@ > type T; > T *d; > expression e; > statement S; > @@ > > d = > -

Re: [PATCH] net: cavium: liquidio: Use vzalloc instead of vmalloc

From: Amitoj Kaur Chawla Date: Sat, 18 Jun 2016 12:23:20 +0530 > vzalloc combines vmalloc and memset 0. > > The Coccinelle semantic patch used to make this change is as follows: > @@ > type T; > T *d; > expression e; > statement S; > @@ > > d = > -vmalloc > +

Re: [PATCH] x86: prevent gcc from emitting SSE into boot code

On Wed, Jun 22, 2016 at 7:37 PM, Dmitry Vyukov wrote: > Latest gcc manages to emit MOVDQA into boot code > which leads to crashes. Add more -mno-see flags. > > Signed-off-by: Dmitry Vyukov > --- > arch/x86/boot/compressed/Makefile | 2 +- > 1 file

Re: [PATCH] x86: prevent gcc from emitting SSE into boot code

On Wed, Jun 22, 2016 at 7:37 PM, Dmitry Vyukov wrote: > Latest gcc manages to emit MOVDQA into boot code > which leads to crashes. Add more -mno-see flags. > > Signed-off-by: Dmitry Vyukov > --- > arch/x86/boot/compressed/Makefile | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff

Re: [PATCH 0/6] Support DAX for device-mapper dm-linear devices

On Wed, 2016-06-22 at 12:15 -0700, Dan Williams wrote: > On Wed, Jun 22, 2016 at 10:44 AM, Kani, Toshimitsu > wrote: > > On Tue, 2016-06-21 at 14:17 -0400, Mike Snitzer wrote: > > > > > > On Tue, Jun 21 2016 at 11:44am -0400, > > > Kani, Toshimitsu wrote:

Re: [PATCH 0/6] Support DAX for device-mapper dm-linear devices

On Wed, 2016-06-22 at 12:15 -0700, Dan Williams wrote: > On Wed, Jun 22, 2016 at 10:44 AM, Kani, Toshimitsu > wrote: > > On Tue, 2016-06-21 at 14:17 -0400, Mike Snitzer wrote: > > > > > > On Tue, Jun 21 2016 at 11:44am -0400, > > > Kani, Toshimitsu wrote: > > > > > > > > On Tue, 2016-06-21 at

Re: [Y2038] [PATCH v2] crypto: Jitter RNG - use ktime_get_ns as fallback

On Wednesday, June 22, 2016 7:26:06 PM CEST Stephan Mueller wrote: > As part of the Y2038 development, __getnstimeofday is not supposed to be > used any more. It is now replaced with ktime_get_ns. The Jitter RNG uses > the time stamp to measure the execution time of a given code path and > tries

Re: [Y2038] [PATCH v2] crypto: Jitter RNG - use ktime_get_ns as fallback

On Wednesday, June 22, 2016 7:26:06 PM CEST Stephan Mueller wrote: > As part of the Y2038 development, __getnstimeofday is not supposed to be > used any more. It is now replaced with ktime_get_ns. The Jitter RNG uses > the time stamp to measure the execution time of a given code path and > tries

Re: [PATCH 4/4] HID: remove ThingM blink(1) driver

Hi Heiner, Heiner Kallweit writes: >>> Also adding Vivien Didelot to CC, as the author of the original driver. >>> Vivien, the full set can be found in linux-input archives ( >>> http://marc.info/?l=linux-input=1=201606=2 ) >> >> Thanks a lot for the follow-up Jiri. >>

Re: [PATCH 4/4] HID: remove ThingM blink(1) driver

Hi Heiner, Heiner Kallweit writes: >>> Also adding Vivien Didelot to CC, as the author of the original driver. >>> Vivien, the full set can be found in linux-input archives ( >>> http://marc.info/?l=linux-input=1=201606=2 ) >> >> Thanks a lot for the follow-up Jiri. >> >> If you guys decide

Re: [PATCH v2] cgroup: disable irqs while holding css_set_lock

Hi On 06/17/2016 04:59 PM, Daniel Bristot de Oliveira wrote: > - using _irq and _irqsave appropriately, and > - using raw_spin locks functions. After some patches/tests on -rt, I figured that there is a -rt specific patch that moves cgroup_free() calls to the non-atomic context (in the -rt

Re: [PATCH v2] cgroup: disable irqs while holding css_set_lock

Hi On 06/17/2016 04:59 PM, Daniel Bristot de Oliveira wrote: > - using _irq and _irqsave appropriately, and > - using raw_spin locks functions. After some patches/tests on -rt, I figured that there is a -rt specific patch that moves cgroup_free() calls to the non-atomic context (in the -rt

Re: [PATCH 4/4] HID: remove ThingM blink(1) driver

Am 22.06.2016 um 15:25 schrieb Jiri Kosina: > On Tue, 21 Jun 2016, Heiner Kallweit wrote: > >> Now that support for ThingM blink(1) was merged into the hid-led driver >> the dedicated driver for this device can be removed. >> >> Signed-off-by: Heiner Kallweit >> --- >>

Re: [PATCH 4/4] HID: remove ThingM blink(1) driver

Am 22.06.2016 um 15:25 schrieb Jiri Kosina: > On Tue, 21 Jun 2016, Heiner Kallweit wrote: > >> Now that support for ThingM blink(1) was merged into the hid-led driver >> the dedicated driver for this device can be removed. >> >> Signed-off-by: Heiner Kallweit >> --- >> drivers/hid/Kconfig

Re: [PATCH 4/4] HID: remove ThingM blink(1) driver

Am 22.06.2016 um 17:42 schrieb Vivien Didelot: > Hi, > > Jiri Kosina writes: > >> On Tue, 21 Jun 2016, Heiner Kallweit wrote: >> >>> Now that support for ThingM blink(1) was merged into the hid-led driver >>> the dedicated driver for this device can be removed. >>> >>>

Re: [PATCH 4/4] HID: remove ThingM blink(1) driver

Am 22.06.2016 um 17:42 schrieb Vivien Didelot: > Hi, > > Jiri Kosina writes: > >> On Tue, 21 Jun 2016, Heiner Kallweit wrote: >> >>> Now that support for ThingM blink(1) was merged into the hid-led driver >>> the dedicated driver for this device can be removed. >>> >>> Signed-off-by: Heiner

Re: [PATCH v4 2/2] reset: add TI SYSCON based reset driver

On 06/22/2016 05:19 AM, Philipp Zabel wrote: > Am Montag, den 20.06.2016, 13:46 -0500 schrieb Andrew F. Davis: >> Add a reset-controller driver for performing reset management of >> various devices present on the SoC, with the reset registers shared >> between devices in a common register memory

Re: [PATCH v4 2/2] reset: add TI SYSCON based reset driver

On 06/22/2016 05:19 AM, Philipp Zabel wrote: > Am Montag, den 20.06.2016, 13:46 -0500 schrieb Andrew F. Davis: >> Add a reset-controller driver for performing reset management of >> various devices present on the SoC, with the reset registers shared >> between devices in a common register memory

Re: [Cocci] [PATCH v3 3/8] coccicheck: enable parmap support

> > Actually, it would be probably good to raise the default chunksize a bit > > for the latter reason. It would depend on which files get assigned to > > which chunks though how much benefit it might have. > > What value do you have in mind? Or should we leave this as a separate future >

Re: [Cocci] [PATCH v3 3/8] coccicheck: enable parmap support

> > Actually, it would be probably good to raise the default chunksize a bit > > for the latter reason. It would depend on which files get assigned to > > which chunks though how much benefit it might have. > > What value do you have in mind? Or should we leave this as a separate future >

[RESEND PATCH v2 1/2] staging: iio: accel: fix error check

sca3000_read_ctrl_reg() returns a negative number on failure, check for this instead of zero. Signed-off-by: Luis de Bethencourt Reviewed-by: Andrew F. Davis Reviewed-by: Jonathan Cameron --- drivers/staging/iio/accel/sca3000_core.c | 2

[RESEND PATCH v2 1/2] staging: iio: accel: fix error check

sca3000_read_ctrl_reg() returns a negative number on failure, check for this instead of zero. Signed-off-by: Luis de Bethencourt Reviewed-by: Andrew F. Davis Reviewed-by: Jonathan Cameron --- drivers/staging/iio/accel/sca3000_core.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

[RESEND PATCH v2 2/2] staging: iio: accel: add error check

Go to error_ret if sca3000_read_ctrl_reg() failed. Signed-off-by: Luis de Bethencourt --- drivers/staging/iio/accel/sca3000_core.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/staging/iio/accel/sca3000_core.c b/drivers/staging/iio/accel/sca3000_core.c

[RESEND PATCH v2 2/2] staging: iio: accel: add error check

Go to error_ret if sca3000_read_ctrl_reg() failed. Signed-off-by: Luis de Bethencourt --- drivers/staging/iio/accel/sca3000_core.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/staging/iio/accel/sca3000_core.c b/drivers/staging/iio/accel/sca3000_core.c index ec12181..b3f6dbf

oferta de préstamo 1,5%

Buen día, Se trata de préstamos de banco TSB plc de Lloyd ofrecen. TSB Lloyds ofrece préstamos flexibles y asequibles para cualquier propósito para ayudarle a alcanzar sus objetivos. nos préstamo a tipo de interés baja del 1,5%. Aquí están algunas características importantes del préstamo

oferta de préstamo 1,5%

Buen día, Se trata de préstamos de banco TSB plc de Lloyd ofrecen. TSB Lloyds ofrece préstamos flexibles y asequibles para cualquier propósito para ayudarle a alcanzar sus objetivos. nos préstamo a tipo de interés baja del 1,5%. Aquí están algunas características importantes del préstamo

RE: [PATCH] ACPI: don't show an error when we're not in charge of PCIe hotplug.

> -Original Message- > From: rjwyso...@gmail.com [mailto:rjwyso...@gmail.com] On Behalf Of > Rafael J. Wysocki > Sent: Tuesday, June 21, 2016 5:51 PM > To: Limonciello, Mario > Cc: Peter Jones ; Rafael J. Wysocki > ; ACPI

RE: [PATCH] ACPI: don't show an error when we're not in charge of PCIe hotplug.

> -Original Message- > From: rjwyso...@gmail.com [mailto:rjwyso...@gmail.com] On Behalf Of > Rafael J. Wysocki > Sent: Tuesday, June 21, 2016 5:51 PM > To: Limonciello, Mario > Cc: Peter Jones ; Rafael J. Wysocki > ; ACPI Devel Maling List ; > Linux Kernel Mailing List ; Len Brown > ;

[RESEND PATCH] staging: gdm724x: gdm_usb: Remove ignored value

The value assigned to ret will be overwritten before it could be read in a future iteration of the loop. Removing the unnecessary assignment. Signed-off-by: Luis de Bethencourt --- drivers/staging/gdm724x/gdm_usb.c | 8 1 file changed, 4 insertions(+), 4

[RESEND PATCH] staging: gdm724x: gdm_usb: Remove ignored value

The value assigned to ret will be overwritten before it could be read in a future iteration of the loop. Removing the unnecessary assignment. Signed-off-by: Luis de Bethencourt --- drivers/staging/gdm724x/gdm_usb.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git

[PATCH v2 2/2] powerpc/fadump: parse fadump reserve memory size based on memory range

Currently, memory for fadump can be specified with fadump_reserve_mem=size, where only a fixed size can be specified. Add the below syntax as well, to support conditional reservation based on system memory size: fadump_reserve_mem=:[,:,...] This syntax helps using the same commandline

Re: [PATCH v13 01/16] PCI: Let pci_mmap_page_range() take resource address

On Wed, Jun 22, 2016 at 8:22 AM, Bjorn Helgaas wrote: > On Tue, Jun 21, 2016 at 09:32:49PM -0700, Yinghai Lu wrote: > > If sparc is broken, let's make this a tiny sparc-only patch that fixes > only the breakage -- no cleanup or restructuring. Then we can do the > more

[PATCH v2 1/2] refactor code parsing size based on memory range

Currently, crashkernel parameter supports the below syntax to parse size based on memory range: crashkernel=:[,:,...] While such parsing is implemented for crashkernel parameter, it applies to other parameters with similar syntax. So, move this code to a more generic place for code

[PATCH v2 2/2] powerpc/fadump: parse fadump reserve memory size based on memory range

Currently, memory for fadump can be specified with fadump_reserve_mem=size, where only a fixed size can be specified. Add the below syntax as well, to support conditional reservation based on system memory size: fadump_reserve_mem=:[,:,...] This syntax helps using the same commandline

Re: [PATCH v13 01/16] PCI: Let pci_mmap_page_range() take resource address

On Wed, Jun 22, 2016 at 8:22 AM, Bjorn Helgaas wrote: > On Tue, Jun 21, 2016 at 09:32:49PM -0700, Yinghai Lu wrote: > > If sparc is broken, let's make this a tiny sparc-only patch that fixes > only the breakage -- no cleanup or restructuring. Then we can do the > more extensive work in a

[PATCH v2 1/2] refactor code parsing size based on memory range

Currently, crashkernel parameter supports the below syntax to parse size based on memory range: crashkernel=:[,:,...] While such parsing is implemented for crashkernel parameter, it applies to other parameters with similar syntax. So, move this code to a more generic place for code

[PATCH v2 0/2] powerpc/fadump: support memory range syntax for fadump memory reservation

This patchset adds support to input system memory range based memory size for fadump reservation. The crashkernel parameter already supports such syntax. The first patch refactors the parsing code of crashkernel parameter for reuse. The second patch uses the newly refactored parsing code to

[PATCH v2 0/2] powerpc/fadump: support memory range syntax for fadump memory reservation

This patchset adds support to input system memory range based memory size for fadump reservation. The crashkernel parameter already supports such syntax. The first patch refactors the parsing code of crashkernel parameter for reuse. The second patch uses the newly refactored parsing code to

[RESEND PATCH v2 3/5] ir-rx51: use PWM framework instead of OMAP dmtimer

Convert driver to use PWM framework instead of calling dmtimer functions directly for PWM timer. Remove paragraph about writing to the Free Software Foundation's mailing address while at it. Signed-off-by: Ivaylo Dimitrov ---

[RESEND PATCH v2 3/5] ir-rx51: use PWM framework instead of OMAP dmtimer

Convert driver to use PWM framework instead of calling dmtimer functions directly for PWM timer. Remove paragraph about writing to the Free Software Foundation's mailing address while at it. Signed-off-by: Ivaylo Dimitrov --- arch/arm/mach-omap2/board-rx51-peripherals.c | 1 -

[RESEND PATCH v2 1/5] ir-rx51: Fix build after multiarch changes broke it

The ir-rx51 driver for n900 has been disabled since the multiarch changes as plat include directory no longer is SoC specific. Let's fix it with minimal changes to pass the dmtimer calls in pdata. Then the following changes can be done while things can be tested to be working for each change: 1.

[RESEND PATCH v2 1/5] ir-rx51: Fix build after multiarch changes broke it

The ir-rx51 driver for n900 has been disabled since the multiarch changes as plat include directory no longer is SoC specific. Let's fix it with minimal changes to pass the dmtimer calls in pdata. Then the following changes can be done while things can be tested to be working for each change: 1.

[RESEND PATCH v2 4/5] ir-rx51: add DT support to driver

With the upcoming removal of legacy boot, lets add support to one of the last N900 drivers remaining without it. As the driver still uses omap dmtimer, add auxdata as well. Signed-off-by: Ivaylo Dimitrov Acked-by: Rob Herring ---

[RESEND PATCH v2 4/5] ir-rx51: add DT support to driver

With the upcoming removal of legacy boot, lets add support to one of the last N900 drivers remaining without it. As the driver still uses omap dmtimer, add auxdata as well. Signed-off-by: Ivaylo Dimitrov Acked-by: Rob Herring --- .../devicetree/bindings/media/nokia,n900-ir | 20

[RESEND PATCH v2 2/5] pwm: omap-dmtimer: Allow for setting dmtimer clock source

OMAP GP timers can have different input clocks that allow different PWM frequencies. However, there is no other way of setting the clock source but through clocks or clock-names properties of the timer itself. This limits PWM functionality to only the frequencies allowed by the particular clock

[RESEND PATCH v2 0/5] ir-rx51 driver fixes

ir-rx51 is a driver for Nokia N900 IR transmitter. The current series fixes the remaining problems in the driver: - replace GP timer 9 with PWM framework usage - replace pulse width timer dmtimer usage with hrtimer - add DT support to the driver - add driver to the board DTS Patch 2 is

[RESEND PATCH v2 2/5] pwm: omap-dmtimer: Allow for setting dmtimer clock source

OMAP GP timers can have different input clocks that allow different PWM frequencies. However, there is no other way of setting the clock source but through clocks or clock-names properties of the timer itself. This limits PWM functionality to only the frequencies allowed by the particular clock

[RESEND PATCH v2 0/5] ir-rx51 driver fixes

ir-rx51 is a driver for Nokia N900 IR transmitter. The current series fixes the remaining problems in the driver: - replace GP timer 9 with PWM framework usage - replace pulse width timer dmtimer usage with hrtimer - add DT support to the driver - add driver to the board DTS Patch 2 is

[RESEND PATCH v2 5/5] ir-rx51: use hrtimer instead of dmtimer

Drop dmtimer usage for pulse timer in favor of hrtimer. That allows removing PWM dmitimer platform data usage. Signed-off-by: Ivaylo Dimitrov --- arch/arm/mach-omap2/board-rx51-peripherals.c | 4 - arch/arm/mach-omap2/pdata-quirks.c | 3 -

[RESEND PATCH v2 5/5] ir-rx51: use hrtimer instead of dmtimer

Drop dmtimer usage for pulse timer in favor of hrtimer. That allows removing PWM dmitimer platform data usage. Signed-off-by: Ivaylo Dimitrov --- arch/arm/mach-omap2/board-rx51-peripherals.c | 4 - arch/arm/mach-omap2/pdata-quirks.c | 3 - drivers/media/rc/ir-rx51.c

Re: Documenting ptrace access mode checking

Hi Jann, On 06/21/2016 10:55 PM, Jann Horn wrote: On Tue, Jun 21, 2016 at 11:41:16AM +0200, Michael Kerrisk (man-pages) wrote: Hi Jann, Stephen, et al. Jann, since you recently committed a patch in this area, and Stephen, since you committed 006ebb40d3d much further back in time, I wonder if

Re: Documenting ptrace access mode checking

Hi Jann, On 06/21/2016 10:55 PM, Jann Horn wrote: On Tue, Jun 21, 2016 at 11:41:16AM +0200, Michael Kerrisk (man-pages) wrote: Hi Jann, Stephen, et al. Jann, since you recently committed a patch in this area, and Stephen, since you committed 006ebb40d3d much further back in time, I wonder if

Re: Documenting ptrace access mode checking

Hi Kees, On 06/21/2016 10:29 PM, Kees Cook wrote: On Tue, Jun 21, 2016 at 12:55 PM, Eric W. Biederman wrote: Adding Oleg just because he seems to do most of the ptrace related maintenance these days. "Michael Kerrisk (man-pages)" writes: Hi

Re: Documenting ptrace access mode checking

Hi Kees, On 06/21/2016 10:29 PM, Kees Cook wrote: On Tue, Jun 21, 2016 at 12:55 PM, Eric W. Biederman wrote: Adding Oleg just because he seems to do most of the ptrace related maintenance these days. "Michael Kerrisk (man-pages)" writes: Hi Jann, Stephen, et al. Jann, since you recently

Re: Documenting ptrace access mode checking

Hi Eric, On 06/21/2016 09:55 PM, Eric W. Biederman wrote: Adding Oleg just because he seems to do most of the ptrace related maintenance these days. "Michael Kerrisk (man-pages)" writes: Hi Jann, Stephen, et al. Jann, since you recently committed a patch in this

Re: Documenting ptrace access mode checking

Hi Eric, On 06/21/2016 09:55 PM, Eric W. Biederman wrote: Adding Oleg just because he seems to do most of the ptrace related maintenance these days. "Michael Kerrisk (man-pages)" writes: Hi Jann, Stephen, et al. Jann, since you recently committed a patch in this area, and Stephen, since

Re: [RFC PATCH v2 05/18] sched: add task flag for preempt IRQ tracking

On Wed, Jun 22, 2016 at 11:40 AM, Josh Poimboeuf wrote: > On Wed, Jun 22, 2016 at 11:26:21AM -0700, Andy Lutomirski wrote: >> > >> > So are you suggesting something like: >> > >> > .macro ENTRY_CALL func pt_regs_offset=0 >> > call \func >> > 1:

Re: [RFC PATCH v2 05/18] sched: add task flag for preempt IRQ tracking

On Wed, Jun 22, 2016 at 11:40 AM, Josh Poimboeuf wrote: > On Wed, Jun 22, 2016 at 11:26:21AM -0700, Andy Lutomirski wrote: >> > >> > So are you suggesting something like: >> > >> > .macro ENTRY_CALL func pt_regs_offset=0 >> > call \func >> > 1: .pushsection .entry_calls, "a"

Re: [PATCH v2] pwm: improve args checking in pwm_apply_state()

On Wed, Jun 22, 2016 at 10:04:22AM +0200, Boris Brezillon wrote: > From 0610f7e24976e176054bce20445ff42d8aea9513 Mon Sep 17 00:00:00 2001 > From: Boris Brezillon > Date: Wed, 22 Jun 2016 09:25:14 +0200 > Subject: [PATCH] pwm: Fix pwm_apply_args() > > Commit

Re: [PATCH v2] pwm: improve args checking in pwm_apply_state()

On Wed, Jun 22, 2016 at 10:04:22AM +0200, Boris Brezillon wrote: > From 0610f7e24976e176054bce20445ff42d8aea9513 Mon Sep 17 00:00:00 2001 > From: Boris Brezillon > Date: Wed, 22 Jun 2016 09:25:14 +0200 > Subject: [PATCH] pwm: Fix pwm_apply_args() > > Commit 5ec803edcb70 ("pwm: Add core

Re: [PATCH 0/6] Support DAX for device-mapper dm-linear devices

On Wed, Jun 22, 2016 at 10:44 AM, Kani, Toshimitsu wrote: > On Tue, 2016-06-21 at 14:17 -0400, Mike Snitzer wrote: >> On Tue, Jun 21 2016 at 11:44am -0400, >> Kani, Toshimitsu wrote: >> > >> > On Tue, 2016-06-21 at 09:41 -0400, Mike Snitzer wrote: >> > >

Re: [PATCH 0/6] Support DAX for device-mapper dm-linear devices

On Wed, Jun 22, 2016 at 10:44 AM, Kani, Toshimitsu wrote: > On Tue, 2016-06-21 at 14:17 -0400, Mike Snitzer wrote: >> On Tue, Jun 21 2016 at 11:44am -0400, >> Kani, Toshimitsu wrote: >> > >> > On Tue, 2016-06-21 at 09:41 -0400, Mike Snitzer wrote: >> > > >> > > On Mon, Jun 20 2016 at 6:22pm

Re: Boot failure on emev2/kzm9d (was: Re: [PATCH v2 11/11] mm/slab: lockless decision to grow cache)

On Wed, Jun 22, 2016 at 05:01:35PM +0200, Geert Uytterhoeven wrote: > On Wed, Jun 22, 2016 at 2:52 AM, Joonsoo Kim wrote: > > Could you try below patch to check who causes the hang? > > > > And, if sysalt-t works when hang, could you get sysalt-t output? I haven't > > used

Re: Boot failure on emev2/kzm9d (was: Re: [PATCH v2 11/11] mm/slab: lockless decision to grow cache)

On Wed, Jun 22, 2016 at 05:01:35PM +0200, Geert Uytterhoeven wrote: > On Wed, Jun 22, 2016 at 2:52 AM, Joonsoo Kim wrote: > > Could you try below patch to check who causes the hang? > > > > And, if sysalt-t works when hang, could you get sysalt-t output? I haven't > > used it before but Paul

[PATCH] Make CONFIG_DEVTMPFS_MOUNT apply to initramfs/initmpfs.

From: Rob Landley Make CONFIG_DEVTMPFS_MOUNT apply to initramfs/initmpfs. Update help text, slightly improve error reporting, move /dev/console open down after devtmpfs mount, don't check IS_ENABLED(CONFIG_TMPFS) before mounting devtmpfs (it's always there, even if just a

[PATCH] Make CONFIG_DEVTMPFS_MOUNT apply to initramfs/initmpfs.

From: Rob Landley Make CONFIG_DEVTMPFS_MOUNT apply to initramfs/initmpfs. Update help text, slightly improve error reporting, move /dev/console open down after devtmpfs mount, don't check IS_ENABLED(CONFIG_TMPFS) before mounting devtmpfs (it's always there, even if just a ramfs alias), and

<    4   5   6   7   8   9   10   11   12   13   >