Re: [PATCH 2/5] clk: qcom: ipq8074: Add Global Clock Controller support

Hi Abhishek, [auto build test WARNING on robh/for-next] [also build test WARNING on v4.11-rc8 next-20170428] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Varadarajan-Narayanan/Add-minimal

Re: [PATCH 2/5] clk: qcom: ipq8074: Add Global Clock Controller support

Hi Abhishek, [auto build test WARNING on robh/for-next] [also build test WARNING on v4.11-rc8 next-20170428] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Varadarajan-Narayanan/Add-minimal

[PATCH] clk: qcom: ipq8074: fix platform_no_drv_owner.cocci warnings

drivers/clk/qcom/gcc-ipq8074.c:1014:3-8: No need to set .owner here. The core will do it. Remove .owner field if calls are used which set it automatically Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci CC: Abhishek Sahu Signed-off-by: Fengguang Wu

[PATCH] clk: qcom: ipq8074: fix platform_no_drv_owner.cocci warnings

drivers/clk/qcom/gcc-ipq8074.c:1014:3-8: No need to set .owner here. The core will do it. Remove .owner field if calls are used which set it automatically Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci CC: Abhishek Sahu Signed-off-by: Fengguang Wu --- gcc-ipq8074.c |

Re: [PATCH] firmware: google: memconsole: Adapt to new coreboot ring buffer format

On Fri, Apr 28, 2017 at 01:44:45PM -0700, Julius Werner wrote: > > -8< > > That needs to go below the --- line, not above it. > > > Really? git am --scissors seems to do the right thing for me this way... Ah, never

Re: [PATCH v2 2/3] firmware: google: memconsole: Escape unprintable characters

On Fri, Apr 28, 2017 at 01:42:24PM -0700, Julius Werner wrote: > Recent improvements in coreboot's memory console allow it to contain > logs from more than one boot as long as the information persists in > memory. Since trying to persist a memory buffer across reboots often > doesn't quite work

Re: [PATCH] firmware: google: memconsole: Adapt to new coreboot ring buffer format

On Fri, Apr 28, 2017 at 01:44:45PM -0700, Julius Werner wrote: > > -8< > > That needs to go below the --- line, not above it. > > > Really? git am --scissors seems to do the right thing for me this way... Ah, never

Re: [PATCH v2 2/3] firmware: google: memconsole: Escape unprintable characters

On Fri, Apr 28, 2017 at 01:42:24PM -0700, Julius Werner wrote: > Recent improvements in coreboot's memory console allow it to contain > logs from more than one boot as long as the information persists in > memory. Since trying to persist a memory buffer across reboots often > doesn't quite work

Re: [PATCH] staging: fbtft: fbtft-core.c: EXPORT_SYMBOL should immediately follow its function

On Sat, Apr 29, 2017 at 01:07:34AM +0200, Shiva Kerdel wrote: > This patch fixes the following checkpatch.pl warning > - EXPORT_SYMBOL(foo); should immediately follow its function/variable > > Signed-off-by: Shiva Kerdel > --- > drivers/staging/fbtft/fbtft-core.c | 25

Re: [PATCH] staging: fbtft: fbtft-core.c: EXPORT_SYMBOL should immediately follow its function

On Sat, Apr 29, 2017 at 01:07:34AM +0200, Shiva Kerdel wrote: > This patch fixes the following checkpatch.pl warning > - EXPORT_SYMBOL(foo); should immediately follow its function/variable > > Signed-off-by: Shiva Kerdel > --- > drivers/staging/fbtft/fbtft-core.c | 25 +++--

Re: [PATCH] staging: comedi: use memdup_user

On Fri, Apr 28, 2017 at 06:53:32PM -0700, Joe Perches wrote: > On Sat, 2017-04-29 at 09:45 +0800, Geliang Tang wrote: > > Use memdup_user() helper instead of open-coding to simplify the code. > > While I doubt this is a problem, this loses > the multiplication overflow check for > sizeof(*insns)

Re: [PATCH] staging: comedi: use memdup_user

On Fri, Apr 28, 2017 at 06:53:32PM -0700, Joe Perches wrote: > On Sat, 2017-04-29 at 09:45 +0800, Geliang Tang wrote: > > Use memdup_user() helper instead of open-coding to simplify the code. > > While I doubt this is a problem, this loses > the multiplication overflow check for > sizeof(*insns)

Re: [PATCH v6 2/5] firmware: add extensible driver data API

On Fri, Apr 28, 2017 at 12:19:05PM +0900, AKASHI Takahiro wrote: > > > > + ret = _request_firmware(_data, name, , device); > > > > + if (ret && driver_data_param_optional(req_params)) > > > > + ret = driver_data_sync_opt_call_cb(req_params); > > > > + else > > > > +

Re: [PATCH v6 2/5] firmware: add extensible driver data API

On Fri, Apr 28, 2017 at 12:19:05PM +0900, AKASHI Takahiro wrote: > > > > + ret = _request_firmware(_data, name, , device); > > > > + if (ret && driver_data_param_optional(req_params)) > > > > + ret = driver_data_sync_opt_call_cb(req_params); > > > > + else > > > > +

[PATCH v2] Introduce v3 namespaced file capabilities

Root in a non-initial user ns cannot be trusted to write a traditional security.capability xattr. If it were allowed to do so, then any unprivileged user on the host could map his own uid to root in a private namespace, write the xattr, and execute the file with privilege on the host. However

[PATCH v2] Introduce v3 namespaced file capabilities

Root in a non-initial user ns cannot be trusted to write a traditional security.capability xattr. If it were allowed to do so, then any unprivileged user on the host could map his own uid to root in a private namespace, write the xattr, and execute the file with privilege on the host. However

Re: [PATCH 1/2] dt-bindings: arm-ccn: Add bindings info for CCN-502 compatible string

Hi Mark/Pawel, I think this patch series has been missed. On 17-02-14 09:48 AM, Mark Rutland wrote: On Fri, Feb 10, 2017 at 12:42:47PM -0800, Velibor Markovski wrote: Add CCN-502 to the list of supported devices by ARM CCN PMU driver. Signed-off-by: Velibor Markovski

Re: [PATCH 1/2] dt-bindings: arm-ccn: Add bindings info for CCN-502 compatible string

Hi Mark/Pawel, I think this patch series has been missed. On 17-02-14 09:48 AM, Mark Rutland wrote: On Fri, Feb 10, 2017 at 12:42:47PM -0800, Velibor Markovski wrote: Add CCN-502 to the list of supported devices by ARM CCN PMU driver. Signed-off-by: Velibor Markovski Acked-by: Mark

Re: [PATCH] x86/intel_idle: add GLK support

Acked-by: Len Brown On Sun, Apr 23, 2017 at 2:06 AM, David E. Box wrote: > From: "Box, David E" > > Gemini Lake uses the same C-states as Broxton and also uses the > IRTL MSR's to determine maximum C-state latency. > >

Re: [PATCH] x86/intel_idle: add GLK support

Acked-by: Len Brown On Sun, Apr 23, 2017 at 2:06 AM, David E. Box wrote: > From: "Box, David E" > > Gemini Lake uses the same C-states as Broxton and also uses the > IRTL MSR's to determine maximum C-state latency. > > Signed-off-by: David E. Box > --- > drivers/idle/intel_idle.c | 2 ++ > 1

Re: iov_iter_pipe warning.

On Fri, Apr 28, 2017 at 09:58:47PM -0400, Dave Jones wrote: > On Fri, Apr 28, 2017 at 07:25:12PM +0100, Al Viro wrote: > > On Fri, Apr 28, 2017 at 06:20:25PM +0100, Al Viro wrote: > > > On Fri, Apr 28, 2017 at 12:50:24PM -0400, Dave Jones wrote: > > > > currently running

Re: iov_iter_pipe warning.

On Fri, Apr 28, 2017 at 09:58:47PM -0400, Dave Jones wrote: > On Fri, Apr 28, 2017 at 07:25:12PM +0100, Al Viro wrote: > > On Fri, Apr 28, 2017 at 06:20:25PM +0100, Al Viro wrote: > > > On Fri, Apr 28, 2017 at 12:50:24PM -0400, Dave Jones wrote: > > > > currently running

Re: [PATCH v2] iov_iter: don't revert iov buffer if csum error

On Sat, Apr 29, 2017 at 10:38:48AM +0800, Ding Tianhong wrote: > The patch 327868212381 (make skb_copy_datagram_msg() et.al. preserve > ->msg_iter on error) will revert the iov buffer if copy to iter > failed, but it didn't copy any datagram if the skb_checksum_complete > error, so no need to

Re: [PATCH v2] iov_iter: don't revert iov buffer if csum error

On Sat, Apr 29, 2017 at 10:38:48AM +0800, Ding Tianhong wrote: > The patch 327868212381 (make skb_copy_datagram_msg() et.al. preserve > ->msg_iter on error) will revert the iov buffer if copy to iter > failed, but it didn't copy any datagram if the skb_checksum_complete > error, so no need to

[PATCH v2] iov_iter: don't revert iov buffer if csum error

The patch 327868212381 (make skb_copy_datagram_msg() et.al. preserve ->msg_iter on error) will revert the iov buffer if copy to iter failed, but it didn't copy any datagram if the skb_checksum_complete error, so no need to revert any data at this place. v2: Sabrina notice that return -EFAULT when

[PATCH v2] iov_iter: don't revert iov buffer if csum error

The patch 327868212381 (make skb_copy_datagram_msg() et.al. preserve ->msg_iter on error) will revert the iov buffer if copy to iter failed, but it didn't copy any datagram if the skb_checksum_complete error, so no need to revert any data at this place. v2: Sabrina notice that return -EFAULT when

[PATCH] kthread: Fix race condition between kthread_parkme() and kthread_unpark()

In general, if kthread_unpark() and kthread_parkme() execute together, the kthread is supposed to be in an unparked state. This is because kthread_unpark() either wakes up the thread if it already got parked, or it cancels a prior kthread_park() call and hence renders the kthread_parkme() moot.

[PATCH] kthread: Fix race condition between kthread_parkme() and kthread_unpark()

In general, if kthread_unpark() and kthread_parkme() execute together, the kthread is supposed to be in an unparked state. This is because kthread_unpark() either wakes up the thread if it already got parked, or it cancels a prior kthread_park() call and hence renders the kthread_parkme() moot.

Re: [PATCH] iov_iter: don't revert if csum error

On 2017/4/28 21:16, Sabrina Dubroca wrote: > 2017-04-28, 20:48:45 +0800, Ding Tianhong wrote: >> The patch 3278682 (make skb_copy_datagram_msg() et.al. preserve >> ->msg_iter on error) will revert the iov buffer if copy to iter >> failed, but it looks no need to revert for csum error, so fix it.

Re: [PATCH] proc: Fix unbalanced hard link numbers

Takashi Iwai writes: > proc_create_mount_point() forgot to increase the parent's nlink, and > it resulted in unbalanced hard link numbers, e.g. /proc/fs shows one > less than expected. Applied. Thanks. > > Fixes: eb6d38d5427b ("proc: Allow creating permanently empty

Re: [PATCH] iov_iter: don't revert if csum error

On 2017/4/28 21:16, Sabrina Dubroca wrote: > 2017-04-28, 20:48:45 +0800, Ding Tianhong wrote: >> The patch 3278682 (make skb_copy_datagram_msg() et.al. preserve >> ->msg_iter on error) will revert the iov buffer if copy to iter >> failed, but it looks no need to revert for csum error, so fix it.

Re: [PATCH] proc: Fix unbalanced hard link numbers

Takashi Iwai writes: > proc_create_mount_point() forgot to increase the parent's nlink, and > it resulted in unbalanced hard link numbers, e.g. /proc/fs shows one > less than expected. Applied. Thanks. > > Fixes: eb6d38d5427b ("proc: Allow creating permanently empty directories...") > Cc:

Re: iov_iter_pipe warning.

On Fri, Apr 28, 2017 at 07:25:12PM +0100, Al Viro wrote: > On Fri, Apr 28, 2017 at 06:20:25PM +0100, Al Viro wrote: > > On Fri, Apr 28, 2017 at 12:50:24PM -0400, Dave Jones wrote: > > > currently running v4.11-rc8-75-gf83246089ca0 > > > > > > sunrpc bit is for the other unrelated problem I'm

Re: iov_iter_pipe warning.

On Fri, Apr 28, 2017 at 07:25:12PM +0100, Al Viro wrote: > On Fri, Apr 28, 2017 at 06:20:25PM +0100, Al Viro wrote: > > On Fri, Apr 28, 2017 at 12:50:24PM -0400, Dave Jones wrote: > > > currently running v4.11-rc8-75-gf83246089ca0 > > > > > > sunrpc bit is for the other unrelated problem I'm

Re: [PATCH] staging: comedi: use memdup_user

On Sat, 2017-04-29 at 09:45 +0800, Geliang Tang wrote: > Use memdup_user() helper instead of open-coding to simplify the code. While I doubt this is a problem, this loses the multiplication overflow check for sizeof(*insns) * insnlist.n_isns > diff --git a/drivers/staging/comedi/comedi_fops.c >

Re: [PATCH] staging: comedi: use memdup_user

On Sat, 2017-04-29 at 09:45 +0800, Geliang Tang wrote: > Use memdup_user() helper instead of open-coding to simplify the code. While I doubt this is a problem, this loses the multiplication overflow check for sizeof(*insns) * insnlist.n_isns > diff --git a/drivers/staging/comedi/comedi_fops.c >

[PATCH] powerpc/pseries: use memdup_user_nul

Use memdup_user_nul() helper instead of open-coding to simplify the code. Signed-off-by: Geliang Tang --- arch/powerpc/platforms/pseries/reconfig.c | 13 +++-- 1 file changed, 3 insertions(+), 10 deletions(-) diff --git a/arch/powerpc/platforms/pseries/reconfig.c

[PATCH] skd_main: use memdup_user

Use memdup_user() helper instead of open-coding to simplify the code. Signed-off-by: Geliang Tang --- drivers/block/skd_main.c | 16 +--- 1 file changed, 5 insertions(+), 11 deletions(-) diff --git a/drivers/block/skd_main.c b/drivers/block/skd_main.c index

[PATCH] powerpc/pseries: use memdup_user_nul

Use memdup_user_nul() helper instead of open-coding to simplify the code. Signed-off-by: Geliang Tang --- arch/powerpc/platforms/pseries/reconfig.c | 13 +++-- 1 file changed, 3 insertions(+), 10 deletions(-) diff --git a/arch/powerpc/platforms/pseries/reconfig.c

[PATCH] skd_main: use memdup_user

Use memdup_user() helper instead of open-coding to simplify the code. Signed-off-by: Geliang Tang --- drivers/block/skd_main.c | 16 +--- 1 file changed, 5 insertions(+), 11 deletions(-) diff --git a/drivers/block/skd_main.c b/drivers/block/skd_main.c index 27833e4..6b3cdd2 100644

[PATCH] staging: comedi: use memdup_user

Use memdup_user() helper instead of open-coding to simplify the code. Signed-off-by: Geliang Tang --- drivers/staging/comedi/comedi_fops.c | 22 +++--- 1 file changed, 7 insertions(+), 15 deletions(-) diff --git a/drivers/staging/comedi/comedi_fops.c

[PATCH] pstore: use memdup_user

Use memdup_user() helper instead of open-coding to simplify the code. Signed-off-by: Geliang Tang --- fs/pstore/platform.c | 11 --- 1 file changed, 4 insertions(+), 7 deletions(-) diff --git a/fs/pstore/platform.c b/fs/pstore/platform.c index 43b3ca5..903e0fe

[PATCH] powerpc/powernv: use memdup_user

Use memdup_user() helper instead of open-coding to simplify the code. Signed-off-by: Geliang Tang --- arch/powerpc/platforms/powernv/opal-prd.c | 13 +++-- 1 file changed, 3 insertions(+), 10 deletions(-) diff --git a/arch/powerpc/platforms/powernv/opal-prd.c

[PATCH] staging: comedi: use memdup_user

Use memdup_user() helper instead of open-coding to simplify the code. Signed-off-by: Geliang Tang --- drivers/staging/comedi/comedi_fops.c | 22 +++--- 1 file changed, 7 insertions(+), 15 deletions(-) diff --git a/drivers/staging/comedi/comedi_fops.c

[PATCH] pstore: use memdup_user

Use memdup_user() helper instead of open-coding to simplify the code. Signed-off-by: Geliang Tang --- fs/pstore/platform.c | 11 --- 1 file changed, 4 insertions(+), 7 deletions(-) diff --git a/fs/pstore/platform.c b/fs/pstore/platform.c index 43b3ca5..903e0fe 100644 ---

[PATCH] powerpc/powernv: use memdup_user

Use memdup_user() helper instead of open-coding to simplify the code. Signed-off-by: Geliang Tang --- arch/powerpc/platforms/powernv/opal-prd.c | 13 +++-- 1 file changed, 3 insertions(+), 10 deletions(-) diff --git a/arch/powerpc/platforms/powernv/opal-prd.c

[PATCH] floppy: use memdup_user

Use memdup_user() helper instead of open-coding to simplify the code. Signed-off-by: Geliang Tang --- drivers/block/floppy.c | 9 +++-- 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/drivers/block/floppy.c b/drivers/block/floppy.c index 60d4c76..167426c

[PATCH] floppy: use memdup_user

Use memdup_user() helper instead of open-coding to simplify the code. Signed-off-by: Geliang Tang --- drivers/block/floppy.c | 9 +++-- 1 file changed, 3 insertions(+), 6 deletions(-) diff --git a/drivers/block/floppy.c b/drivers/block/floppy.c index 60d4c76..167426c 100644 ---

[PATCH] powerpc/nvram: use memdup_user

Use memdup_user() helper instead of open-coding to simplify the code. Signed-off-by: Geliang Tang --- arch/powerpc/kernel/nvram_64.c | 14 +- 1 file changed, 5 insertions(+), 9 deletions(-) diff --git a/arch/powerpc/kernel/nvram_64.c

[PATCH] powerpc/nvram: use memdup_user

Use memdup_user() helper instead of open-coding to simplify the code. Signed-off-by: Geliang Tang --- arch/powerpc/kernel/nvram_64.c | 14 +- 1 file changed, 5 insertions(+), 9 deletions(-) diff --git a/arch/powerpc/kernel/nvram_64.c b/arch/powerpc/kernel/nvram_64.c index

[PATCH] cciss: use memdup_user

Use memdup_user() helper instead of open-coding to simplify the code. Signed-off-by: Geliang Tang --- drivers/block/cciss.c | 12 +++- 1 file changed, 3 insertions(+), 9 deletions(-) diff --git a/drivers/block/cciss.c b/drivers/block/cciss.c index

[PATCH] cciss: use memdup_user

Use memdup_user() helper instead of open-coding to simplify the code. Signed-off-by: Geliang Tang --- drivers/block/cciss.c | 12 +++- 1 file changed, 3 insertions(+), 9 deletions(-) diff --git a/drivers/block/cciss.c b/drivers/block/cciss.c index cd37550..40ee715 100644 ---

[PATCH 2/2] efi/efi_test: drop useless kfree

Drop useless kfree when memdup_user() failed, since we have already called kfree in memdup_user(). Signed-off-by: Geliang Tang --- drivers/firmware/efi/test/efi_test.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git

[PATCH 2/2] efi/efi_test: drop useless kfree

Drop useless kfree when memdup_user() failed, since we have already called kfree in memdup_user(). Signed-off-by: Geliang Tang --- drivers/firmware/efi/test/efi_test.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/drivers/firmware/efi/test/efi_test.c

[PATCH 1/2] efi/efi_test: use memdup_user

Use memdup_user() helper instead of open-coding to simplify the code. Signed-off-by: Geliang Tang --- drivers/firmware/efi/test/efi_test.c | 11 +++ 1 file changed, 3 insertions(+), 8 deletions(-) diff --git a/drivers/firmware/efi/test/efi_test.c

[PATCH 1/2] efi/efi_test: use memdup_user

Use memdup_user() helper instead of open-coding to simplify the code. Signed-off-by: Geliang Tang --- drivers/firmware/efi/test/efi_test.c | 11 +++ 1 file changed, 3 insertions(+), 8 deletions(-) diff --git a/drivers/firmware/efi/test/efi_test.c b/drivers/firmware/efi/test/efi_test.c

[PATCH v2] tty/serial: atmel: use offset_in_page() macro

Use offset_in_page() macro instead of open-coding. Signed-off-by: Geliang Tang --- Changes in v2: - include mm.h --- drivers/tty/serial/atmel_serial.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/drivers/tty/serial/atmel_serial.c

[PATCH v2] tty/serial: atmel: use offset_in_page() macro

Use offset_in_page() macro instead of open-coding. Signed-off-by: Geliang Tang --- Changes in v2: - include mm.h --- drivers/tty/serial/atmel_serial.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/drivers/tty/serial/atmel_serial.c b/drivers/tty/serial/atmel_serial.c

[PATCH v2] IB/i40iw: use setup_timer

Use setup_timer() instead of init_timer() to simplify the code. Signed-off-by: Geliang Tang --- Changes in v2: - use setup_timer() in i40iw_terminate_start_timer(). --- drivers/infiniband/hw/i40iw/i40iw_cm.c| 5 ++--- drivers/infiniband/hw/i40iw/i40iw_utils.c | 10

[PATCH v2] IB/i40iw: use setup_timer

Use setup_timer() instead of init_timer() to simplify the code. Signed-off-by: Geliang Tang --- Changes in v2: - use setup_timer() in i40iw_terminate_start_timer(). --- drivers/infiniband/hw/i40iw/i40iw_cm.c| 5 ++--- drivers/infiniband/hw/i40iw/i40iw_utils.c | 10 -- 2 files

Re: [PATCH v4] Input: psxpad-spi - Add PSX (Play Station 1/2) pad SPI driver

Mr.Gutman Thanks to the opinion. I thought that PC applications can flexibly set button and axis settings. However, there are many applications that can not be set. To briefly explain the operation of the PSX pad, 1. When analog button is off, PSX gamepad send "digital" responses. 2. When

Re: [PATCH v4] Input: psxpad-spi - Add PSX (Play Station 1/2) pad SPI driver

Mr.Gutman Thanks to the opinion. I thought that PC applications can flexibly set button and axis settings. However, there are many applications that can not be set. To briefly explain the operation of the PSX pad, 1. When analog button is off, PSX gamepad send "digital" responses. 2. When

Re: [PATCH v3] staging: speakup: fix wrong code indent

Greg Kroah-Hartman writes: > This patch doesn't apply to my tree at all, what tree/branch did you > make it against? >From the 'T:' line in MAINTAINER at STAGING SUBSYSTEM, I thought that I should base changes on:

Re: [PATCH v3] staging: speakup: fix wrong code indent

Greg Kroah-Hartman writes: > This patch doesn't apply to my tree at all, what tree/branch did you > make it against? >From the 'T:' line in MAINTAINER at STAGING SUBSYSTEM, I thought that I should base changes on: git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git Since there

Re: [PATCH 2/2] libnvdimm: clear region badblock in nvdimm_clear_poison()

On Fri, Apr 28, 2017 at 5:12 PM, Dan Williams wrote: > On Fri, Apr 28, 2017 at 5:10 PM, Dan Williams > wrote: >> On Thu, Apr 27, 2017 at 3:57 PM, Toshi Kani wrote: >>> Badblocks are tracked at both region and device

Re: [PATCH 2/2] libnvdimm: clear region badblock in nvdimm_clear_poison()

On Fri, Apr 28, 2017 at 5:12 PM, Dan Williams wrote: > On Fri, Apr 28, 2017 at 5:10 PM, Dan Williams > wrote: >> On Thu, Apr 27, 2017 at 3:57 PM, Toshi Kani wrote: >>> Badblocks are tracked at both region and device levels. >>> pmem_clear_poison() and nsio_rw_bytes() call nvdimm_clear_poison()

[PATCH] staging: fbtft: fbtft-core.c: EXPORT_SYMBOL should immediately follow its function

This patch fixes the following checkpatch.pl warning - EXPORT_SYMBOL(foo); should immediately follow its function/variable Signed-off-by: Shiva Kerdel --- drivers/staging/fbtft/fbtft-core.c | 25 +++-- 1 file changed, 15 insertions(+), 10 deletions(-) diff

[PATCH] staging: fbtft: fbtft-core.c: EXPORT_SYMBOL should immediately follow its function

This patch fixes the following checkpatch.pl warning - EXPORT_SYMBOL(foo); should immediately follow its function/variable Signed-off-by: Shiva Kerdel --- drivers/staging/fbtft/fbtft-core.c | 25 +++-- 1 file changed, 15 insertions(+), 10 deletions(-) diff --git

Re: [PATCH 2/2] libnvdimm: clear region badblock in nvdimm_clear_poison()

On Fri, Apr 28, 2017 at 5:10 PM, Dan Williams wrote: > On Thu, Apr 27, 2017 at 3:57 PM, Toshi Kani wrote: >> Badblocks are tracked at both region and device levels. >> pmem_clear_poison() and nsio_rw_bytes() call nvdimm_clear_poison() >> and then

Re: [PATCH 2/2] libnvdimm: clear region badblock in nvdimm_clear_poison()

On Fri, Apr 28, 2017 at 5:10 PM, Dan Williams wrote: > On Thu, Apr 27, 2017 at 3:57 PM, Toshi Kani wrote: >> Badblocks are tracked at both region and device levels. >> pmem_clear_poison() and nsio_rw_bytes() call nvdimm_clear_poison() >> and then badblocks_clear() to clear badblocks at the

Re: [PATCH RFC tip/core/rcu] Make SRCU be once again optional

On Fri, Apr 28, 2017 at 05:51:15PM -0400, Nicolas Pitre wrote: > On Fri, 28 Apr 2017, Paul E. McKenney wrote: > > > Hello, Nicolas! > > > > Saw the TTY write up LWN and figured I should send this your way. > > It should be worth about 2K compared to current -next, which gave > > up the 2K

Re: [PATCH RFC tip/core/rcu] Make SRCU be once again optional

On Fri, Apr 28, 2017 at 05:51:15PM -0400, Nicolas Pitre wrote: > On Fri, 28 Apr 2017, Paul E. McKenney wrote: > > > Hello, Nicolas! > > > > Saw the TTY write up LWN and figured I should send this your way. > > It should be worth about 2K compared to current -next, which gave > > up the 2K

Re: [PATCH 2/2] libnvdimm: clear region badblock in nvdimm_clear_poison()

On Thu, Apr 27, 2017 at 3:57 PM, Toshi Kani wrote: > Badblocks are tracked at both region and device levels. > pmem_clear_poison() and nsio_rw_bytes() call nvdimm_clear_poison() > and then badblocks_clear() to clear badblocks at the device level. > However, it does not update

Re: [PATCH 2/2] libnvdimm: clear region badblock in nvdimm_clear_poison()

On Thu, Apr 27, 2017 at 3:57 PM, Toshi Kani wrote: > Badblocks are tracked at both region and device levels. > pmem_clear_poison() and nsio_rw_bytes() call nvdimm_clear_poison() > and then badblocks_clear() to clear badblocks at the device level. > However, it does not update badblocks at the

[PATCH] regulator: Allow for asymmetric settling times

Some regulators have different settling times for voltage increases and decreases. To avoid a time penalty on the faster transition extend the settling time property to allow for different settings for upward and downward transitions. Signed-off-by: Matthias Kaehlcke ---

[PATCH] regulator: Allow for asymmetric settling times

Some regulators have different settling times for voltage increases and decreases. To avoid a time penalty on the faster transition extend the settling time property to allow for different settings for upward and downward transitions. Signed-off-by: Matthias Kaehlcke --- Dependencies (from

[PATCH v2] acpi, nfit: kill ACPI_NFIT_DEBUG

Inevitably when one actually needs to debug a DSM issue it's on a distribution kernel that has CONFIG_ACPI_NFIT_DEBUG=n. The config symbol was only there to avoid the compile error due to the missing fallback for print_hex_dump_debug in the CONFIG_DYNAMIC_DEBUG=n case. That was fixed with commit

[PATCH v2] acpi, nfit: kill ACPI_NFIT_DEBUG

Inevitably when one actually needs to debug a DSM issue it's on a distribution kernel that has CONFIG_ACPI_NFIT_DEBUG=n. The config symbol was only there to avoid the compile error due to the missing fallback for print_hex_dump_debug in the CONFIG_DYNAMIC_DEBUG=n case. That was fixed with commit

[GIT PULL] clk fixes for v4.11-rc8

The following changes since commit e7590308d17e578e47f298cc3fec359108341cb6: Merge tag 'sunxi-clk-fixes-for-4.11-2-bis' of https://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux into clk-fixes (2017-04-17 11:04:12 -0700) are available in the git repository at:

[GIT PULL] clk fixes for v4.11-rc8

The following changes since commit e7590308d17e578e47f298cc3fec359108341cb6: Merge tag 'sunxi-clk-fixes-for-4.11-2-bis' of https://git.kernel.org/pub/scm/linux/kernel/git/sunxi/linux into clk-fixes (2017-04-17 11:04:12 -0700) are available in the git repository at:

Re: [PATCH 1/2] wcn36xx: Pass used skb to ieee80211_tx_status()

On Thu 27 Apr 01:22 PDT 2017, Johannes Berg wrote: > > > @@ -371,7 +371,7 @@ static void reap_tx_dxes(struct wcn36xx *wcn, > > struct wcn36xx_dxe_ch *ch) > >   info = IEEE80211_SKB_CB(ctl->skb); > >   if (!(info->flags & > > IEEE80211_TX_CTL_REQ_TX_STATUS)) {

Re: [PATCH 1/2] wcn36xx: Pass used skb to ieee80211_tx_status()

On Thu 27 Apr 01:22 PDT 2017, Johannes Berg wrote: > > > @@ -371,7 +371,7 @@ static void reap_tx_dxes(struct wcn36xx *wcn, > > struct wcn36xx_dxe_ch *ch) > >   info = IEEE80211_SKB_CB(ctl->skb); > >   if (!(info->flags & > > IEEE80211_TX_CTL_REQ_TX_STATUS)) {

Re: [PATCH 00/14] sched/topology fixes

On 04/28/2017 10:53 AM, Peter Zijlstra wrote: > On Fri, Apr 28, 2017 at 03:19:58PM +0200, Peter Zijlstra wrote: >> Hi, >> >> These patches are based upon the hard work of Lauro. He put in the time and >> effort to understand and debug the code. >> >> So while I didn't take many of his actual

Re: [PATCH 00/14] sched/topology fixes

On 04/28/2017 10:53 AM, Peter Zijlstra wrote: > On Fri, Apr 28, 2017 at 03:19:58PM +0200, Peter Zijlstra wrote: >> Hi, >> >> These patches are based upon the hard work of Lauro. He put in the time and >> effort to understand and debug the code. >> >> So while I didn't take many of his actual

Re: [PATCH 0/3] dynamic_hex_dump cleanup

On Fri, Apr 28, 2017 at 4:04 PM, Joe Perches wrote: > On Fri, 2017-04-28 at 15:59 -0700, Dan Williams wrote: >> ...but again, hex_dump_dbg() implies to me dev_dbg() behavior, i.e. >> that the hexdump happens in the KERN_DEBUG case > > I think you are confusing KERN_DEBUG, a

Re: [PATCH 0/3] dynamic_hex_dump cleanup

On Fri, Apr 28, 2017 at 4:04 PM, Joe Perches wrote: > On Fri, 2017-04-28 at 15:59 -0700, Dan Williams wrote: >> ...but again, hex_dump_dbg() implies to me dev_dbg() behavior, i.e. >> that the hexdump happens in the KERN_DEBUG case > > I think you are confusing KERN_DEBUG, a logging level, with a

Re: [PATCH 0/3] dynamic_hex_dump cleanup

On Fri, 2017-04-28 at 15:59 -0700, Dan Williams wrote: > ...but again, hex_dump_dbg() implies to me dev_dbg() behavior, i.e. > that the hexdump happens in the KERN_DEBUG case I think you are confusing KERN_DEBUG, a logging level, with a preprocessor #define of DEBUG. > which I don't want. I >

Re: [PATCH 0/3] dynamic_hex_dump cleanup

On Fri, 2017-04-28 at 15:59 -0700, Dan Williams wrote: > ...but again, hex_dump_dbg() implies to me dev_dbg() behavior, i.e. > that the hexdump happens in the KERN_DEBUG case I think you are confusing KERN_DEBUG, a logging level, with a preprocessor #define of DEBUG. > which I don't want. I >

Re: [PATCH v3 0/3] Handle memmap and mem kernel options in boot stage kaslr

On 04/27/17 at 03:57pm, YASUAKI ISHIMATSU wrote: > Hi Baoquan, > > > On 04/26/2017 06:16 AM, Baoquan He wrote: > > People reported kernel panic occurs during system boots up with mem boot > > option. > > After checking code, several problems are found about memmap= and mem= in > > boot stage >

Re: [PATCH 2/2] iommu/s390: Add support for iommu_device handling

Hi Joerg, [auto build test ERROR on s390/features] [also build test ERROR on v4.11-rc8 next-20170428] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Joerg-Roedel/iommu-s390-Fix-iommu-groups

Re: [PATCH v3 0/3] Handle memmap and mem kernel options in boot stage kaslr

On 04/27/17 at 03:57pm, YASUAKI ISHIMATSU wrote: > Hi Baoquan, > > > On 04/26/2017 06:16 AM, Baoquan He wrote: > > People reported kernel panic occurs during system boots up with mem boot > > option. > > After checking code, several problems are found about memmap= and mem= in > > boot stage >

Re: [PATCH 2/2] iommu/s390: Add support for iommu_device handling

Hi Joerg, [auto build test ERROR on s390/features] [also build test ERROR on v4.11-rc8 next-20170428] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Joerg-Roedel/iommu-s390-Fix-iommu-groups

Re: [PATCH 0/3] dynamic_hex_dump cleanup

On Fri, Apr 28, 2017 at 3:31 PM, Joe Perches wrote: > On Fri, 2017-04-28 at 15:19 -0700, Dan Williams wrote: >> On Fri, Apr 28, 2017 at 3:14 PM, Dan Williams >> wrote: >> > On Fri, Apr 28, 2017 at 3:07 PM, Joe Perches wrote: >> > >

Re: [PATCH 0/3] dynamic_hex_dump cleanup

On Fri, Apr 28, 2017 at 3:31 PM, Joe Perches wrote: > On Fri, 2017-04-28 at 15:19 -0700, Dan Williams wrote: >> On Fri, Apr 28, 2017 at 3:14 PM, Dan Williams >> wrote: >> > On Fri, Apr 28, 2017 at 3:07 PM, Joe Perches wrote: >> > > On Fri, 2017-04-28 at 14:52 -0700, Dan Williams wrote: >> > >

Re: [PATCH v6 1/5] skbuff: return -EMSGSIZE in skb_to_sgvec to prevent overflow

Hi Sabrina, On Fri, Apr 28, 2017 at 6:18 PM, Sabrina Dubroca wrote: > One small thing here: since you're touching this comment, could you > move it next to skb_to_sgvec, since that's the function it's supposed > to document? Done. I'll wait until next week to resubmit, to

Re: [PATCH v6 1/5] skbuff: return -EMSGSIZE in skb_to_sgvec to prevent overflow

Hi Sabrina, On Fri, Apr 28, 2017 at 6:18 PM, Sabrina Dubroca wrote: > One small thing here: since you're touching this comment, could you > move it next to skb_to_sgvec, since that's the function it's supposed > to document? Done. I'll wait until next week to resubmit, to give some more time

[PATCH v4 1/3] drm/vc4: Turn the V3D clock on at runtime.

For the Raspberry Pi's bindings, the power domain also implicitly turns on the clock and deasserts reset, but for the new Cygnus port we start representing the clock in the devicetree. v2: Document the clock-names property, check for -ENOENT for no clock in DT. v3: Drop NULL checks around clk

[PATCH v4 1/3] drm/vc4: Turn the V3D clock on at runtime.

For the Raspberry Pi's bindings, the power domain also implicitly turns on the clock and deasserts reset, but for the new Cygnus port we start representing the clock in the devicetree. v2: Document the clock-names property, check for -ENOENT for no clock in DT. v3: Drop NULL checks around clk

[PATCH v4 2/3] drm/vc4: Don't try to initialize FBDEV if we're only bound to V3D.

The FBDEV initialization would throw an error in dmesg, when we just want to silently not initialize fbdev on a V3D-only VC4 instance. Signed-off-by: Eric Anholt --- drivers/gpu/drm/vc4/vc4_kms.c | 10 ++ 1 file changed, 6 insertions(+), 4 deletions(-) diff --git

[PATCH v4 2/3] drm/vc4: Don't try to initialize FBDEV if we're only bound to V3D.

The FBDEV initialization would throw an error in dmesg, when we just want to silently not initialize fbdev on a V3D-only VC4 instance. Signed-off-by: Eric Anholt --- drivers/gpu/drm/vc4/vc4_kms.c | 10 ++ 1 file changed, 6 insertions(+), 4 deletions(-) diff --git

  1   2   3   4   5   6   7   8   9   10   >