[tip:perf/urgent] tooling headers: Synchronize updated s390 kvm UAPI headers

Commit-ID: 9a3853587c2bb0a38c2ce80a613ace5e84ae4337 Gitweb: https://git.kernel.org/tip/9a3853587c2bb0a38c2ce80a613ace5e84ae4337 Author: Arnaldo Carvalho de Melo AuthorDate: Fri, 2 Feb 2018 16:43:45 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 2 Feb 2018 16:43:45 -0300

[tip:perf/urgent] tools headers: Synchronize sound/asound.h

Commit-ID: 6bc7626c046e069ea4802f3fbc7a41059047ac77 Gitweb: https://git.kernel.org/tip/6bc7626c046e069ea4802f3fbc7a41059047ac77 Author: Arnaldo Carvalho de Melo AuthorDate: Fri, 2 Feb 2018 13:06:04 -0300 Committer: Arnaldo Carvalho de Melo CommitDate: Fri, 2 Feb 2018 16:41:49 -0300

Re: [PATCH 3.18 00/36] 3.18.94-stable review

On Mon, Feb 05, 2018 at 10:23:28AM -0800, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 3.18.94 release. > There are 36 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

Re: [PATCH 3.18 00/36] 3.18.94-stable review

On Mon, Feb 05, 2018 at 10:23:28AM -0800, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 3.18.94 release. > There are 36 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

Re: [PATCH v4 2/5] irqchip/gic-v3-its: add ability to save/restore ITS state

On Mon, Feb 5, 2018 at 7:56 AM, Marc Zyngier wrote: > On 03/02/18 01:24, Derek Basehore wrote: >> Some platforms power off GIC logic in suspend, so we need to >> save/restore state. The distributor and redistributor registers need >> to be handled in platform code due to

Re: [PATCH v4 2/5] irqchip/gic-v3-its: add ability to save/restore ITS state

On Mon, Feb 5, 2018 at 7:56 AM, Marc Zyngier wrote: > On 03/02/18 01:24, Derek Basehore wrote: >> Some platforms power off GIC logic in suspend, so we need to >> save/restore state. The distributor and redistributor registers need >> to be handled in platform code due to access permissions on

Re: [PATCH v2 1/3] x86/entry: Clear extra registers beyond syscall arguments for 64bit kernels

On Mon, Feb 5, 2018 at 3:58 AM, Ingo Molnar wrote: > > * Dan Williams wrote: > >> + /* >> + * Sanitize extra registers of values that a speculation attack >> + * might want to exploit. In the CONFIG_FRAME_POINTER=y case, >> + * the

Re: [PATCH v2 1/3] x86/entry: Clear extra registers beyond syscall arguments for 64bit kernels

On Mon, Feb 5, 2018 at 3:58 AM, Ingo Molnar wrote: > > * Dan Williams wrote: > >> + /* >> + * Sanitize extra registers of values that a speculation attack >> + * might want to exploit. In the CONFIG_FRAME_POINTER=y case, >> + * the expectation is that %ebp will be clobbered

[PATCH 4/4] HID: logitech-dj: Fix a typo in a comment line

From: Markus Elfring Date: Mon, 5 Feb 2018 22:14:49 +0100 Adjust a word in this description. Signed-off-by: Markus Elfring --- drivers/hid/hid-logitech-dj.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 4/4] HID: logitech-dj: Fix a typo in a comment line

From: Markus Elfring Date: Mon, 5 Feb 2018 22:14:49 +0100 Adjust a word in this description. Signed-off-by: Markus Elfring --- drivers/hid/hid-logitech-dj.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/hid/hid-logitech-dj.c b/drivers/hid/hid-logitech-dj.c index

Re: [PATCH v2 8/8] platform: vivid-cec: use 64-bit arithmetic instead of 32-bit

On 02/05/2018 09:36 PM, Gustavo A. R. Silva wrote: > Add suffix ULL to constant 10 in order to give the compiler complete > information about the proper arithmetic to use. Notice that this > constant is used in a context that expects an expression of type > u64 (64 bits, unsigned). > > The

Re: [PATCH v2 8/8] platform: vivid-cec: use 64-bit arithmetic instead of 32-bit

On 02/05/2018 09:36 PM, Gustavo A. R. Silva wrote: > Add suffix ULL to constant 10 in order to give the compiler complete > information about the proper arithmetic to use. Notice that this > constant is used in a context that expects an expression of type > u64 (64 bits, unsigned). > > The

[PATCH 3/4] HID: logitech-dj: Combine substrings for seven messages

From: Markus Elfring Date: Mon, 5 Feb 2018 22:06:20 +0100 The script "checkpatch.pl" pointed information out like the following. WARNING: quoted string split across lines Thus fix the affected source code places. Signed-off-by: Markus Elfring

[PATCH 3/4] HID: logitech-dj: Combine substrings for seven messages

From: Markus Elfring Date: Mon, 5 Feb 2018 22:06:20 +0100 The script "checkpatch.pl" pointed information out like the following. WARNING: quoted string split across lines Thus fix the affected source code places. Signed-off-by: Markus Elfring --- drivers/hid/hid-logitech-dj.c | 29

Re: [GIT PULL 00/10] perf/urgent fixes

> > The following changes since commit 72906f38934a49faf4d2d38ea9ae32adcf7d5d0c: > > Merge branch 'x86-hyperv-for-linus' of > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip (2018-01-30 13:04:50 > -0800) > > are available in the Git repository at: > > git://git.kernel.org/pub/scm/linux/

[PATCH 2/4] HID: logitech-dj: Improve a size determination in four functions

From: Markus Elfring Date: Mon, 5 Feb 2018 21:47:45 +0100 Replace the specification of data structures by pointer dereferences as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style

Re: [GIT PULL 00/10] perf/urgent fixes

f7d5d0c: > > Merge branch 'x86-hyperv-for-linus' of > git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip (2018-01-30 13:04:50 > -0800) > > are available in the Git repository at: > > git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git > tags/perf-urg

[PATCH 2/4] HID: logitech-dj: Improve a size determination in four functions

From: Markus Elfring Date: Mon, 5 Feb 2018 21:47:45 +0100 Replace the specification of data structures by pointer dereferences as the parameter for the operator "sizeof" to make the corresponding size determination a bit safer according to the Linux coding style convention. This issue was

[PATCH 1/4] HID: logitech-dj: Delete an error message for a failed memory allocation in two functions

From: Markus Elfring Date: Mon, 5 Feb 2018 21:36:18 +0100 Omit an extra message for a memory allocation failure in these functions. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring ---

[PATCH 1/4] HID: logitech-dj: Delete an error message for a failed memory allocation in two functions

From: Markus Elfring Date: Mon, 5 Feb 2018 21:36:18 +0100 Omit an extra message for a memory allocation failure in these functions. This issue was detected by using the Coccinelle software. Signed-off-by: Markus Elfring --- drivers/hid/hid-logitech-dj.c | 12 +++- 1 file changed, 3

[PATCH 0/4] HID: logitech-dj: Adjustments for some function implementations

From: Markus Elfring Date: Mon, 5 Feb 2018 22:22:11 +0100 A few update suggestions were taken into account from static source code analysis. Markus Elfring (4): Delete an error message for a failed memory allocation in two functions Improve a size

[PATCH 0/4] HID: logitech-dj: Adjustments for some function implementations

From: Markus Elfring Date: Mon, 5 Feb 2018 22:22:11 +0100 A few update suggestions were taken into account from static source code analysis. Markus Elfring (4): Delete an error message for a failed memory allocation in two functions Improve a size determination in four functions Combine

Re: [PATCH for 4.16 00/11] membarrier updates for 4.16

Hi, Find below the interdiff of the (minor) edits I've done to the series, before applying them to tip:sched/urgent. I've also tidied up some of the changelogs. Nothing earth-shattering. Thanks, Ingo => arch/powerpc/Kconfig | 2 +- arch/x86/entry/entry_32.S | 2 +-

Re: [PATCH for 4.16 00/11] membarrier updates for 4.16

Hi, Find below the interdiff of the (minor) edits I've done to the series, before applying them to tip:sched/urgent. I've also tidied up some of the changelogs. Nothing earth-shattering. Thanks, Ingo => arch/powerpc/Kconfig | 2 +- arch/x86/entry/entry_32.S | 2 +-

Re: [tip:x86/urgent] x86/dumpstack: Avoid uninitlized variable

On Fri, Feb 2, 2018 at 11:36 PM, tip-bot for Arnd Bergmann wrote: > Commit-ID: ebfc15019cfa72496c674ffcb0b8ef10790dcddc > Gitweb: > https://git.kernel.org/tip/ebfc15019cfa72496c674ffcb0b8ef10790dcddc > Author: Arnd Bergmann > AuthorDate: Fri, 2 Feb 2018

Re: [tip:x86/urgent] x86/dumpstack: Avoid uninitlized variable

On Fri, Feb 2, 2018 at 11:36 PM, tip-bot for Arnd Bergmann wrote: > Commit-ID: ebfc15019cfa72496c674ffcb0b8ef10790dcddc > Gitweb: > https://git.kernel.org/tip/ebfc15019cfa72496c674ffcb0b8ef10790dcddc > Author: Arnd Bergmann > AuthorDate: Fri, 2 Feb 2018 15:56:17 +0100 > Committer:

Re: [PATCH] usb: dwc2: gadget: Use true and false for boolean values

On 01/23/2018 07:45 AM, Gustavo A. R. Silva wrote: Assign true or false to boolean variables instead of an integer value. This issue was detected with the help of Coccinelle. Signed-off-by: Gustavo A. R. Silva --- drivers/usb/dwc2/gadget.c | 4 ++-- 1 file changed,

Re: [PATCH] usb: dwc2: gadget: Use true and false for boolean values

On 01/23/2018 07:45 AM, Gustavo A. R. Silva wrote: Assign true or false to boolean variables instead of an integer value. This issue was detected with the help of Coccinelle. Signed-off-by: Gustavo A. R. Silva --- drivers/usb/dwc2/gadget.c | 4 ++-- 1 file changed, 2 insertions(+), 2

Re: [PATCH 1/3] perf tools: Fix period/freq terms setup

Em Mon, Feb 05, 2018 at 12:58:16PM -0800, Stephane Eranian escreveu: > On Mon, Feb 5, 2018 at 7:17 AM, Jiri Olsa wrote: > > On Fri, Feb 02, 2018 at 01:04:34PM -0800, Stephane Eranian wrote: > >> On Fri, Feb 2, 2018 at 12:40 PM, Arnaldo Carvalho de Melo > >>

Re: [PATCH 1/3] perf tools: Fix period/freq terms setup

Em Mon, Feb 05, 2018 at 12:58:16PM -0800, Stephane Eranian escreveu: > On Mon, Feb 5, 2018 at 7:17 AM, Jiri Olsa wrote: > > On Fri, Feb 02, 2018 at 01:04:34PM -0800, Stephane Eranian wrote: > >> On Fri, Feb 2, 2018 at 12:40 PM, Arnaldo Carvalho de Melo > >> wrote: > >> > Em Fri, Feb 02, 2018 at

[PATCH v2 8/8] platform: vivid-cec: use 64-bit arithmetic instead of 32-bit

Add suffix ULL to constant 10 in order to give the compiler complete information about the proper arithmetic to use. Notice that this constant is used in a context that expects an expression of type u64 (64 bits, unsigned). The expression len * 10 * CEC_TIM_DATA_BIT_TOTAL is currently being

[PATCH v2 8/8] platform: vivid-cec: use 64-bit arithmetic instead of 32-bit

Add suffix ULL to constant 10 in order to give the compiler complete information about the proper arithmetic to use. Notice that this constant is used in a context that expects an expression of type u64 (64 bits, unsigned). The expression len * 10 * CEC_TIM_DATA_BIT_TOTAL is currently being

Re: [PATCH] vsprintf: avoid misleading "(null)" for %px

On Tue, Feb 06, 2018 at 07:32:32AM +1100, Kees Cook wrote: > On Tue, Feb 6, 2018 at 7:15 AM, Tobin C. Harding wrote: > > On Tue, Feb 06, 2018 at 05:57:17AM +1100, Kees Cook wrote: > >> On Mon, Feb 5, 2018 at 8:44 PM, Petr Mladek wrote: > >> > On Sun 2018-02-04

Re: [PATCH] vsprintf: avoid misleading "(null)" for %px

On Tue, Feb 06, 2018 at 07:32:32AM +1100, Kees Cook wrote: > On Tue, Feb 6, 2018 at 7:15 AM, Tobin C. Harding wrote: > > On Tue, Feb 06, 2018 at 05:57:17AM +1100, Kees Cook wrote: > >> On Mon, Feb 5, 2018 at 8:44 PM, Petr Mladek wrote: > >> > On Sun 2018-02-04 18:45:21, Adam Borowski wrote: > >>

Re: [PATCH 1/3] perf tools: Fix period/freq terms setup

On Mon, Feb 5, 2018 at 7:17 AM, Jiri Olsa wrote: > On Fri, Feb 02, 2018 at 01:04:34PM -0800, Stephane Eranian wrote: >> On Fri, Feb 2, 2018 at 12:40 PM, Arnaldo Carvalho de Melo >> wrote: >> > Em Fri, Feb 02, 2018 at 05:28:49PM -0300, Arnaldo Carvalho de Melo

Re: [PATCH 1/3] perf tools: Fix period/freq terms setup

On Mon, Feb 5, 2018 at 7:17 AM, Jiri Olsa wrote: > On Fri, Feb 02, 2018 at 01:04:34PM -0800, Stephane Eranian wrote: >> On Fri, Feb 2, 2018 at 12:40 PM, Arnaldo Carvalho de Melo >> wrote: >> > Em Fri, Feb 02, 2018 at 05:28:49PM -0300, Arnaldo Carvalho de Melo >> > escreveu: >> >> Em Fri, Feb

Re: [PATCH V2 0/7] sched/deadline: fix cpusets bandwidth accounting

On Fri, Feb 02, 2018 at 02:17:50PM +0100, Luca Abeni wrote: > Hi Mathieu, > > On Thu, 1 Feb 2018 09:51:02 -0700 > Mathieu Poirier wrote: > > > This is the follow-up patchset to [1] that attempt to fix a problem > > reported by Steve Rostedt [2] where DL bandwidth

Re: [PATCH V2 0/7] sched/deadline: fix cpusets bandwidth accounting

On Fri, Feb 02, 2018 at 02:17:50PM +0100, Luca Abeni wrote: > Hi Mathieu, > > On Thu, 1 Feb 2018 09:51:02 -0700 > Mathieu Poirier wrote: > > > This is the follow-up patchset to [1] that attempt to fix a problem > > reported by Steve Rostedt [2] where DL bandwidth accounting is not > >

Re: [PATCH] libnvdimm: remove redundant assignment to pointer 'dev'

On 05/02/18 18:44, Dan Williams wrote: > On Mon, Feb 5, 2018 at 10:20 AM, Ross Zwisler > wrote: >> On Mon, Feb 05, 2018 at 02:08:52PM +, Colin King wrote: >>> From: Colin Ian King >>> >>> Pointer dev is being assigned a value that is

Re: [PATCH] libnvdimm: remove redundant assignment to pointer 'dev'

On 05/02/18 18:44, Dan Williams wrote: > On Mon, Feb 5, 2018 at 10:20 AM, Ross Zwisler > wrote: >> On Mon, Feb 05, 2018 at 02:08:52PM +, Colin King wrote: >>> From: Colin Ian King >>> >>> Pointer dev is being assigned a value that is never read, it is being >>> re-assigned the same value

[GIT PULL] xfs: updates for 4.16

Hi Linus, As promised, here's a (much smaller) second pull request for the second week of the merge cycle. This time around we have a couple patches shutting off unsupported fs configurations, and a couple of cleanups. Last, we turn off EXPERIMENTAL for the reverse mapping btree, since the

[GIT PULL] xfs: updates for 4.16

Hi Linus, As promised, here's a (much smaller) second pull request for the second week of the merge cycle. This time around we have a couple patches shutting off unsupported fs configurations, and a couple of cleanups. Last, we turn off EXPERIMENTAL for the reverse mapping btree, since the

Re: [PATCH] vsprintf: avoid misleading "(null)" for %px

On Tue, Feb 6, 2018 at 7:15 AM, Tobin C. Harding wrote: > On Tue, Feb 06, 2018 at 05:57:17AM +1100, Kees Cook wrote: >> On Mon, Feb 5, 2018 at 8:44 PM, Petr Mladek wrote: >> > Hi, >> > >> > I add people who actively commented on adding %px modifier, >> > see the

Re: [PATCH] vsprintf: avoid misleading "(null)" for %px

On Tue, Feb 6, 2018 at 7:15 AM, Tobin C. Harding wrote: > On Tue, Feb 06, 2018 at 05:57:17AM +1100, Kees Cook wrote: >> On Mon, Feb 5, 2018 at 8:44 PM, Petr Mladek wrote: >> > Hi, >> > >> > I add people who actively commented on adding %px modifier, >> > see the thread starting at >> >

Re: [PATCH for 4.16 v7 02/11] powerpc: membarrier: Skip memory barrier in switch_mm()

- On Feb 5, 2018, at 3:22 PM, Ingo Molnar mi...@kernel.org wrote: > * Mathieu Desnoyers wrote: > >> >> +config ARCH_HAS_MEMBARRIER_HOOKS >> +bool > > Yeah, so I have renamed this to ARCH_HAS_MEMBARRIER_CALLBACKS, and propagated > it > through the rest

Re: [PATCH for 4.16 v7 02/11] powerpc: membarrier: Skip memory barrier in switch_mm()

- On Feb 5, 2018, at 3:22 PM, Ingo Molnar mi...@kernel.org wrote: > * Mathieu Desnoyers wrote: > >> >> +config ARCH_HAS_MEMBARRIER_HOOKS >> +bool > > Yeah, so I have renamed this to ARCH_HAS_MEMBARRIER_CALLBACKS, and propagated > it > through the rest of the patches. "Callback" is

Re: [PATCH 1/2] modpost: don't add warnings for LTO-generated symbols

On Mon, Feb 5, 2018 at 5:22 PM, Andi Kleen wrote: > On Mon, Feb 05, 2018 at 04:59:32PM +0100, Arnd Bergmann wrote: >> On Mon, Feb 5, 2018 at 4:50 PM, Andi Kleen wrote: >> > On Mon, Feb 05, 2018 at 04:12:52PM +0100, Arnd Bergmann wrote: >> >> WARNING:

Re: [PATCH 1/2] modpost: don't add warnings for LTO-generated symbols

On Mon, Feb 5, 2018 at 5:22 PM, Andi Kleen wrote: > On Mon, Feb 05, 2018 at 04:59:32PM +0100, Arnd Bergmann wrote: >> On Mon, Feb 5, 2018 at 4:50 PM, Andi Kleen wrote: >> > On Mon, Feb 05, 2018 at 04:12:52PM +0100, Arnd Bergmann wrote: >> >> WARNING: vmlinux.o(.data+0x12e0): Section mismatch in

Re: [PATCH 05/20] rtc: at32ap700x: Remove PLATFORM_AT32AP dependency

On Mon, Feb 5, 2018 at 3:01 PM, Alexandre Belloni wrote: > Hi, > > On 05/02/2018 at 02:42:38 +0100, Ulf Magnusson wrote: >> On Mon, Feb 5, 2018 at 2:21 AM, Ulf Magnusson wrote: >> > The PLATFORM_AT32AP symbol went away when AVR32 was

Re: [PATCH 05/20] rtc: at32ap700x: Remove PLATFORM_AT32AP dependency

On Mon, Feb 5, 2018 at 3:01 PM, Alexandre Belloni wrote: > Hi, > > On 05/02/2018 at 02:42:38 +0100, Ulf Magnusson wrote: >> On Mon, Feb 5, 2018 at 2:21 AM, Ulf Magnusson wrote: >> > The PLATFORM_AT32AP symbol went away when AVR32 was removed in >> > commit 26202873bb51 ("avr32: remove support

[PATCH v2 4/8] i2c: ov9650: use 64-bit arithmetic instead of 32-bit

Add suffix ULL to constants 1 and 100 in order to give the compiler complete information about the proper arithmetic to use. Notice that these constants are used in contexts that expect expressions of type u64 (64 bits, unsigned). The following expressions: (u64)(fi->interval.numerator *

[PATCH v2 4/8] i2c: ov9650: use 64-bit arithmetic instead of 32-bit

Add suffix ULL to constants 1 and 100 in order to give the compiler complete information about the proper arithmetic to use. Notice that these constants are used in contexts that expect expressions of type u64 (64 bits, unsigned). The following expressions: (u64)(fi->interval.numerator *

[PATCH v2 3/8] i2c: max2175: use 64-bit arithmetic instead of 32-bit

Add suffix LL to constant 2 in order to give the compiler complete information about the proper arithmetic to use. Notice that this constant is used in a context that expects an expression of type s64 (64 bits, signed). The expression 2 * (clock_rate - abs_nco_freq) is currently being evaluated

[PATCH v2 3/8] i2c: max2175: use 64-bit arithmetic instead of 32-bit

Add suffix LL to constant 2 in order to give the compiler complete information about the proper arithmetic to use. Notice that this constant is used in a context that expects an expression of type s64 (64 bits, signed). The expression 2 * (clock_rate - abs_nco_freq) is currently being evaluated

[PATCH v2 0/8] use 64-bit arithmetic instead of 32-bit

Add suffix LL and ULL to various constants in order to give the compiler complete information about the proper arithmetic to use. Such constants are used in contexts that expect expressions of type u64 (64 bits, unsigned) and s64 (64 bits, signed). The mentioned expressions are currently being

[PATCH v2 0/8] use 64-bit arithmetic instead of 32-bit

Add suffix LL and ULL to various constants in order to give the compiler complete information about the proper arithmetic to use. Such constants are used in contexts that expect expressions of type u64 (64 bits, unsigned) and s64 (64 bits, signed). The mentioned expressions are currently being

Re: [PATCH v3 1/2] ASoC: codecs: Add support for AK5558 ADC driver

On Mon, Feb 5, 2018 at 3:01 PM, Daniel Baluta wrote: > AK5558 is a 32-bit, 768 kHZ sampling, differential input ADC > for digital audio systems. > > Datasheet is available at: > > https://www.akm.com/akm/en/file/datasheet/AK5558VN.pdf > > Initial patch includes support for

[PATCH v2 7/8] platform: sh_veu: use 64-bit arithmetic instead of 32-bit

Cast left and top to dma_addr_t in order to give the compiler complete information about the proper arithmetic to use. Notice that these variables are being used in contexts that expect expressions of type dma_addr_t (64 bit, unsigned). Such expressions are currently being evaluated using 32-bit

Re: [PATCH v3 1/2] ASoC: codecs: Add support for AK5558 ADC driver

On Mon, Feb 5, 2018 at 3:01 PM, Daniel Baluta wrote: > AK5558 is a 32-bit, 768 kHZ sampling, differential input ADC > for digital audio systems. > > Datasheet is available at: > > https://www.akm.com/akm/en/file/datasheet/AK5558VN.pdf > > Initial patch includes support for normal and TDM modes. >

[PATCH v2 7/8] platform: sh_veu: use 64-bit arithmetic instead of 32-bit

Cast left and top to dma_addr_t in order to give the compiler complete information about the proper arithmetic to use. Notice that these variables are being used in contexts that expect expressions of type dma_addr_t (64 bit, unsigned). Such expressions are currently being evaluated using 32-bit

[PATCH v2 5/8] pci: cx88-input: use 64-bit arithmetic instead of 32-bit

Add suffix LL to constant 100 in order to give the compiler complete information about the proper arithmetic to use. Notice that this constant is used in a context that expects an expression of type ktime_t (64 bits, signed). The expression ir->polling * 100 is currently being evaluated

[PATCH v2 6/8] rockchip/rga: use 64-bit arithmetic instead of 32-bit

Cast p to dma_addr_t in order to avoid a potential integer overflow. This variable is being used in a context that expects an expression of type dma_addr_t (u64). The expression p << PAGE_SHIFT is currently being evaluated using 32-bit arithmetic. Addresses-Coverity-ID: 1458347 Signed-off-by:

[PATCH v2 5/8] pci: cx88-input: use 64-bit arithmetic instead of 32-bit

Add suffix LL to constant 100 in order to give the compiler complete information about the proper arithmetic to use. Notice that this constant is used in a context that expects an expression of type ktime_t (64 bits, signed). The expression ir->polling * 100 is currently being evaluated

[PATCH v2 6/8] rockchip/rga: use 64-bit arithmetic instead of 32-bit

Cast p to dma_addr_t in order to avoid a potential integer overflow. This variable is being used in a context that expects an expression of type dma_addr_t (u64). The expression p << PAGE_SHIFT is currently being evaluated using 32-bit arithmetic. Addresses-Coverity-ID: 1458347 Signed-off-by:

Re: [PATCH v3 2/2] ASoC: ak5558: Add bindings for AK5558 ADC

On Mon, Feb 5, 2018 at 3:01 PM, Daniel Baluta wrote: > Document the bindings for AK5558 ADC. > > Signed-off-by: Daniel Baluta > --- > Documentation/devicetree/bindings/sound/ak5558.txt | 22 > ++ > 1 file changed, 22

Re: [PATCH v3 2/2] ASoC: ak5558: Add bindings for AK5558 ADC

On Mon, Feb 5, 2018 at 3:01 PM, Daniel Baluta wrote: > Document the bindings for AK5558 ADC. > > Signed-off-by: Daniel Baluta > --- > Documentation/devicetree/bindings/sound/ak5558.txt | 22 > ++ > 1 file changed, 22 insertions(+) > create mode 100644

Re: [PATCH 1/3] x86/entry: Clear extra registers beyond syscall arguments for 64bit kernels

On Mon, Feb 5, 2018 at 7:48 PM, Ingo Molnar wrote: > > * Brian Gerst wrote: > >> On Mon, Feb 5, 2018 at 1:29 PM, Ingo Molnar wrote: >> > >> > * Andy Lutomirski wrote: >> > >> >> [...] Clearing R10 is mostly useless in the

Re: [PATCH 1/3] x86/entry: Clear extra registers beyond syscall arguments for 64bit kernels

On Mon, Feb 5, 2018 at 7:48 PM, Ingo Molnar wrote: > > * Brian Gerst wrote: > >> On Mon, Feb 5, 2018 at 1:29 PM, Ingo Molnar wrote: >> > >> > * Andy Lutomirski wrote: >> > >> >> [...] Clearing R10 is mostly useless in the syscall path because we'll >> >> just >> >> unconditionally reload it

Re: [PATCH for 4.16 v7 02/11] powerpc: membarrier: Skip memory barrier in switch_mm()

* Mathieu Desnoyers wrote: > > +config ARCH_HAS_MEMBARRIER_HOOKS > + bool Yeah, so I have renamed this to ARCH_HAS_MEMBARRIER_CALLBACKS, and propagated it through the rest of the patches. "Callback" is the canonical name, and I also cringe every time I

Re: [PATCH for 4.16 v7 02/11] powerpc: membarrier: Skip memory barrier in switch_mm()

* Mathieu Desnoyers wrote: > > +config ARCH_HAS_MEMBARRIER_HOOKS > + bool Yeah, so I have renamed this to ARCH_HAS_MEMBARRIER_CALLBACKS, and propagated it through the rest of the patches. "Callback" is the canonical name, and I also cringe every time I see 'hook'. Please let me know

[PATCH v3 0/2] Add support for AK5558 ADC

We support normal mode, TDM mode and pm. Changes since v2: [addressed comments from Andy, Fabio and Rob] * sort include files * use probe_new * reword the binding document * use adc@10 instead of ak5558@10 * remove file name at the beginning of codec source code. * make i2c_probe and i2c_remove

[PATCH v3 0/2] Add support for AK5558 ADC

We support normal mode, TDM mode and pm. Changes since v2: [addressed comments from Andy, Fabio and Rob] * sort include files * use probe_new * reword the binding document * use adc@10 instead of ak5558@10 * remove file name at the beginning of codec source code. * make i2c_probe and i2c_remove

[PATCH v3 2/2] ASoC: ak5558: Add bindings for AK5558 ADC

Document the bindings for AK5558 ADC. Signed-off-by: Daniel Baluta --- Documentation/devicetree/bindings/sound/ak5558.txt | 22 ++ 1 file changed, 22 insertions(+) create mode 100644 Documentation/devicetree/bindings/sound/ak5558.txt diff --git

[PATCH v3 2/2] ASoC: ak5558: Add bindings for AK5558 ADC

Document the bindings for AK5558 ADC. Signed-off-by: Daniel Baluta --- Documentation/devicetree/bindings/sound/ak5558.txt | 22 ++ 1 file changed, 22 insertions(+) create mode 100644 Documentation/devicetree/bindings/sound/ak5558.txt diff --git

[PATCH v3 1/2] ASoC: codecs: Add support for AK5558 ADC driver

AK5558 is a 32-bit, 768 kHZ sampling, differential input ADC for digital audio systems. Datasheet is available at: https://www.akm.com/akm/en/file/datasheet/AK5558VN.pdf Initial patch includes support for normal and TDM modes. Signed-off-by: Junichi Wakasugi

[PATCH v3 1/2] ASoC: codecs: Add support for AK5558 ADC driver

AK5558 is a 32-bit, 768 kHZ sampling, differential input ADC for digital audio systems. Datasheet is available at: https://www.akm.com/akm/en/file/datasheet/AK5558VN.pdf Initial patch includes support for normal and TDM modes. Signed-off-by: Junichi Wakasugi [initial coding for 3.18 kernel]

Re: [PATCH] vsprintf: avoid misleading "(null)" for %px

On Mon, Feb 05, 2018 at 09:36:03AM -0800, Randy Dunlap wrote: > On 02/05/2018 08:49 AM, Steven Rostedt wrote: > > On Mon, 5 Feb 2018 16:22:19 +0100 > > Adam Borowski wrote: > > > >> My change touches %px only, where your concern doesn't apply. > >> > >> You're right, though,

Re: [PATCH] vsprintf: avoid misleading "(null)" for %px

On Mon, Feb 05, 2018 at 09:36:03AM -0800, Randy Dunlap wrote: > On 02/05/2018 08:49 AM, Steven Rostedt wrote: > > On Mon, 5 Feb 2018 16:22:19 +0100 > > Adam Borowski wrote: > > > >> My change touches %px only, where your concern doesn't apply. > >> > >> You're right, though, when it comes to

[GIT PULL] PCI changes for v4.16

PCI changes: - skip AER driver error recovery callbacks for correctable errors reported via ACPI APEI, as we already do for errors reported via the native path (Tyler Baicar) - fix DPC shared interrupt handling (Alex Williamson) - print full DPC interrupt number (Keith Busch) -

[GIT PULL] PCI changes for v4.16

PCI changes: - skip AER driver error recovery callbacks for correctable errors reported via ACPI APEI, as we already do for errors reported via the native path (Tyler Baicar) - fix DPC shared interrupt handling (Alex Williamson) - print full DPC interrupt number (Keith Busch) -

Re: [PATCH] vsprintf: avoid misleading "(null)" for %px

On Tue, Feb 06, 2018 at 05:57:17AM +1100, Kees Cook wrote: > On Mon, Feb 5, 2018 at 8:44 PM, Petr Mladek wrote: > > Hi, > > > > I add people who actively commented on adding %px modifier, > > see the thread starting at > >

Re: [PATCH] vsprintf: avoid misleading "(null)" for %px

On Tue, Feb 06, 2018 at 05:57:17AM +1100, Kees Cook wrote: > On Mon, Feb 5, 2018 at 8:44 PM, Petr Mladek wrote: > > Hi, > > > > I add people who actively commented on adding %px modifier, > > see the thread starting at > > https://lkml.kernel.org/r/1511921105-3647-5-git-send-email...@tobin.cc > >

[PATCH 4/4] net: amd-xgbe: fix comparison to bitshift when dealing with a mask

Due to a typo, the mask was destroyed by a comparison instead of a bit shift. Signed-off-by: Wolfram Sang --- Only build tested. To be applied individually per subsystem. drivers/net/ethernet/amd/xgbe/xgbe-drv.c | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH 3/4] v4l: dvb-frontends: stb0899: fix comparison to bitshift when dealing with a mask

Due to a typo, the mask was destroyed by a comparison instead of a bit shift. Signed-off-by: Wolfram Sang --- Only build tested. To be applied individually per subsystem. drivers/media/dvb-frontends/stb0899_reg.h | 8 1 file changed, 4 insertions(+),

[PATCH 4/4] net: amd-xgbe: fix comparison to bitshift when dealing with a mask

Due to a typo, the mask was destroyed by a comparison instead of a bit shift. Signed-off-by: Wolfram Sang --- Only build tested. To be applied individually per subsystem. drivers/net/ethernet/amd/xgbe/xgbe-drv.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 3/4] v4l: dvb-frontends: stb0899: fix comparison to bitshift when dealing with a mask

Due to a typo, the mask was destroyed by a comparison instead of a bit shift. Signed-off-by: Wolfram Sang --- Only build tested. To be applied individually per subsystem. drivers/media/dvb-frontends/stb0899_reg.h | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git

[PATCH 0/4] tree-wide: fix comparison to bitshift when dealing with a mask

In one Renesas driver, I found a typo which turned an intended bit shift ('<<') into a comparison ('<'). Because this is a subtle issue, I looked tree wide for similar patterns. This small patch series is the outcome. Buildbot and checkpatch are happy. Only compile-tested. To be applied

[PATCH 0/4] tree-wide: fix comparison to bitshift when dealing with a mask

In one Renesas driver, I found a typo which turned an intended bit shift ('<<') into a comparison ('<'). Because this is a subtle issue, I looked tree wide for similar patterns. This small patch series is the outcome. Buildbot and checkpatch are happy. Only compile-tested. To be applied

[PATCH 2/4] drm/exynos: fix comparison to bitshift when dealing with a mask

Due to a typo, the mask was destroyed by a comparison instead of a bit shift. Signed-off-by: Wolfram Sang --- Only build tested. To be applied individually per subsystem. drivers/gpu/drm/exynos/regs-fimc.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

[PATCH 2/4] drm/exynos: fix comparison to bitshift when dealing with a mask

Due to a typo, the mask was destroyed by a comparison instead of a bit shift. Signed-off-by: Wolfram Sang --- Only build tested. To be applied individually per subsystem. drivers/gpu/drm/exynos/regs-fimc.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 1/4] v4l: vsp1: fix mask creation for MULT_ALPHA_RATIO

Due to a typo, the mask was destroyed by a comparison instead of a bit shift. No regression since the mask has not been used yet. Signed-off-by: Wolfram Sang --- Only build tested. To be applied individually per subsystem.

[PATCH 1/4] v4l: vsp1: fix mask creation for MULT_ALPHA_RATIO

Due to a typo, the mask was destroyed by a comparison instead of a bit shift. No regression since the mask has not been used yet. Signed-off-by: Wolfram Sang --- Only build tested. To be applied individually per subsystem. drivers/media/platform/vsp1/vsp1_regs.h | 2 +- 1 file changed, 1

[PATCH v2 2/8] dvb-frontends: ves1820: use 64-bit arithmetic instead of 32-bit

Add suffix ULL to constant 10 in order to give the compiler complete information about the proper arithmetic to use. Notice that this constant is used in a context that expects an expression of type u64 (64 bits, unsigned). The expression fpxin = state->config->xin * 10 is currently being

[PATCH v2 2/8] dvb-frontends: ves1820: use 64-bit arithmetic instead of 32-bit

Add suffix ULL to constant 10 in order to give the compiler complete information about the proper arithmetic to use. Notice that this constant is used in a context that expects an expression of type u64 (64 bits, unsigned). The expression fpxin = state->config->xin * 10 is currently being

[PATCH v2 1/8] rtl2832: use 64-bit arithmetic instead of 32-bit in rtl2832_set_frontend

Add suffix ULL to constant 7 in order to give the compiler complete information about the proper arithmetic to use. Notice that this constant is used in a context that expects an expression of type u64 (64 bits, unsigned). The expression dev->pdata->clk * 7 is currently being evaluated using

[PATCH v2 1/8] rtl2832: use 64-bit arithmetic instead of 32-bit in rtl2832_set_frontend

Add suffix ULL to constant 7 in order to give the compiler complete information about the proper arithmetic to use. Notice that this constant is used in a context that expects an expression of type u64 (64 bits, unsigned). The expression dev->pdata->clk * 7 is currently being evaluated using

Re: [PATCH 1/3] x86/entry: Clear extra registers beyond syscall arguments for 64bit kernels

* Ingo Molnar wrote: > Btw., to underline these arguments, here's some statistical data about actual > register usage the x86 kernel. So this caveat was bothering me: > List of caveats/notes: > > Note #4: > The 'avg uses per fn' number is over-estimates the real uses per

Re: [PATCH 1/3] x86/entry: Clear extra registers beyond syscall arguments for 64bit kernels

* Ingo Molnar wrote: > Btw., to underline these arguments, here's some statistical data about actual > register usage the x86 kernel. So this caveat was bothering me: > List of caveats/notes: > > Note #4: > The 'avg uses per fn' number is over-estimates the real uses per function, >

[PATCH 1/1] KEYS: encrypted: fix buffer overread in valid_master_desc()

From: Eric Biggers commit 794b4bc292f5d31739d89c0202c54e7dc9bc3add upstream With the 'encrypted' key type it was possible for userspace to provide a data blob ending with a master key description shorter than expected, e.g. 'keyctl add encrypted desc "new x" @s'. When

[PATCH 1/1] KEYS: encrypted: fix buffer overread in valid_master_desc()

From: Eric Biggers commit 794b4bc292f5d31739d89c0202c54e7dc9bc3add upstream With the 'encrypted' key type it was possible for userspace to provide a data blob ending with a master key description shorter than expected, e.g. 'keyctl add encrypted desc "new x" @s'. When validating such a master

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