Re: [PATCH v2 1/9] llist: Provide a safe version for llist_for_each

On Mon, Feb 13, 2017 at 03:52:44PM +0800, Huang, Ying wrote: > Byungchul Park writes: > > > On Mon, Feb 13, 2017 at 03:36:33PM +0800, Huang, Ying wrote: > >> Byungchul Park writes: > >> > >> > Sometimes we have to dereference next field of llist

Re: [PATCH v2 1/9] llist: Provide a safe version for llist_for_each

On Mon, Feb 13, 2017 at 03:52:44PM +0800, Huang, Ying wrote: > Byungchul Park writes: > > > On Mon, Feb 13, 2017 at 03:36:33PM +0800, Huang, Ying wrote: > >> Byungchul Park writes: > >> > >> > Sometimes we have to dereference next field of llist node before entering > >> > loop becasue the

Re: [PATCH v3 1/2] mtd: ifc: Update dependency of IFC for LS1021A

On Mon, 13 Feb 2017 07:39:41 + Alison Wang wrote: > Hi, Boris, > > Sorry, I forgot to change them. Should I resend them or you help to fix > that when applying? I can fix that when applying, no need to resend. Note that you missed 4.11 (already sent my PR to

Re: [PATCH v3 1/2] mtd: ifc: Update dependency of IFC for LS1021A

On Mon, 13 Feb 2017 07:39:41 + Alison Wang wrote: > Hi, Boris, > > Sorry, I forgot to change them. Should I resend them or you help to fix > that when applying? I can fix that when applying, no need to resend. Note that you missed 4.11 (already sent my PR to Brian), I'll queue it

Re: [PATCH V4 2/2] Move stack parameters for sed_ioctl to prevent oversized stack with CONFIG_KASAN

> int sed_ioctl(struct opal_dev *dev, unsigned int cmd, unsigned long ptr) > { > + void *ioctl_ptr; > + int ret = -ENOTTY; > void __user *arg = (void __user *)ptr; Can we use this opportunity to clean up the usual ioctl argument mess. Id say pass the "void __user *argp" argument

Re: [PATCH V4 2/2] Move stack parameters for sed_ioctl to prevent oversized stack with CONFIG_KASAN

> int sed_ioctl(struct opal_dev *dev, unsigned int cmd, unsigned long ptr) > { > + void *ioctl_ptr; > + int ret = -ENOTTY; > void __user *arg = (void __user *)ptr; Can we use this opportunity to clean up the usual ioctl argument mess. Id say pass the "void __user *argp" argument

Re: [PATCH] spi-nor: use ERR_CAST in return

On Mon, 13 Feb 2017 07:35:52 + Nicholas Mc Guire wrote: > On Sun, Feb 12, 2017 at 11:04:10PM +0100, Boris Brezillon wrote: > > +Mika > > > > On Sun, 12 Feb 2017 22:45:43 +0100 > > Boris Brezillon wrote: > > > > > On Sun, 12 Feb 2017

Re: [PATCH] spi-nor: use ERR_CAST in return

On Mon, 13 Feb 2017 07:35:52 + Nicholas Mc Guire wrote: > On Sun, Feb 12, 2017 at 11:04:10PM +0100, Boris Brezillon wrote: > > +Mika > > > > On Sun, 12 Feb 2017 22:45:43 +0100 > > Boris Brezillon wrote: > > > > > On Sun, 12 Feb 2017 17:43:43 +0100 > > > Nicholas Mc Guire wrote: > > >

Re: [PATCH v2 1/9] llist: Provide a safe version for llist_for_each

Byungchul Park writes: > On Mon, Feb 13, 2017 at 03:36:33PM +0800, Huang, Ying wrote: >> Byungchul Park writes: >> >> > Sometimes we have to dereference next field of llist node before entering >> > loop becasue the node might be deleted or the

Re: [PATCH v2 1/9] llist: Provide a safe version for llist_for_each

Byungchul Park writes: > On Mon, Feb 13, 2017 at 03:36:33PM +0800, Huang, Ying wrote: >> Byungchul Park writes: >> >> > Sometimes we have to dereference next field of llist node before entering >> > loop becasue the node might be deleted or the next field might be >> > modified within the

Re: [PATCH V4 1/2] uapi: sed-opal fix IOW for activate lsp to use correct struct

Looks fine, Reviewed-by: Christoph Hellwig

Re: [PATCH V4 1/2] uapi: sed-opal fix IOW for activate lsp to use correct struct

Looks fine, Reviewed-by: Christoph Hellwig

Re: [PATCH v6 7/8] uapi: export all headers under uapi directories

> linux/genwqe/..install.cmd > linux/genwqe/.install Third time: NAK on exporting internal kbuild metadata.

Re: [PATCH v6 7/8] uapi: export all headers under uapi directories

> linux/genwqe/..install.cmd > linux/genwqe/.install Third time: NAK on exporting internal kbuild metadata.

RE: [PATCH 2/2] x86/vdso: Add VCLOCK_HVCLOCK vDSO clock read method

> From: Thomas Gleixner [mailto:t...@linutronix.de] > Sent: Saturday, February 11, 2017 02:02 > ... > That's important if the stuff happens cross CPU. If the update happens on > the same CPU then this is a different story and as there are VMexits > involved they might provide the required

RE: [PATCH 2/2] x86/vdso: Add VCLOCK_HVCLOCK vDSO clock read method

> From: Thomas Gleixner [mailto:t...@linutronix.de] > Sent: Saturday, February 11, 2017 02:02 > ... > That's important if the stuff happens cross CPU. If the update happens on > the same CPU then this is a different story and as there are VMexits > involved they might provide the required

Re: [PATCH v2 5/6] drm: convert drivers to use drm_of_find_panel_or_bridge

On Thu, 9 Feb 2017 13:05:57 -0600 Rob Herring wrote: > Similar to the previous commit, convert drivers open coding OF graph > parsing to use drm_of_find_panel_or_bridge instead. > > This changes some error messages to debug messages (in the graph core). > Graph connections are

Re: [PATCH v2 5/6] drm: convert drivers to use drm_of_find_panel_or_bridge

On Thu, 9 Feb 2017 13:05:57 -0600 Rob Herring wrote: > Similar to the previous commit, convert drivers open coding OF graph > parsing to use drm_of_find_panel_or_bridge instead. > > This changes some error messages to debug messages (in the graph core). > Graph connections are often "no

Re: [PATCH v2] gpio: return NULL from gpiod_get_optional when GPIOLIB is disabled

Hello, On Sun, Feb 12, 2017 at 05:15:01PM -0800, Dmitry Torokhov wrote: > On Sun, Feb 12, 2017 at 05:13:55PM -0800, Dmitry Torokhov wrote: > > Given the intent behind gpiod_get_optional() and friends it does not make > > sense to return -ENOSYS when GPIOLIB is disabled: the driver is expected to

Re: [PATCH v2] gpio: return NULL from gpiod_get_optional when GPIOLIB is disabled

Hello, On Sun, Feb 12, 2017 at 05:15:01PM -0800, Dmitry Torokhov wrote: > On Sun, Feb 12, 2017 at 05:13:55PM -0800, Dmitry Torokhov wrote: > > Given the intent behind gpiod_get_optional() and friends it does not make > > sense to return -ENOSYS when GPIOLIB is disabled: the driver is expected to

Re: [PATCH v2 1/9] llist: Provide a safe version for llist_for_each

On Mon, Feb 13, 2017 at 03:36:33PM +0800, Huang, Ying wrote: > Byungchul Park writes: > > > Sometimes we have to dereference next field of llist node before entering > > loop becasue the node might be deleted or the next field might be > > modified within the loop. So

Re: [PATCH v2 1/9] llist: Provide a safe version for llist_for_each

On Mon, Feb 13, 2017 at 03:36:33PM +0800, Huang, Ying wrote: > Byungchul Park writes: > > > Sometimes we have to dereference next field of llist node before entering > > loop becasue the node might be deleted or the next field might be > > modified within the loop. So this adds the safe version

Re: [PATCH RFC] spi-nor: provide a range for poll_timout

On Sun, Feb 12, 2017 at 10:59:23PM +0100, Boris Brezillon wrote: > +Mika > > On Sun, 12 Feb 2017 17:42:57 +0100 > Nicholas Mc Guire wrote: > > > The overall poll time here is INTEL_SPI_TIMEOUT * 1000 which is > > 5000 * 1000 - so 5seconds and it is coded as a tight loop here

RE: [PATCH v3 1/2] mtd: ifc: Update dependency of IFC for LS1021A

Hi, Boris, Sorry, I forgot to change them. Should I resend them or you help to fix that when applying? Best Regards, Alison Wang > > Hi Alison, > > The subject prefix is still wrong, should be 'memory: ifc: '. > > On Mon, 13 Feb 2017 14:46:55 +0800 > Alison Wang

Re: [PATCH RFC] spi-nor: provide a range for poll_timout

On Sun, Feb 12, 2017 at 10:59:23PM +0100, Boris Brezillon wrote: > +Mika > > On Sun, 12 Feb 2017 17:42:57 +0100 > Nicholas Mc Guire wrote: > > > The overall poll time here is INTEL_SPI_TIMEOUT * 1000 which is > > 5000 * 1000 - so 5seconds and it is coded as a tight loop here delay_us > > to

RE: [PATCH v3 1/2] mtd: ifc: Update dependency of IFC for LS1021A

Hi, Boris, Sorry, I forgot to change them. Should I resend them or you help to fix that when applying? Best Regards, Alison Wang > > Hi Alison, > > The subject prefix is still wrong, should be 'memory: ifc: '. > > On Mon, 13 Feb 2017 14:46:55 +0800 > Alison Wang wrote: > > > As

Re: [PATCH v3 2/2] gpio: mockup: implement event injecting over debugfs

On Mon, Feb 6, 2017 at 3:11 PM, Bartosz Golaszewski wrote: > Create a debugfs directory for every mockup chip and a single file > for every line. Writing (0 or 1) to these files allows the user to > inject line events (falling or rising edge respectively). > >

Re: [PATCH v3 2/2] gpio: mockup: implement event injecting over debugfs

On Mon, Feb 6, 2017 at 3:11 PM, Bartosz Golaszewski wrote: > Create a debugfs directory for every mockup chip and a single file > for every line. Writing (0 or 1) to these files allows the user to > inject line events (falling or rising edge respectively). > > Signed-off-by: Bartosz Golaszewski

Re: [PATCH] spi-nor: use true/false for bool

On Sun, Feb 12, 2017 at 11:01:44PM +0100, Boris Brezillon wrote: > +Mika > > On Sun, 12 Feb 2017 22:50:44 +0100 > Boris Brezillon wrote: > > > On Sun, 12 Feb 2017 17:43:31 +0100 > > Nicholas Mc Guire wrote: > > > > > writeable in struct

Re: [PATCH] spi-nor: use true/false for bool

On Sun, Feb 12, 2017 at 11:01:44PM +0100, Boris Brezillon wrote: > +Mika > > On Sun, 12 Feb 2017 22:50:44 +0100 > Boris Brezillon wrote: > > > On Sun, 12 Feb 2017 17:43:31 +0100 > > Nicholas Mc Guire wrote: > > > > > writeable in struct intel_spi is a boolean and assignment should be to > >

Re: [PATCH v3 1/2] gpio: mockup: add a dummy irqchip

On Mon, Feb 6, 2017 at 3:11 PM, Bartosz Golaszewski wrote: > Setup a dummy irqchip that will allow us to inject line events for > testing purposes. > > Signed-off-by: Bartosz Golaszewski Patch applied. Yours, Linus Walleij

Re: [PATCH] spi-nor: use ERR_CAST in return

On Sun, Feb 12, 2017 at 11:04:10PM +0100, Boris Brezillon wrote: > +Mika > > On Sun, 12 Feb 2017 22:45:43 +0100 > Boris Brezillon wrote: > > > On Sun, 12 Feb 2017 17:43:43 +0100 > > Nicholas Mc Guire wrote: > > > > > This fixes a sparse

Re: [PATCH v2 1/9] llist: Provide a safe version for llist_for_each

Byungchul Park writes: > Sometimes we have to dereference next field of llist node before entering > loop becasue the node might be deleted or the next field might be > modified within the loop. So this adds the safe version of llist_for_each, > that is,

Re: [PATCH v3 1/2] gpio: mockup: add a dummy irqchip

On Mon, Feb 6, 2017 at 3:11 PM, Bartosz Golaszewski wrote: > Setup a dummy irqchip that will allow us to inject line events for > testing purposes. > > Signed-off-by: Bartosz Golaszewski Patch applied. Yours, Linus Walleij

Re: [PATCH] spi-nor: use ERR_CAST in return

On Sun, Feb 12, 2017 at 11:04:10PM +0100, Boris Brezillon wrote: > +Mika > > On Sun, 12 Feb 2017 22:45:43 +0100 > Boris Brezillon wrote: > > > On Sun, 12 Feb 2017 17:43:43 +0100 > > Nicholas Mc Guire wrote: > > > > > This fixes a sparse warning about > > > > Your commit message seems to

Re: [PATCH v2 1/9] llist: Provide a safe version for llist_for_each

Byungchul Park writes: > Sometimes we have to dereference next field of llist node before entering > loop becasue the node might be deleted or the next field might be > modified within the loop. So this adds the safe version of llist_for_each, > that is, llist_for_each_safe. > > Signed-off-by:

Re: [PATCH v3 1/2] mtd: ifc: Update dependency of IFC for LS1021A

Hi Alison, The subject prefix is still wrong, should be 'memory: ifc: '. On Mon, 13 Feb 2017 14:46:55 +0800 Alison Wang wrote: > As Freescale/NXP IFC controller is available on LS1021A, the dependency > for LS1021A is added. > > LS1021A is an earlier product and is not

Re: [PATCH v3 1/2] mtd: ifc: Update dependency of IFC for LS1021A

Hi Alison, The subject prefix is still wrong, should be 'memory: ifc: '. On Mon, 13 Feb 2017 14:46:55 +0800 Alison Wang wrote: > As Freescale/NXP IFC controller is available on LS1021A, the dependency > for LS1021A is added. > > LS1021A is an earlier product and is not compatible with later >

[PATCH v2 1/9] llist: Provide a safe version for llist_for_each

Sometimes we have to dereference next field of llist node before entering loop becasue the node might be deleted or the next field might be modified within the loop. So this adds the safe version of llist_for_each, that is, llist_for_each_safe. Signed-off-by: Byungchul Park

[PATCH v2 1/9] llist: Provide a safe version for llist_for_each

Sometimes we have to dereference next field of llist node before entering loop becasue the node might be deleted or the next field might be modified within the loop. So this adds the safe version of llist_for_each, that is, llist_for_each_safe. Signed-off-by: Byungchul Park ---

[PATCH v2 6/9] namespace.c: Don't reinvent the wheel but use existing llist API

Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- fs/namespace.c | 12 +--- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/fs/namespace.c b/fs/namespace.c index b5b1259..5cb2229 100644 ---

[PATCH v2 0/9] Don't reinvent the wheel but use existing llist API

Change from v1 - split one patch to several ones, one for each subsystem. - replace for_each with the safe version where it's necessary. Byungchul Park (9): llist: Provide a safe version for llist_for_each bcache: Don't reinvent the wheel but use existing llist API raid5: Don't reinvent the

[PATCH v2 6/9] namespace.c: Don't reinvent the wheel but use existing llist API

Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- fs/namespace.c | 12 +--- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/fs/namespace.c b/fs/namespace.c index b5b1259..5cb2229 100644 --- a/fs/namespace.c +++

[PATCH v2 0/9] Don't reinvent the wheel but use existing llist API

Change from v1 - split one patch to several ones, one for each subsystem. - replace for_each with the safe version where it's necessary. Byungchul Park (9): llist: Provide a safe version for llist_for_each bcache: Don't reinvent the wheel but use existing llist API raid5: Don't reinvent the

[PATCH v2 9/9] mm: Don't reinvent the wheel but use existing llist API

Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- mm/vmalloc.c | 10 -- 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/mm/vmalloc.c b/mm/vmalloc.c index 3ca82d4..8c0eb45 100644 ---

[PATCH v2 7/9] irq_work: Don't reinvent the wheel but use existing llist API

Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- kernel/irq_work.c | 6 +- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/kernel/irq_work.c b/kernel/irq_work.c index bcf107c..e2ebe8c 100644 ---

[PATCH v2 9/9] mm: Don't reinvent the wheel but use existing llist API

Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- mm/vmalloc.c | 10 -- 1 file changed, 4 insertions(+), 6 deletions(-) diff --git a/mm/vmalloc.c b/mm/vmalloc.c index 3ca82d4..8c0eb45 100644 --- a/mm/vmalloc.c +++ b/mm/vmalloc.c

[PATCH v2 7/9] irq_work: Don't reinvent the wheel but use existing llist API

Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- kernel/irq_work.c | 6 +- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/kernel/irq_work.c b/kernel/irq_work.c index bcf107c..e2ebe8c 100644 --- a/kernel/irq_work.c +++

[PATCH v2 2/9] bcache: Don't reinvent the wheel but use existing llist API

Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- drivers/md/bcache/closure.c | 17 +++-- 1 file changed, 3 insertions(+), 14 deletions(-) diff --git a/drivers/md/bcache/closure.c

[PATCH v2 2/9] bcache: Don't reinvent the wheel but use existing llist API

Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- drivers/md/bcache/closure.c | 17 +++-- 1 file changed, 3 insertions(+), 14 deletions(-) diff --git a/drivers/md/bcache/closure.c b/drivers/md/bcache/closure.c index

[PATCH v2 3/9] raid5: Don't reinvent the wheel but use existing llist API

Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- drivers/md/raid5.c | 6 ++ 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/drivers/md/raid5.c b/drivers/md/raid5.c index 36c13e4..22a0326 100644

[PATCH v2 8/9] sched: Don't reinvent the wheel but use existing llist API

Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- kernel/sched/core.c | 13 ++--- 1 file changed, 2 insertions(+), 11 deletions(-) diff --git a/kernel/sched/core.c b/kernel/sched/core.c index

[PATCH v2 5/9] fput: Don't reinvent the wheel but use existing llist API

Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- fs/file_table.c | 12 +--- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/fs/file_table.c b/fs/file_table.c index 6d982b5..3209da2 100644 ---

[PATCH v2 8/9] sched: Don't reinvent the wheel but use existing llist API

Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- kernel/sched/core.c | 13 ++--- 1 file changed, 2 insertions(+), 11 deletions(-) diff --git a/kernel/sched/core.c b/kernel/sched/core.c index d01f9d0..417060b 100644 ---

[PATCH v2 5/9] fput: Don't reinvent the wheel but use existing llist API

Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- fs/file_table.c | 12 +--- 1 file changed, 5 insertions(+), 7 deletions(-) diff --git a/fs/file_table.c b/fs/file_table.c index 6d982b5..3209da2 100644 --- a/fs/file_table.c +++

[PATCH v2 3/9] raid5: Don't reinvent the wheel but use existing llist API

Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- drivers/md/raid5.c | 6 ++ 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/drivers/md/raid5.c b/drivers/md/raid5.c index 36c13e4..22a0326 100644 --- a/drivers/md/raid5.c

[PATCH v2 4/9] vhost/scsi: Don't reinvent the wheel but use existing llist API

Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- drivers/vhost/scsi.c | 11 +++ 1 file changed, 3 insertions(+), 8 deletions(-) diff --git a/drivers/vhost/scsi.c b/drivers/vhost/scsi.c index

[PATCH v2 4/9] vhost/scsi: Don't reinvent the wheel but use existing llist API

Although llist provides proper APIs, they are not used. Make them used. Signed-off-by: Byungchul Park --- drivers/vhost/scsi.c | 11 +++ 1 file changed, 3 insertions(+), 8 deletions(-) diff --git a/drivers/vhost/scsi.c b/drivers/vhost/scsi.c index 253310c..a4cb966 100644 ---

[PATCH v3 2/2] mtd: nand: Update dependency of IFC for LS1021A

As NAND support for Freescale/NXP IFC controller is available on LS1021A, the dependency for LS1021A is added. LS1021A is an earlier product and is not compatible with later LayerScape architecture. So ARCH_LAYERSCAPE can't cover LS1021A. Signed-off-by: Alison Wang ---

[PATCH v3 2/2] mtd: nand: Update dependency of IFC for LS1021A

As NAND support for Freescale/NXP IFC controller is available on LS1021A, the dependency for LS1021A is added. LS1021A is an earlier product and is not compatible with later LayerScape architecture. So ARCH_LAYERSCAPE can't cover LS1021A. Signed-off-by: Alison Wang --- Changes in v3: - Update

RE: [PATCH v2 2/2] mtd: nand: Update dependency of IFC for LS1021A

Hi, Boris, > On Thu, 5 Jan 2017 02:02:30 + > Alison Wang wrote: > > > > On 01/04/2017 02:46 AM, Alison Wang wrote: > > > >> On 01/03/2017 03:41 AM, Alison Wang wrote: > > > >>> As NAND support for Freescale/NXP IFC controller is available > on > > > >>> LS1021A, the

RE: [PATCH v2 2/2] mtd: nand: Update dependency of IFC for LS1021A

Hi, Boris, > On Thu, 5 Jan 2017 02:02:30 + > Alison Wang wrote: > > > > On 01/04/2017 02:46 AM, Alison Wang wrote: > > > >> On 01/03/2017 03:41 AM, Alison Wang wrote: > > > >>> As NAND support for Freescale/NXP IFC controller is available > on > > > >>> LS1021A, the dependency for LS1021A

[PATCH v3 1/2] mtd: ifc: Update dependency of IFC for LS1021A

As Freescale/NXP IFC controller is available on LS1021A, the dependency for LS1021A is added. LS1021A is an earlier product and is not compatible with later LayerScape architecture. So ARCH_LAYERSCAPE can't cover LS1021A. Signed-off-by: Alison Wang --- Changes in v3: -

[PATCH v3 1/2] mtd: ifc: Update dependency of IFC for LS1021A

As Freescale/NXP IFC controller is available on LS1021A, the dependency for LS1021A is added. LS1021A is an earlier product and is not compatible with later LayerScape architecture. So ARCH_LAYERSCAPE can't cover LS1021A. Signed-off-by: Alison Wang --- Changes in v3: - Update the commit

Re: [PATCH 0/3] s390: audit and remove needless module.h includes

On Thu, Feb 09, 2017 at 03:20:22PM -0500, Paul Gortmaker wrote: > Paul Gortmaker (3): > s390: kernel: Audit and remove any unnecessary uses of module.h > s390: mm: Audit and remove any unnecessary uses of module.h > s390: Audit and remove any remaining unnecessary uses of module.h Applied,

Re: [PATCH 0/3] s390: audit and remove needless module.h includes

On Thu, Feb 09, 2017 at 03:20:22PM -0500, Paul Gortmaker wrote: > Paul Gortmaker (3): > s390: kernel: Audit and remove any unnecessary uses of module.h > s390: mm: Audit and remove any unnecessary uses of module.h > s390: Audit and remove any remaining unnecessary uses of module.h Applied,

Re: [PATCH] perf: Fix CONFIG_KPROBE_EVENTS and CONFIG_UPROBE_EVENTS typos

* Anton Blanchard wrote: > From: Anton Blanchard > > Fix some incorrect Kconfig options, they should be CONFIG_KPROBE_EVENT > and CONFIG_UPROBE_EVENT. > > Signed-off-by: Anton Blanchard > --- > arch/sparc/configs/sparc64_defconfig | 2 +-

Re: [PATCH] perf: Fix CONFIG_KPROBE_EVENTS and CONFIG_UPROBE_EVENTS typos

* Anton Blanchard wrote: > From: Anton Blanchard > > Fix some incorrect Kconfig options, they should be CONFIG_KPROBE_EVENT > and CONFIG_UPROBE_EVENT. > > Signed-off-by: Anton Blanchard > --- > arch/sparc/configs/sparc64_defconfig | 2 +- > tools/perf/util/probe-file.c | 8

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

Hi Paul, On Sun, 12 Feb 2017 20:37:48 -0800 "Paul E. McKenney" wrote: > > I chickened out on that commit for this merge window, so it will come > back at -rc1. But I will cover that when I rebase to -rc1. OK, thanks. -- Cheers, Stephen Rothwell

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

Hi Paul, On Sun, 12 Feb 2017 20:37:48 -0800 "Paul E. McKenney" wrote: > > I chickened out on that commit for this merge window, so it will come > back at -rc1. But I will cover that when I rebase to -rc1. OK, thanks. -- Cheers, Stephen Rothwell

Re: [PATCH] Make EN2 pin optional in the TRF7970A driver

Hello Rob, Am 10.02.2017 um 16:51 schrieb Rob Herring: On Tue, Feb 07, 2017 at 06:22:04AM +0100, Heiko Schocher wrote: From: Guan Ben Make the EN2 pin optional. This is useful for boards, which have this pin fix wired, for example to ground. Signed-off-by: Guan Ben

Re: [PATCH] Make EN2 pin optional in the TRF7970A driver

Hello Rob, Am 10.02.2017 um 16:51 schrieb Rob Herring: On Tue, Feb 07, 2017 at 06:22:04AM +0100, Heiko Schocher wrote: From: Guan Ben Make the EN2 pin optional. This is useful for boards, which have this pin fix wired, for example to ground. Signed-off-by: Guan Ben Signed-off-by: Mark

linux-next: Tree for Feb 13

Hi all, Changes since 20170210: The ipsec-next tree gained a conflict against the net-next tree. The rdma-leon gained a conflict against Linus' tree. The l2mtd-tree lost its build failure. Non-merge commits (relative to Linus' tree): 8646 9682 files changed, 388711 insertions(+), 182504

linux-next: Tree for Feb 13

Hi all, Changes since 20170210: The ipsec-next tree gained a conflict against the net-next tree. The rdma-leon gained a conflict against Linus' tree. The l2mtd-tree lost its build failure. Non-merge commits (relative to Linus' tree): 8646 9682 files changed, 388711 insertions(+), 182504

Re: [PATCH 1/1] dma: imx-sdma: add 1ms delay to ensure SDMA channel is stopped

Hello Vinod On 02/13/2017 11:05 AM, Vinod Koul wrote: On Fri, Feb 10, 2017 at 06:46:45AM -0800, jiada_w...@mentor.com wrote: From: Jiada Wang sdma_disable_channel() cannot ensure dma is stopped to access module's FIFOs. Maybe SDMA core is running and accessing BD when

Re: [PATCH 1/1] dma: imx-sdma: add 1ms delay to ensure SDMA channel is stopped

Hello Vinod On 02/13/2017 11:05 AM, Vinod Koul wrote: On Fri, Feb 10, 2017 at 06:46:45AM -0800, jiada_w...@mentor.com wrote: From: Jiada Wang sdma_disable_channel() cannot ensure dma is stopped to access module's FIFOs. Maybe SDMA core is running and accessing BD when disable of

Re: [PATCH] Input: tsc2004/5 - do not use irq_set_irq_wake() directly

Hi, On Sun, Feb 12, 2017 at 03:43:33PM -0800, Dmitry Torokhov wrote: > Instead of setting irq_set_irq_wake() directly in probe(), mark the device > as wakeup-capable, and use enable_irq_wake() and disable_irq_wake() in > suspend/resume path. > > Signed-off-by: Dmitry Torokhov

Re: [PATCH] Input: tsc2004/5 - do not use irq_set_irq_wake() directly

Hi, On Sun, Feb 12, 2017 at 03:43:33PM -0800, Dmitry Torokhov wrote: > Instead of setting irq_set_irq_wake() directly in probe(), mark the device > as wakeup-capable, and use enable_irq_wake() and disable_irq_wake() in > suspend/resume path. > > Signed-off-by: Dmitry Torokhov Reviewed-By:

[PATCH RFC 2/3] coresight: add support for debug module

Coresight includes debug module and usually the module connects with CPU debug logic. ARMv8 architecture reference manual (ARMv8-ARM) has defined the debug registers in the chapter "H9: External Debug Register Descriptions". After enable the debug module we can check CPU state and PC value, etc.

[PATCH RFC 3/3] arm64: dts: register Hi6220's coresight debug module

Bind coresight debug driver for Hi6220. Signed-off-by: Leo Yan --- .../boot/dts/hisilicon/hikey_6220_coresight.dtsi | 73 ++ 1 file changed, 73 insertions(+) diff --git a/arch/arm64/boot/dts/hisilicon/hikey_6220_coresight.dtsi

[PATCH RFC 3/3] arm64: dts: register Hi6220's coresight debug module

Bind coresight debug driver for Hi6220. Signed-off-by: Leo Yan --- .../boot/dts/hisilicon/hikey_6220_coresight.dtsi | 73 ++ 1 file changed, 73 insertions(+) diff --git a/arch/arm64/boot/dts/hisilicon/hikey_6220_coresight.dtsi

[PATCH RFC 2/3] coresight: add support for debug module

Coresight includes debug module and usually the module connects with CPU debug logic. ARMv8 architecture reference manual (ARMv8-ARM) has defined the debug registers in the chapter "H9: External Debug Register Descriptions". After enable the debug module we can check CPU state and PC value, etc.

Re: [PATCH] Input: pwm-beeper: support customized freq for SND_BELL

Hello Rob, Am 10.02.2017 um 16:48 schrieb Rob Herring: On Tue, Feb 07, 2017 at 06:21:34AM +0100, Heiko Schocher wrote: From: Guan Ben extend the pwm-beeper driver to support customized frequency for SND_BELL from device tree. Signed-off-by: Guan Ben

[PATCH RFC 1/3] coresight: binding for coresight debug driver

Adding compatible string for new coresight debug driver. Signed-off-by: Leo Yan --- Documentation/devicetree/bindings/arm/coresight.txt | 9 +++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/Documentation/devicetree/bindings/arm/coresight.txt

Re: [PATCH] Input: pwm-beeper: support customized freq for SND_BELL

Hello Rob, Am 10.02.2017 um 16:48 schrieb Rob Herring: On Tue, Feb 07, 2017 at 06:21:34AM +0100, Heiko Schocher wrote: From: Guan Ben extend the pwm-beeper driver to support customized frequency for SND_BELL from device tree. Signed-off-by: Guan Ben Signed-off-by: Mark Jonas

[PATCH RFC 1/3] coresight: binding for coresight debug driver

Adding compatible string for new coresight debug driver. Signed-off-by: Leo Yan --- Documentation/devicetree/bindings/arm/coresight.txt | 9 +++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/Documentation/devicetree/bindings/arm/coresight.txt

[PATCH RFC 0/3] coresight: enable debug module

This patch series is to enable coresight debug module. With debug module we can check CPU state and PC value, etc. So this is helpful for CPU lockup bugs, e.g. if one CPU has run into infinite loop with IRQ disabled. The hang CPU cannot switch context and handle any interrupt, so it cannot handle

[PATCH RFC 0/3] coresight: enable debug module

This patch series is to enable coresight debug module. With debug module we can check CPU state and PC value, etc. So this is helpful for CPU lockup bugs, e.g. if one CPU has run into infinite loop with IRQ disabled. The hang CPU cannot switch context and handle any interrupt, so it cannot handle

[PATCH] x86: kernel: fix unused variable warning in vm86_32.c

If CONFIG_TRANSPARENT_HUGEPAGE is not set in kernel config, a warning is shown in vm86_32.c. The warning is as follows: >arch/x86/kernel/vm86_32.c: In function ‘mark_screen_rdonly’: >arch/x86/kernel/vm86_32.c:180:26: warning: unused variable ‘vma’ >[-Wunused-variable] > struct vm_area_struct

[PATCH] x86: kernel: fix unused variable warning in vm86_32.c

If CONFIG_TRANSPARENT_HUGEPAGE is not set in kernel config, a warning is shown in vm86_32.c. The warning is as follows: >arch/x86/kernel/vm86_32.c: In function ‘mark_screen_rdonly’: >arch/x86/kernel/vm86_32.c:180:26: warning: unused variable ‘vma’ >[-Wunused-variable] > struct vm_area_struct

Re: [lkp] [x86/acpi] dc6db24d24: BUG: unable to handle kernel paging request at 0000116007090008

Hi, liyang On 02/13, Dou Liyang wrote: >Hi, Xiaolong > >At 02/13/2017 09:37 AM, Ye Xiaolong wrote: >>On 11/21, Dou Liyang wrote: >>>Hi, Xiaolong, >>> >>>At 11/21/2016 09:31 AM, Ye Xiaolong wrote: On 11/18, Dou Liyang wrote: >Hi xiaolong > >At 11/18/2016 02:16 PM, Ye Xiaolong

Re: [lkp] [x86/acpi] dc6db24d24: BUG: unable to handle kernel paging request at 0000116007090008

Hi, liyang On 02/13, Dou Liyang wrote: >Hi, Xiaolong > >At 02/13/2017 09:37 AM, Ye Xiaolong wrote: >>On 11/21, Dou Liyang wrote: >>>Hi, Xiaolong, >>> >>>At 11/21/2016 09:31 AM, Ye Xiaolong wrote: On 11/18, Dou Liyang wrote: >Hi xiaolong > >At 11/18/2016 02:16 PM, Ye Xiaolong

Re: [RFC][PATCH 12/21] tracing: Account for variables in named trigger compatibility

On Wed, Feb 08, 2017 at 11:25:08AM -0600, Tom Zanussi wrote: > Named triggers must also have the same set of variables in order to be > considered compatible - update the trigger match test to account for > that. > > The reason for this requirement is that named triggers with variables > are

Re: [RFC][PATCH 12/21] tracing: Account for variables in named trigger compatibility

On Wed, Feb 08, 2017 at 11:25:08AM -0600, Tom Zanussi wrote: > Named triggers must also have the same set of variables in order to be > considered compatible - update the trigger match test to account for > that. > > The reason for this requirement is that named triggers with variables > are

Re: [RFC][PATCH 11/21] tracing: Add variable support to hist triggers

On Wed, Feb 08, 2017 at 11:25:07AM -0600, Tom Zanussi wrote: > Add support for saving the value of a current event's event field by > assigning it to a variable that can be read by a subsequent event. > > The basic syntax for saving a variable is to simply prefix a unique > variable name not

Re: [RFC][PATCH 11/21] tracing: Add variable support to hist triggers

On Wed, Feb 08, 2017 at 11:25:07AM -0600, Tom Zanussi wrote: > Add support for saving the value of a current event's event field by > assigning it to a variable that can be read by a subsequent event. > > The basic syntax for saving a variable is to simply prefix a unique > variable name not

Re: [PATCH] llist: Don't reinvent the wheel but use existing llist API

On Mon, Feb 13, 2017 at 05:43:26AM +, Al Viro wrote: > On Mon, Feb 13, 2017 at 01:10:13PM +0900, Byungchul Park wrote: > > Although llist provides proper APIs, they are not used. Make them used. > > > @@ -231,12 +231,10 @@ static void __fput(struct file *file) > > static void

Re: [PATCH] llist: Don't reinvent the wheel but use existing llist API

On Mon, Feb 13, 2017 at 05:43:26AM +, Al Viro wrote: > On Mon, Feb 13, 2017 at 01:10:13PM +0900, Byungchul Park wrote: > > Although llist provides proper APIs, they are not used. Make them used. > > > @@ -231,12 +231,10 @@ static void __fput(struct file *file) > > static void

Re: [PATCH] llist: Don't reinvent the wheel but use existing llist API

On Mon, Feb 13, 2017 at 01:38:36PM +0800, Huang, Ying wrote: > Hi, Byungchul, > > Byungchul Park writes: > > > Although llist provides proper APIs, they are not used. Make them used. > > > > Signed-off-by: Byungchul Park > > --- > >

Re: [PATCH] llist: Don't reinvent the wheel but use existing llist API

On Mon, Feb 13, 2017 at 01:38:36PM +0800, Huang, Ying wrote: > Hi, Byungchul, > > Byungchul Park writes: > > > Although llist provides proper APIs, they are not used. Make them used. > > > > Signed-off-by: Byungchul Park > > --- > > drivers/md/bcache/closure.c | 15 ++- > >

  1   2   3   4   5   6   7   >