Re: [PATCH 0/2] Fix incorrect warning from dma-debug

On 05/09/2016 06:00 AM, Robin Murphy wrote: > On 09/05/16 10:37, Robin Murphy wrote: >> Hi Niklas, >> >> On 08/05/16 11:59, Niklas Söderlund wrote: >>> Hi, >>> >>> While using CONFIG_DMA_API_DEBUG i came across this warning which I >>> think is a false positive. As shown

Re: [PATCH 0/2] Fix incorrect warning from dma-debug

On 05/09/2016 06:00 AM, Robin Murphy wrote: > On 09/05/16 10:37, Robin Murphy wrote: >> Hi Niklas, >> >> On 08/05/16 11:59, Niklas Söderlund wrote: >>> Hi, >>> >>> While using CONFIG_DMA_API_DEBUG i came across this warning which I >>> think is a false positive. As shown

[RFC] NMI: Generic per-code NMI handler (panic/kdump)

Hello, I'm new to the LKML, so should I make mistakes, please tell me along with the correct way to do (or doc I've read but forgotten). I've written a small module to manage NMI events based on their code, so a sysadmin can drop them (avoid console messages) or panic the kernel (kdump).

[RFC] NMI: Generic per-code NMI handler (panic/kdump)

Hello, I'm new to the LKML, so should I make mistakes, please tell me along with the correct way to do (or doc I've read but forgotten). I've written a small module to manage NMI events based on their code, so a sysadmin can drop them (avoid console messages) or panic the kernel (kdump).

Re: [PATCH 0/3] staging: ccree: resolve checkpatch issues.

* Matthew Giassa [2017-05-06 15:46:53 -0700]: Included is a set of small fixes to resolve all outstanding checkpatch warnings issues for drivers/staging/ccree/cc_hal.h. Two are cosmetic (training whitespace and 80+ character comment), and the other is functional (macro

Re: [PATCH 0/3] staging: ccree: resolve checkpatch issues.

* Matthew Giassa [2017-05-06 15:46:53 -0700]: Included is a set of small fixes to resolve all outstanding checkpatch warnings issues for drivers/staging/ccree/cc_hal.h. Two are cosmetic (training whitespace and 80+ character comment), and the other is functional (macro argument previously not

[PATCH 2/3] staging: ccree: resolve columns over 80 chars in cc_hal.h

Modified comment to resolve 80+ characters warning from checkpatch. ie: WARNING: line over 80 characters Warnings no longer present after change. Signed-off-by: Matthew Giassa --- drivers/staging/ccree/cc_hal.h | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff

[PATCH 3/3] staging: ccree: resolve possible macro issue in cc_hal.h

Wrapping "offset" in macro definition to resolve checkpatch issue, ie: CHECK: Macro argument 'offset' may be better as '(offset)' to avoid precedence issues Signed-off-by: Matthew Giassa --- drivers/staging/ccree/cc_hal.h | 5 +++-- 1 file changed, 3 insertions(+), 2

[PATCH 2/3] staging: ccree: resolve columns over 80 chars in cc_hal.h

Modified comment to resolve 80+ characters warning from checkpatch. ie: WARNING: line over 80 characters Warnings no longer present after change. Signed-off-by: Matthew Giassa --- drivers/staging/ccree/cc_hal.h | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git

[PATCH 3/3] staging: ccree: resolve possible macro issue in cc_hal.h

Wrapping "offset" in macro definition to resolve checkpatch issue, ie: CHECK: Macro argument 'offset' may be better as '(offset)' to avoid precedence issues Signed-off-by: Matthew Giassa --- drivers/staging/ccree/cc_hal.h | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git

[PATCH 0/3] staging: ccree: resolve checkpatch issues.

Included is a set of small fixes to resolve all outstanding checkpatch warnings issues for drivers/staging/ccree/cc_hal.h. Two are cosmetic (training whitespace and 80+ character comment), and the other is functional (macro argument previously not wrapped in parentheses).

[PATCH 1/3] staging: ccree: resolve training whitespace in cc_hal.h

Removing trailing newlines reported by checkpatch.pl. ie: ERROR: trailing whitespace (lines 3, 7, 12). Warnings no longer present after change. Signed-off-by: Matthew Giassa --- drivers/staging/ccree/cc_hal.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff

[PATCH 0/3] staging: ccree: resolve checkpatch issues.

Included is a set of small fixes to resolve all outstanding checkpatch warnings issues for drivers/staging/ccree/cc_hal.h. Two are cosmetic (training whitespace and 80+ character comment), and the other is functional (macro argument previously not wrapped in parentheses).

[PATCH 1/3] staging: ccree: resolve training whitespace in cc_hal.h

Removing trailing newlines reported by checkpatch.pl. ie: ERROR: trailing whitespace (lines 3, 7, 12). Warnings no longer present after change. Signed-off-by: Matthew Giassa --- drivers/staging/ccree/cc_hal.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git

Re: [PATCH] ACPI: SPCR: Use access width to determine mmio usage

On 05/04/2017 11:05 AM, Jon Mason wrote: > The current SPCR code does not check the access width of the mmio, and > uses a default of 8bit register accesses. This prevents devices that > only do 16 or 32bit register accesses from working. By simply checking > this field and setting the mmio

Re: [PATCH] ACPI: SPCR: Use access width to determine mmio usage

On 05/04/2017 11:05 AM, Jon Mason wrote: > The current SPCR code does not check the access width of the mmio, and > uses a default of 8bit register accesses. This prevents devices that > only do 16 or 32bit register accesses from working. By simply checking > this field and setting the mmio

[PATCH] docs: complete bumping minimal GNU Make version to 3.81

Commit 37d69ee3080811 ("docs: bump minimal GNU Make version to 3.81") changes one entry of GNU make version in the changes.rst, there's still one more entry saying that one need version 3.80. Fix that. Signed-off-by: Max Filippov --- Documentation/process/changes.rst | 2 +-

[PATCH] docs: complete bumping minimal GNU Make version to 3.81

Commit 37d69ee3080811 ("docs: bump minimal GNU Make version to 3.81") changes one entry of GNU make version in the changes.rst, there's still one more entry saying that one need version 3.80. Fix that. Signed-off-by: Max Filippov --- Documentation/process/changes.rst | 2 +- 1 file changed, 1

[PATCH] scsi: lpfc: ensure els_wq is being checked before destroying it

From: Colin Ian King I believe there is a typo on the wq destroy of els_wq, currently the driver is checking if els_cq is not null and I think this should be a check on els_wq instead. Detected by CoverityScan, CID#1411629 ("Copy-paste error") Signed-off-by: Colin Ian

[PATCH] scsi: lpfc: ensure els_wq is being checked before destroying it

From: Colin Ian King I believe there is a typo on the wq destroy of els_wq, currently the driver is checking if els_cq is not null and I think this should be a check on els_wq instead. Detected by CoverityScan, CID#1411629 ("Copy-paste error") Signed-off-by: Colin Ian King ---

Re: [PATCH V6 1/9] PM / OPP: Introduce "power-domain-opp" property

Rob Herring writes: > On Wed, Apr 26, 2017 at 04:27:05PM +0530, Viresh Kumar wrote: >> Power-domains need to express their active states in DT and the devices >> within the power-domain need to express their dependency on those active >> states. The power-domains can use the OPP

Re: [PATCH V6 1/9] PM / OPP: Introduce "power-domain-opp" property

Rob Herring writes: > On Wed, Apr 26, 2017 at 04:27:05PM +0530, Viresh Kumar wrote: >> Power-domains need to express their active states in DT and the devices >> within the power-domain need to express their dependency on those active >> states. The power-domains can use the OPP tables without

Re: [PATCH V6 1/9] PM / OPP: Introduce "power-domain-opp" property

Sudeep Holla writes: > On 28/04/17 21:48, Rob Herring wrote: >> On Wed, Apr 26, 2017 at 04:27:05PM +0530, Viresh Kumar wrote: >>> Power-domains need to express their active states in DT and the devices >>> within the power-domain need to express their dependency on those

Re: [PATCH V6 1/9] PM / OPP: Introduce "power-domain-opp" property

Sudeep Holla writes: > On 28/04/17 21:48, Rob Herring wrote: >> On Wed, Apr 26, 2017 at 04:27:05PM +0530, Viresh Kumar wrote: >>> Power-domains need to express their active states in DT and the devices >>> within the power-domain need to express their dependency on those active >>> states. The

[PATCH 4.9 0/9] 4.9.27-stable review

This is the start of the stable review cycle for the 4.9.27 release. There are 9 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Mon May 8 20:38:28 UTC 2017. Anything

[PATCH 4.9 0/9] 4.9.27-stable review

This is the start of the stable review cycle for the 4.9.27 release. There are 9 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Mon May 8 20:38:28 UTC 2017. Anything

[PATCH 4.9 2/9] Handle mismatched open calls

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Sachin Prabhu commit 38bd49064a1ecb67baad33598e3d824448ab11ec upstream. A signal can interrupt a SendReceive call which result in incoming responses to the call being

[PATCH 4.9 3/9] tpm_tis: use default timeout value if chip reports it as zero

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Maciej S. Szmigiero commit 1d70fe9d9c3a4c627f9757cbba5d628687b121c1 upstream. Since commit 1107d065fdf1 ("tpm_tis: Introduce intermediate layer for TPM access")

[PATCH 4.9 2/9] Handle mismatched open calls

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Sachin Prabhu commit 38bd49064a1ecb67baad33598e3d824448ab11ec upstream. A signal can interrupt a SendReceive call which result in incoming responses to the call being ignored. This is a

[PATCH 4.9 3/9] tpm_tis: use default timeout value if chip reports it as zero

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Maciej S. Szmigiero commit 1d70fe9d9c3a4c627f9757cbba5d628687b121c1 upstream. Since commit 1107d065fdf1 ("tpm_tis: Introduce intermediate layer for TPM access") Atmel 3203 TPM on ThinkPad X61S

[PATCH 4.10 1/5] timerfd: Protect the might cancel mechanism proper

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit 1e38da300e1e395a15048b0af1e5305bd91402f6 upstream. The handling of the might_cancel queueing is not properly protected, so parallel operations on

[PATCH 4.9 8/9] cpu/hotplug: Serialize callback invocations proper

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior commit dc434e056fe1dada20df7ba07f32739d3a701adf upstream. The setup/remove_state/instance() functions in the hotplug core code are serialized

[PATCH 4.10 1/5] timerfd: Protect the might cancel mechanism proper

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit 1e38da300e1e395a15048b0af1e5305bd91402f6 upstream. The handling of the might_cancel queueing is not properly protected, so parallel operations on the file descriptor

[PATCH 4.9 8/9] cpu/hotplug: Serialize callback invocations proper

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Sebastian Andrzej Siewior commit dc434e056fe1dada20df7ba07f32739d3a701adf upstream. The setup/remove_state/instance() functions in the hotplug core code are serialized against concurrent CPU

[PATCH 4.9 4/9] scsi: storvsc: Workaround for virtual DVD SCSI version

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Stephen Hemminger commit f1c635b439a5c01776fe3a25b1e2dc546ea82e6f upstream. Hyper-V host emulation of SCSI for virtual DVD device reports SCSI version 0 (UNKNOWN)

[PATCH 4.9 4/9] scsi: storvsc: Workaround for virtual DVD SCSI version

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Stephen Hemminger commit f1c635b439a5c01776fe3a25b1e2dc546ea82e6f upstream. Hyper-V host emulation of SCSI for virtual DVD device reports SCSI version 0 (UNKNOWN) but is still capable of

[PATCH 4.9 6/9] 8250_pci: Fix potential use-after-free in error path

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Gabriel Krisman Bertazi commit c130b666a9a711f985a0a44b58699ebe14bb7245 upstream. Commit f209fa03fc9d ("serial: 8250_pci: Detach low-level driver during PCI error

[PATCH 4.9 9/9] dm ioctl: prevent stack leak in dm ioctl call

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Adrian Salido commit 4617f564c06117c7d1b611be49521a4430042287 upstream. When calling a dm ioctl that doesn't process any data (IOCTL_FLAGS_NO_PARAMS), the contents of the

[PATCH 4.9 6/9] 8250_pci: Fix potential use-after-free in error path

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Gabriel Krisman Bertazi commit c130b666a9a711f985a0a44b58699ebe14bb7245 upstream. Commit f209fa03fc9d ("serial: 8250_pci: Detach low-level driver during PCI error recovery") introduces a

[PATCH 4.9 9/9] dm ioctl: prevent stack leak in dm ioctl call

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Adrian Salido commit 4617f564c06117c7d1b611be49521a4430042287 upstream. When calling a dm ioctl that doesn't process any data (IOCTL_FLAGS_NO_PARAMS), the contents of the data field in struct

[PATCH 4.9 7/9] ceph: try getting buffer capability for readahead/fadvise

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Yan, Zheng commit 2b1ac852eb67a6e95595e576371d23519105559f upstream. For readahead/fadvise cases, caller of ceph_readpages does not hold buffer capability. Pages can be added

[PATCH 4.9 7/9] ceph: try getting buffer capability for readahead/fadvise

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Yan, Zheng commit 2b1ac852eb67a6e95595e576371d23519105559f upstream. For readahead/fadvise cases, caller of ceph_readpages does not hold buffer capability. Pages can be added to page cache

[PATCH 4.9 5/9] hwmon: (it87) Avoid registering the same chip on both SIO addresses

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Guenter Roeck commit 8358378b22518d92424597503d3c1cd302a490b6 upstream. IT8705F is known to respond on both SIO addresses. Registering it twice may result in system

[PATCH 4.9 5/9] hwmon: (it87) Avoid registering the same chip on both SIO addresses

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Guenter Roeck commit 8358378b22518d92424597503d3c1cd302a490b6 upstream. IT8705F is known to respond on both SIO addresses. Registering it twice may result in system lockups. Reported-by:

[PATCH 4.9 1/9] timerfd: Protect the might cancel mechanism proper

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit 1e38da300e1e395a15048b0af1e5305bd91402f6 upstream. The handling of the might_cancel queueing is not properly protected, so parallel operations on the

[PATCH 4.9 1/9] timerfd: Protect the might cancel mechanism proper

4.9-stable review patch. If anyone has any objections, please let me know. -- From: Thomas Gleixner commit 1e38da300e1e395a15048b0af1e5305bd91402f6 upstream. The handling of the might_cancel queueing is not properly protected, so parallel operations on the file descriptor can

[PATCH 4.10 5/5] dm ioctl: prevent stack leak in dm ioctl call

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Adrian Salido commit 4617f564c06117c7d1b611be49521a4430042287 upstream. When calling a dm ioctl that doesn't process any data (IOCTL_FLAGS_NO_PARAMS), the contents of the

[PATCH 4.10 4/5] hwmon: (it87) Avoid registering the same chip on both SIO addresses

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Guenter Roeck commit 8358378b22518d92424597503d3c1cd302a490b6 upstream. IT8705F is known to respond on both SIO addresses. Registering it twice may result in system

[PATCH 4.10 5/5] dm ioctl: prevent stack leak in dm ioctl call

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Adrian Salido commit 4617f564c06117c7d1b611be49521a4430042287 upstream. When calling a dm ioctl that doesn't process any data (IOCTL_FLAGS_NO_PARAMS), the contents of the data field in struct

[PATCH 4.10 4/5] hwmon: (it87) Avoid registering the same chip on both SIO addresses

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Guenter Roeck commit 8358378b22518d92424597503d3c1cd302a490b6 upstream. IT8705F is known to respond on both SIO addresses. Registering it twice may result in system lockups. Reported-by:

[PATCH 4.10 2/5] Handle mismatched open calls

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Sachin Prabhu commit 38bd49064a1ecb67baad33598e3d824448ab11ec upstream. A signal can interrupt a SendReceive call which result in incoming responses to the call being

[PATCH 4.10 2/5] Handle mismatched open calls

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Sachin Prabhu commit 38bd49064a1ecb67baad33598e3d824448ab11ec upstream. A signal can interrupt a SendReceive call which result in incoming responses to the call being ignored. This is a

[PATCH 4.10 3/5] scsi: storvsc: Workaround for virtual DVD SCSI version

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Stephen Hemminger commit f1c635b439a5c01776fe3a25b1e2dc546ea82e6f upstream. Hyper-V host emulation of SCSI for virtual DVD device reports SCSI version 0 (UNKNOWN)

[PATCH 4.10 0/5] 4.10.15-stable review

This is the start of the stable review cycle for the 4.10.15 release. There are 5 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Mon May 8 20:38:36 UTC 2017. Anything

[PATCH 4.10 3/5] scsi: storvsc: Workaround for virtual DVD SCSI version

4.10-stable review patch. If anyone has any objections, please let me know. -- From: Stephen Hemminger commit f1c635b439a5c01776fe3a25b1e2dc546ea82e6f upstream. Hyper-V host emulation of SCSI for virtual DVD device reports SCSI version 0 (UNKNOWN) but is still capable of

[PATCH 4.10 0/5] 4.10.15-stable review

This is the start of the stable review cycle for the 4.10.15 release. There are 5 patches in this series, all will be posted as a response to this one. If anyone has any issues with these being applied, please let me know. Responses should be made by Mon May 8 20:38:36 UTC 2017. Anything

Re: [PATCH 3/3] staging: rtl8723bs: fix up for cfg80211_roamed() API change

Hi Stephen, [auto build test ERROR on staging/staging-testing] [cannot apply to v4.11 next-20170505] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH 3/3] staging: rtl8723bs: fix up for cfg80211_roamed() API change

Hi Stephen, [auto build test ERROR on staging/staging-testing] [cannot apply to v4.11 next-20170505] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH 2/3] staging: rtl8723bs: merge fix for "nl80211: allow multiple active scheduled scan requests"

Hi Stephen, [auto build test ERROR on staging/staging-testing] [cannot apply to v4.11 next-20170505] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH 2/3] staging: rtl8723bs: merge fix for "nl80211: allow multiple active scheduled scan requests"

Hi Stephen, [auto build test ERROR on staging/staging-testing] [cannot apply to v4.11 next-20170505] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH] staging: lustre: llite: Fix variable length array warning

On Fri, May 05, 2017 at 01:52:36AM -0700, Joe Perches wrote: > On Thu, 2017-05-04 at 23:41 -0700, Guru Das Srinagesh wrote: > > Fix sparse warning "warning: Variable length array is used." by using > > kmalloc_array to allocate the required amount of memory instead and > > kfree to deallocate

Re: [PATCH] staging: lustre: llite: Fix variable length array warning

On Fri, May 05, 2017 at 01:52:36AM -0700, Joe Perches wrote: > On Thu, 2017-05-04 at 23:41 -0700, Guru Das Srinagesh wrote: > > Fix sparse warning "warning: Variable length array is used." by using > > kmalloc_array to allocate the required amount of memory instead and > > kfree to deallocate

Re: [git pull] drm pull for v4.12

On Tue, May 2, 2017 at 8:44 PM, Dave Airlie wrote: > > i915: > vblank evasion improvements These may be "improvements", but they end up being very noisy. I geta fair amount of messages like [drm] Atomic update on pipe (A) took 161 us, max time under evasion is 100 us on

Re: [git pull] drm pull for v4.12

On Tue, May 2, 2017 at 8:44 PM, Dave Airlie wrote: > > i915: > vblank evasion improvements These may be "improvements", but they end up being very noisy. I geta fair amount of messages like [drm] Atomic update on pipe (A) took 161 us, max time under evasion is 100 us on my desktop

Re: [PATCH] kthread: fix use-after-free if kthread fork fails

On 05/05, Vegard Nossum wrote: > > On 05/05/17 18:44, Oleg Nesterov wrote: > > > >Can't we just move both > > > > p->set_child_tid = (clone_flags & CLONE_CHILD_SETTID) ? child_tidptr : > > NULL; > > /* > > * Clear TID on mm_release()? > > */ > > p->clear_child_tid =

Re: [PATCH] kthread: fix use-after-free if kthread fork fails

On 05/05, Vegard Nossum wrote: > > On 05/05/17 18:44, Oleg Nesterov wrote: > > > >Can't we just move both > > > > p->set_child_tid = (clone_flags & CLONE_CHILD_SETTID) ? child_tidptr : > > NULL; > > /* > > * Clear TID on mm_release()? > > */ > > p->clear_child_tid =

[PATCH 3/3] kernel-sched: Combine two seq_printf() calls into one in show_schedstat()

From: Markus Elfring Date: Sat, 6 May 2017 21:26:19 +0200 Some data were put into a sequence by two separate function calls. Print the same data by a single function call instead. This issue was detected by using the Coccinelle software. Signed-off-by: Markus

[PATCH 3/3] kernel-sched: Combine two seq_printf() calls into one in show_schedstat()

From: Markus Elfring Date: Sat, 6 May 2017 21:26:19 +0200 Some data were put into a sequence by two separate function calls. Print the same data by a single function call instead. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring --- kernel/sched/stats.c

[PATCH 2/3] kernel-sched: Adjust four checks for null pointers

From: Markus Elfring Date: Sat, 6 May 2017 21:17:36 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The script “checkpatch.pl” pointed information out like the following. Comparison to NULL could be written !… Thus

[PATCH 2/3] kernel-sched: Adjust four checks for null pointers

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

Re: [PATCH/RFC] signal: Export signal_wake_up_state() to modules

On 05/05, Geert Uytterhoeven wrote: > > I'm using signal_wake_up() to abort a task blocked on > wait_for_completion_interruptible(), cfr. sh_msiof_slave_abort() in > "spi: sh-msiof: Add slave mode support" > (http://www.spinics.net/lists/devicetree/msg175575.html). > > Is exporting

Re: [PATCH/RFC] signal: Export signal_wake_up_state() to modules

On 05/05, Geert Uytterhoeven wrote: > > I'm using signal_wake_up() to abort a task blocked on > wait_for_completion_interruptible(), cfr. sh_msiof_slave_abort() in > "spi: sh-msiof: Add slave mode support" > (http://www.spinics.net/lists/devicetree/msg175575.html). > > Is exporting

[PATCH 1/3] kernel-sched: Use seq_putc() in three functions

From: Markus Elfring Date: Sat, 6 May 2017 20:45:35 +0200 Four single characters (line breaks) should be put into a sequence. Thus use the corresponding function "seq_putc". This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring

[PATCH 1/3] kernel-sched: Use seq_putc() in three functions

From: Markus Elfring Date: Sat, 6 May 2017 20:45:35 +0200 Four single characters (line breaks) should be put into a sequence. Thus use the corresponding function "seq_putc". This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring --- kernel/sched/cpuacct.c | 6

[PATCH 0/3] kernel-sched: Fine-tuning for eight function implementations

From: Markus Elfring Date: Sat, 6 May 2017 21:35:45 +0200 A few update suggestions were taken into account from static source code analysis. Markus Elfring (3): Use seq_putc() in three functions Adjust four checks for null pointers Combine two seq_printf()

[PATCH 0/3] kernel-sched: Fine-tuning for eight function implementations

From: Markus Elfring Date: Sat, 6 May 2017 21:35:45 +0200 A few update suggestions were taken into account from static source code analysis. Markus Elfring (3): Use seq_putc() in three functions Adjust four checks for null pointers Combine two seq_printf() calls into one in

Re: [PATCH] pinctrl: imx: Check for memory allocation failure

Hi Christophe, On Sat, May 06, 2017 at 10:23:59AM +0200, Christophe JAILLET wrote: > If 'devm_kzalloc' fails, a NULL pointer will be dereferenced. > Return -ENOMEM instead, as done for the other memory allocation just a > few lines below. This looks fine. > BTW, change the 'devm_kzalloc' into a

Re: [PATCH] pinctrl: imx: Check for memory allocation failure

Hi Christophe, On Sat, May 06, 2017 at 10:23:59AM +0200, Christophe JAILLET wrote: > If 'devm_kzalloc' fails, a NULL pointer will be dereferenced. > Return -ENOMEM instead, as done for the other memory allocation just a > few lines below. This looks fine. > BTW, change the 'devm_kzalloc' into a

Re: [PATCH 2/2] arm64:vdso: Remove ISB from gettimeofday.

Quick reply - didn't realize it could be speculatively read as described, but I should have. Makes sense now, thanks. -- Computer Architect | Sent from my 64-bit #ARM Powered phone > On May 6, 2017, at 13:38, Pinski, Andrew wrote: > > Sorry sending again as plain

Re: [PATCH 2/2] arm64:vdso: Remove ISB from gettimeofday.

Quick reply - didn't realize it could be speculatively read as described, but I should have. Makes sense now, thanks. -- Computer Architect | Sent from my 64-bit #ARM Powered phone > On May 6, 2017, at 13:38, Pinski, Andrew wrote: > > Sorry sending again as plain text (I did not notice that

Re: [PATCH] scsi: qedf: Avoid reading past end of buffer

On Fri, 5 May 2017, 7:10pm, Kees Cook wrote: > On Fri, May 5, 2017 at 4:01 PM, Bart Van Assche > wrote: > > On Fri, 2017-05-05 at 15:42 -0700, Kees Cook wrote: > >> diff --git a/drivers/scsi/qedf/qedf_main.c b/drivers/scsi/qedf/qedf_main.c > >> index

Re: [PATCH] scsi: qedf: Avoid reading past end of buffer

On Fri, 5 May 2017, 7:10pm, Kees Cook wrote: > On Fri, May 5, 2017 at 4:01 PM, Bart Van Assche > wrote: > > On Fri, 2017-05-05 at 15:42 -0700, Kees Cook wrote: > >> diff --git a/drivers/scsi/qedf/qedf_main.c b/drivers/scsi/qedf/qedf_main.c > >> index cceddd995a4b..a5c97342fd5d 100644 > >> ---

Re: [4.12.0-rc0]: compile error in initramfs.c

On Sat, May 06, 2017 at 10:39:01AM -0700, Linus Torvalds wrote: > On Sat, May 6, 2017 at 10:28 AM, Randy Dunlap wrote: > > > > A fix was posted here: > > http://marc.info/?l=linux-kernel=149405418520059=2 > > That looks like it will just cause a warning instead ("unused

Re: [4.12.0-rc0]: compile error in initramfs.c

On Sat, May 06, 2017 at 10:39:01AM -0700, Linus Torvalds wrote: > On Sat, May 6, 2017 at 10:28 AM, Randy Dunlap wrote: > > > > A fix was posted here: > > http://marc.info/?l=linux-kernel=149405418520059=2 > > That looks like it will just cause a warning instead ("unused label"). > > The proper

Re: [RFC PATCH] x86/boot: Add the secdata section to the setup header

On May 6, 2017 10:34:49 AM PDT, Brian Gerst wrote: >On Fri, May 5, 2017 at 5:26 AM, Gary Lin wrote: >> This is a different approach to replace my previous implementation of >> Security Version(*). Instead of using the fields in the PE/COFF >header, >> this

Re: [RFC PATCH] x86/boot: Add the secdata section to the setup header

On May 6, 2017 10:34:49 AM PDT, Brian Gerst wrote: >On Fri, May 5, 2017 at 5:26 AM, Gary Lin wrote: >> This is a different approach to replace my previous implementation of >> Security Version(*). Instead of using the fields in the PE/COFF >header, >> this commit adds secdata_offset in the setup

Re: [PATCH] Input: psxpad-spi - Add PlayStation 1/2 joypads via SPI interface Driver

Mr.Torokhov Mr.Herrmann Sorry, I sent Playstation 1/2 joypads patch again. Mr.Torokhov's Reviewed-by added. Best regard. 2017-05-07 3:41 GMT+09:00 Tomohiro Yoshidomi : > PlayStation 1/2 joypads can be connected directly to the SPI interface. > > Signed-off-by: Tomohiro

Re: [PATCH] Input: psxpad-spi - Add PlayStation 1/2 joypads via SPI interface Driver

Mr.Torokhov Mr.Herrmann Sorry, I sent Playstation 1/2 joypads patch again. Mr.Torokhov's Reviewed-by added. Best regard. 2017-05-07 3:41 GMT+09:00 Tomohiro Yoshidomi : > PlayStation 1/2 joypads can be connected directly to the SPI interface. > > Signed-off-by: Tomohiro Yoshidomi > Reviewed-by:

[PATCH] Input: psxpad-spi - Add PlayStation 1/2 joypads via SPI interface Driver

PlayStation 1/2 joypads can be connected directly to the SPI interface. Signed-off-by: Tomohiro Yoshidomi Reviewed-by: Dmitry Torokhov Acked-by: David Herrmann --- drivers/input/joystick/Kconfig | 22 ++

[PATCH] Input: psxpad-spi - Add PlayStation 1/2 joypads via SPI interface Driver

PlayStation 1/2 joypads can be connected directly to the SPI interface. Signed-off-by: Tomohiro Yoshidomi Reviewed-by: Dmitry Torokhov Acked-by: David Herrmann --- drivers/input/joystick/Kconfig | 22 ++ drivers/input/joystick/Makefile | 1 + drivers/input/joystick/psxpad-spi.c |

Re: [PATCH] Input: psxpad-spi - Add PlayStation 1/2 joypads via SPI interface Driver

Mr.Torokhov Mr.Herrmann I sent Playstation 1/2 joypads patch, Mr.Hrrmann's Ack-by added. Best regard.

Re: [PATCH] Input: psxpad-spi - Add PlayStation 1/2 joypads via SPI interface Driver

Mr.Torokhov Mr.Herrmann I sent Playstation 1/2 joypads patch, Mr.Hrrmann's Ack-by added. Best regard.

Re: [PATCH v7] Input: psxpad-spi - Add PlayStation 1/2 joypads via SPI interface Driver

Mr.Torokhov Mr.Herrmann I sent Playstation 1/2 joypads patch, Mr.Hrrmann's Ack-by added. Best regard.

Re: [PATCH v7] Input: psxpad-spi - Add PlayStation 1/2 joypads via SPI interface Driver

Mr.Torokhov Mr.Herrmann I sent Playstation 1/2 joypads patch, Mr.Hrrmann's Ack-by added. Best regard.

[PATCH] Input: psxpad-spi - Add PlayStation 1/2 joypads via SPI interface Driver

PlayStation 1/2 joypads can be connected directly to the SPI interface. Signed-off-by: Tomohiro Yoshidomi Acked-by: David Herrmann --- drivers/input/joystick/Kconfig | 22 ++ drivers/input/joystick/Makefile | 1 +

[PATCH] Input: psxpad-spi - Add PlayStation 1/2 joypads via SPI interface Driver

PlayStation 1/2 joypads can be connected directly to the SPI interface. Signed-off-by: Tomohiro Yoshidomi Acked-by: David Herrmann --- drivers/input/joystick/Kconfig | 22 ++ drivers/input/joystick/Makefile | 1 + drivers/input/joystick/psxpad-spi.c | 438

Re: [GIT PULL] Char/Misc driver patches for 4.12-rc1

On Sat, 2017-05-06 at 11:00 -0700, Linus Torvalds wrote: > On Fri, May 5, 2017 at 10:09 PM, Stephen Rothwell < > s...@canb.auug.org.au> wrote: > > > > On Fri, 5 May 2017 13:01:34 -0700 Linus Torvalds < > > torva...@linux-foundation.org> wrote: > > > > > > > > > I prefer doing merge resolutions

Re: [GIT PULL] Char/Misc driver patches for 4.12-rc1

On Sat, 2017-05-06 at 11:00 -0700, Linus Torvalds wrote: > On Fri, May 5, 2017 at 10:09 PM, Stephen Rothwell < > s...@canb.auug.org.au> wrote: > > > > On Fri, 5 May 2017 13:01:34 -0700 Linus Torvalds < > > torva...@linux-foundation.org> wrote: > > > > > > > > > I prefer doing merge resolutions

[PATCH v3] backlight: report error on failure

It is possible to update the backlight power and the brightness using the sysfs and on writing it either returns the count or if the callback function does not exist then returns the error code 'ENXIO'. We have a situation where the userspace client is writing to the sysfs to update the power and

[PATCH v3] backlight: report error on failure

It is possible to update the backlight power and the brightness using the sysfs and on writing it either returns the count or if the callback function does not exist then returns the error code 'ENXIO'. We have a situation where the userspace client is writing to the sysfs to update the power and

  1   2   3   4   >