Re: [PATCH v4 1/3] locking: Document the semantics of spin_is_locked()

On 04/06/2018 12:47 PM, Andrea Parri wrote: > There appeared to be a certain, recurrent uncertainty concerning the > semantics of spin_is_locked(), likely a consequence of the fact that > this semantics remains undocumented or that it has been historically > linked to the (likewise unclear)

Re: [PATCH v4 1/3] locking: Document the semantics of spin_is_locked()

On 04/06/2018 12:47 PM, Andrea Parri wrote: > There appeared to be a certain, recurrent uncertainty concerning the > semantics of spin_is_locked(), likely a consequence of the fact that > this semantics remains undocumented or that it has been historically > linked to the (likewise unclear)

[PATCH 00/11] [v5] Use global pages with PTI

Changes from v4 * Fix compile error reported by Tom Lendacky * Avoid setting _PAGE_GLOBAL on non-present entries Changes from v3: * Fix whitespace issue noticed by willy * Clarify comments about X86_FEATURE_PGE checks * Clarify commit message around the necessity of _PAGE_GLOBAL filtering

[PATCH 00/11] [v5] Use global pages with PTI

Changes from v4 * Fix compile error reported by Tom Lendacky * Avoid setting _PAGE_GLOBAL on non-present entries Changes from v3: * Fix whitespace issue noticed by willy * Clarify comments about X86_FEATURE_PGE checks * Clarify commit message around the necessity of _PAGE_GLOBAL filtering

[PATCH 02/11] x86/mm: undo double _PAGE_PSE clearing

From: Dave Hansen When clearing _PAGE_PRESENT on a huge page, we need to be careful to also clear _PAGE_PSE, otherwise it might still get confused for a valid large page table entry. We do that near the spot where we *set* _PAGE_PSE. That's fine, but it's

[PATCH 02/11] x86/mm: undo double _PAGE_PSE clearing

From: Dave Hansen When clearing _PAGE_PRESENT on a huge page, we need to be careful to also clear _PAGE_PSE, otherwise it might still get confused for a valid large page table entry. We do that near the spot where we *set* _PAGE_PSE. That's fine, but it's unnecessary. pgprot_large_2_4k()

[PATCH 01/11] x86/mm: factor out pageattr _PAGE_GLOBAL setting

From: Dave Hansen The pageattr code has a pattern repeated where it sets _PAGE_GLOBAL for present PTEs but clears it for non-present PTEs. The intention is to keep _PAGE_GLOBAL from getting confused with _PAGE_PROTNONE since _PAGE_GLOBAL is for present PTEs and

[PATCH 04/11] x86/espfix: document use of _PAGE_GLOBAL

From: Dave Hansen The "normal" kernel page table creation mechanisms using PAGE_KERNEL_* page protections will never set _PAGE_GLOBAL with PTI. The few places in the kernel that always want _PAGE_GLOBAL must avoid using PAGE_KERNEL_*. Document that we want it here

[PATCH 04/11] x86/espfix: document use of _PAGE_GLOBAL

From: Dave Hansen The "normal" kernel page table creation mechanisms using PAGE_KERNEL_* page protections will never set _PAGE_GLOBAL with PTI. The few places in the kernel that always want _PAGE_GLOBAL must avoid using PAGE_KERNEL_*. Document that we want it here and its use is not

[PATCH 01/11] x86/mm: factor out pageattr _PAGE_GLOBAL setting

From: Dave Hansen The pageattr code has a pattern repeated where it sets _PAGE_GLOBAL for present PTEs but clears it for non-present PTEs. The intention is to keep _PAGE_GLOBAL from getting confused with _PAGE_PROTNONE since _PAGE_GLOBAL is for present PTEs and _PAGE_PROTNONE is for

[PATCH 07/11] x86/mm: comment _PAGE_GLOBAL mystery

From: Dave Hansen I was mystified as to where the _PAGE_GLOBAL in the kernel page tables for kernel text came from. I audited all the places I could find, but I missed one: head_64.S. The page tables that we create in here live for a long time, and they also have

[PATCH 07/11] x86/mm: comment _PAGE_GLOBAL mystery

From: Dave Hansen I was mystified as to where the _PAGE_GLOBAL in the kernel page tables for kernel text came from. I audited all the places I could find, but I missed one: head_64.S. The page tables that we create in here live for a long time, and they also have _PAGE_GLOBAL set, despite

[PATCH 06/11] x86/mm: remove extra filtering in pageattr code

From: Dave Hansen The pageattr code has a mode where it can set or clear PTE bits in existing PTEs, so the page protections of the *new* PTEs come from one of two places: 1. The set/clear masks: cpa->mask_clr / cpa->mask_set 2. The existing PTE We filter

[PATCH 06/11] x86/mm: remove extra filtering in pageattr code

From: Dave Hansen The pageattr code has a mode where it can set or clear PTE bits in existing PTEs, so the page protections of the *new* PTEs come from one of two places: 1. The set/clear masks: cpa->mask_clr / cpa->mask_set 2. The existing PTE We filter ->mask_set/clr for supported PTE bits

[PATCH 10/11] x86/pti: never implicitly clear _PAGE_GLOBAL for kernel image

From: Dave Hansen Summary: In current kernels, with PTI enabled, no pages are marked Global. This potentially increases TLB misses. But, the mechanism by which the Global bit is set and cleared is rather haphazard. This patch makes the process more explicit. In

[PATCH 10/11] x86/pti: never implicitly clear _PAGE_GLOBAL for kernel image

From: Dave Hansen Summary: In current kernels, with PTI enabled, no pages are marked Global. This potentially increases TLB misses. But, the mechanism by which the Global bit is set and cleared is rather haphazard. This patch makes the process more explicit. In the end, it leaves us with

Re: [PATCH v4 1/3] locking: Document the semantics of spin_is_locked()

On Fri, Apr 06, 2018 at 09:47:39PM +0200, Andrea Parri wrote: > There appeared to be a certain, recurrent uncertainty concerning the > semantics of spin_is_locked(), likely a consequence of the fact that > this semantics remains undocumented or that it has been historically > linked to the

[PATCH] openrisc: define mb() as its mandatory

Following Peter Z's patch ("asm-generic: Disallow no-op mb() for SMP systems") which makes mb() mandatory for SMP architectures we define it as l.msync. On OpenRISC this will flush the current cores write buffer and trigger remote cores to invalidate their caches of the written memory.

Re: [PATCH v4 1/3] locking: Document the semantics of spin_is_locked()

On Fri, Apr 06, 2018 at 09:47:39PM +0200, Andrea Parri wrote: > There appeared to be a certain, recurrent uncertainty concerning the > semantics of spin_is_locked(), likely a consequence of the fact that > this semantics remains undocumented or that it has been historically > linked to the

[PATCH] openrisc: define mb() as its mandatory

Following Peter Z's patch ("asm-generic: Disallow no-op mb() for SMP systems") which makes mb() mandatory for SMP architectures we define it as l.msync. On OpenRISC this will flush the current cores write buffer and trigger remote cores to invalidate their caches of the written memory.

[PATCH 09/11] x86/pti: enable global pages for shared areas

From: Dave Hansen The entry/exit text and cpu_entry_area are mapped into userspace and the kernel. But, they are not _PAGE_GLOBAL. This creates unnecessary TLB misses. Add the _PAGE_GLOBAL flag for these areas. Signed-off-by: Dave Hansen

[PATCH 05/11] x86/mm: do not auto-massage page protections

From: Dave Hansen A PTE is constructed from a physical address and a pgprotval_t. __PAGE_KERNEL, for instance, is a pgprot_t and must be converted into a pgprotval_t before it can be used to create a PTE. This is done implicitly within functions like pfn_pte() by

[PATCH 09/11] x86/pti: enable global pages for shared areas

From: Dave Hansen The entry/exit text and cpu_entry_area are mapped into userspace and the kernel. But, they are not _PAGE_GLOBAL. This creates unnecessary TLB misses. Add the _PAGE_GLOBAL flag for these areas. Signed-off-by: Dave Hansen Cc: Andrea Arcangeli Cc: Andy Lutomirski Cc: Linus

[PATCH 05/11] x86/mm: do not auto-massage page protections

From: Dave Hansen A PTE is constructed from a physical address and a pgprotval_t. __PAGE_KERNEL, for instance, is a pgprot_t and must be converted into a pgprotval_t before it can be used to create a PTE. This is done implicitly within functions like pfn_pte() by massage_pgprot(). However,

[PATCH 08/11] x86/mm: do not forbid _PAGE_RW before init for __ro_after_init

From: Dave Hansen __ro_after_init data gets stuck in the .rodata section. That's normally fine because the kernel itself manages the R/W properties. But, if we run __change_page_attr() on an area which is __ro_after_init, the .rodata checks will trigger and force

[PATCH 08/11] x86/mm: do not forbid _PAGE_RW before init for __ro_after_init

From: Dave Hansen __ro_after_init data gets stuck in the .rodata section. That's normally fine because the kernel itself manages the R/W properties. But, if we run __change_page_attr() on an area which is __ro_after_init, the .rodata checks will trigger and force the area to be immediately

[PATCH 11/11] x86/pti: leave kernel text global for !PCID

Note: This has changed since the last version. It now clones the kernel text PMDs at a much later point and also disables this functionality on AMD K8 processors. Details in the patch. -- I'm sticking this at the end of the series because it's a bit weird. It can be dropped and the rest of

[PATCH 11/11] x86/pti: leave kernel text global for !PCID

Note: This has changed since the last version. It now clones the kernel text PMDs at a much later point and also disables this functionality on AMD K8 processors. Details in the patch. -- I'm sticking this at the end of the series because it's a bit weird. It can be dropped and the rest of

[PATCH 03/11] x86/mm: introduce "default" kernel PTE mask

From: Dave Hansen The __PAGE_KERNEL_* page permissions are "raw". They contain bits that may or may not be supported on the current processor. They need to be filtered by a mask (currently __supported_pte_mask) to turn them into a value that we can actually set in

[PATCH 03/11] x86/mm: introduce "default" kernel PTE mask

From: Dave Hansen The __PAGE_KERNEL_* page permissions are "raw". They contain bits that may or may not be supported on the current processor. They need to be filtered by a mask (currently __supported_pte_mask) to turn them into a value that we can actually set in a PTE. These

Re: [PATCH 02/10] locking/qspinlock: Remove unbounded cmpxchg loop from locking slowpath

On 04/05/2018 12:58 PM, Will Deacon wrote: > The qspinlock locking slowpath utilises a "pending" bit as a simple form > of an embedded test-and-set lock that can avoid the overhead of explicit > queuing in cases where the lock is held but uncontended. This bit is > managed using a cmpxchg loop

Re: [PATCH 02/10] locking/qspinlock: Remove unbounded cmpxchg loop from locking slowpath

On 04/05/2018 12:58 PM, Will Deacon wrote: > The qspinlock locking slowpath utilises a "pending" bit as a simple form > of an embedded test-and-set lock that can avoid the overhead of explicit > queuing in cases where the lock is held but uncontended. This bit is > managed using a cmpxchg loop

[PATCH] staging: pi433: break long lines in pi433_if.c

Breaks long lines in pi433_if.c, fixing checkpatch.pl warnings: "WARNING: line over 80 characters" Signed-off-by: Simon Sandström --- drivers/staging/pi433/pi433_if.c | 19 ++- 1 file changed, 14 insertions(+), 5 deletions(-) diff --git

[PATCH] staging: pi433: break long lines in pi433_if.c

Breaks long lines in pi433_if.c, fixing checkpatch.pl warnings: "WARNING: line over 80 characters" Signed-off-by: Simon Sandström --- drivers/staging/pi433/pi433_if.c | 19 ++- 1 file changed, 14 insertions(+), 5 deletions(-) diff --git a/drivers/staging/pi433/pi433_if.c

Re: [PATCH 2/2] clk: spear: fix WDT clock definition on SPEAr600

Quoting Quentin Schulz (2018-04-06 00:50:45) > There is no SPEAr600 device named "wdt". Instead, the description of the > WDT (watchdog) was recently added to the Device Tree, and the device > name is "fc88.wdt", so we should associate the WDT fixed rate clock > to this device name. > >

Re: [PATCH 2/2] clk: spear: fix WDT clock definition on SPEAr600

Quoting Quentin Schulz (2018-04-06 00:50:45) > There is no SPEAr600 device named "wdt". Instead, the description of the > WDT (watchdog) was recently added to the Device Tree, and the device > name is "fc88.wdt", so we should associate the WDT fixed rate clock > to this device name. > >

Re: [PATCH 1/6] clk: stm32mp1: add missing static

Quoting gabriel.fernan...@st.com (2018-04-05 23:39:28) > From: Gabriel Fernandez > > Add missing static for const parent names and clock ops. > > Signed-off-by: Gabriel Fernandez > --- Applied to clk-next

Re: [PATCH 1/6] clk: stm32mp1: add missing static

Quoting gabriel.fernan...@st.com (2018-04-05 23:39:28) > From: Gabriel Fernandez > > Add missing static for const parent names and clock ops. > > Signed-off-by: Gabriel Fernandez > --- Applied to clk-next

Re: [PATCH 4/6] clk: stm32mp1: add missing tzc2 clock

Quoting gabriel.fernan...@st.com (2018-04-05 23:39:31) > From: Gabriel Fernandez > > This patch adds tzc2 clock and rename tzc clock into tzc1 > > Signed-off-by: Gabriel Fernandez > --- Applied to clk-next

Re: [PATCH 2/6] clk: stm32mp1: remove unused dfsdm_src[] const

Quoting gabriel.fernan...@st.com (2018-04-05 23:39:29) > From: Gabriel Fernandez > > This patch remove unused constant. > > Signed-off-by: Gabriel Fernandez > --- Applied to clk-next

Re: [PATCH 4/6] clk: stm32mp1: add missing tzc2 clock

Quoting gabriel.fernan...@st.com (2018-04-05 23:39:31) > From: Gabriel Fernandez > > This patch adds tzc2 clock and rename tzc clock into tzc1 > > Signed-off-by: Gabriel Fernandez > --- Applied to clk-next

Re: [PATCH 2/6] clk: stm32mp1: remove unused dfsdm_src[] const

Quoting gabriel.fernan...@st.com (2018-04-05 23:39:29) > From: Gabriel Fernandez > > This patch remove unused constant. > > Signed-off-by: Gabriel Fernandez > --- Applied to clk-next

Re: [PATCH 3/6] clk: stm32mp1: fix SAI3 & SAI4 clocks

Quoting gabriel.fernan...@st.com (2018-04-05 23:39:30) > From: Gabriel Fernandez > > fix bad copy / paste. > SAI3 & SAI4 used gate of SAI2 instead SAI3 & SAI4 > > Signed-off-by: Gabriel Fernandez > --- Applied to clk-next

Re: [PATCH 6/6] clk: stm32mp1: remove ck_apb_dbg clock

Quoting gabriel.fernan...@st.com (2018-04-05 23:39:33) > From: Gabriel Fernandez > > It's recommended to use only clk_sys_dbg clock instead to activate > debug IP. > > Signed-off-by: Gabriel Fernandez > --- Applied to clk-next

Re: [PATCH 3/6] clk: stm32mp1: fix SAI3 & SAI4 clocks

Quoting gabriel.fernan...@st.com (2018-04-05 23:39:30) > From: Gabriel Fernandez > > fix bad copy / paste. > SAI3 & SAI4 used gate of SAI2 instead SAI3 & SAI4 > > Signed-off-by: Gabriel Fernandez > --- Applied to clk-next

Re: [PATCH 6/6] clk: stm32mp1: remove ck_apb_dbg clock

Quoting gabriel.fernan...@st.com (2018-04-05 23:39:33) > From: Gabriel Fernandez > > It's recommended to use only clk_sys_dbg clock instead to activate > debug IP. > > Signed-off-by: Gabriel Fernandez > --- Applied to clk-next

Re: [PATCH v2] powerpc, pkey: make protection key 0 less special

Ram Pai writes: > On Wed, Apr 04, 2018 at 06:41:01PM -0300, Thiago Jung Bauermann wrote: >> >> Hello Ram, >> >> Ram Pai writes: >> >> > Applications need the ability to associate an address-range with some >> > key and latter revert to its initial

Re: [PATCH v2] powerpc, pkey: make protection key 0 less special

Ram Pai writes: > On Wed, Apr 04, 2018 at 06:41:01PM -0300, Thiago Jung Bauermann wrote: >> >> Hello Ram, >> >> Ram Pai writes: >> >> > Applications need the ability to associate an address-range with some >> > key and latter revert to its initial default key. Pkey-0 comes close to >> >

Re: [PATCH 5/6] clk: stm32mp1: set stgen_k clock as critical

Quoting gabriel.fernan...@st.com (2018-04-05 23:39:32) > From: Gabriel Fernandez > > stgen_k should be declared as critical to avoid blocking console > when ck_hsi is not used. > > Signed-off-by: Gabriel Fernandez > --- Applied to clk-next

Re: [PATCH 5/6] clk: stm32mp1: set stgen_k clock as critical

Quoting gabriel.fernan...@st.com (2018-04-05 23:39:32) > From: Gabriel Fernandez > > stgen_k should be declared as critical to avoid blocking console > when ck_hsi is not used. > > Signed-off-by: Gabriel Fernandez > --- Applied to clk-next

Re: [PATCH v5 8/8] clk: davinci: kill davinci_clk_reset_assert/deassert()

Quoting Bartosz Golaszewski (2018-03-30 08:28:56) > From: Bartosz Golaszewski > > This code is no longer used. Remove it. > > Signed-off-by: Bartosz Golaszewski > Reviewed-by: David Lechner > --- I'll try to

Re: [PATCH v5 8/8] clk: davinci: kill davinci_clk_reset_assert/deassert()

Quoting Bartosz Golaszewski (2018-03-30 08:28:56) > From: Bartosz Golaszewski > > This code is no longer used. Remove it. > > Signed-off-by: Bartosz Golaszewski > Reviewed-by: David Lechner > --- I'll try to remember, but please send this again if we need to apply it to the clk tree for

Some minor fixes for perf user tools

This patchkit fixes some random minor issues in the perf user tools -Andi

Some minor fixes for perf user tools

This patchkit fixes some random minor issues in the perf user tools -Andi

[PATCH 1/4] perf, tools, mem: Allow all record/report options

From: Andi Kleen For perf mem report / perf mem record, pass all unknown options through to the underlying report/record commands. This makes things like perf mem record -a sleep 1 work. Matches how c2c and other tools work. Signed-off-by: Andi Kleen

[PATCH 1/4] perf, tools, mem: Allow all record/report options

From: Andi Kleen For perf mem report / perf mem record, pass all unknown options through to the underlying report/record commands. This makes things like perf mem record -a sleep 1 work. Matches how c2c and other tools work. Signed-off-by: Andi Kleen ---

[PATCH 3/4] perf, tools, record: Remove misleading error suggestion

From: Andi Kleen When perf record encounters an error setting up an event it suggests to enable CONFIG_PERF_EVENTS. This is misleading because: - Usually it is enabled (it is really hard to disable on x86) - The problem is usually somewhere else, e.g. the CPU is not

[PATCH 3/4] perf, tools, record: Remove misleading error suggestion

From: Andi Kleen When perf record encounters an error setting up an event it suggests to enable CONFIG_PERF_EVENTS. This is misleading because: - Usually it is enabled (it is really hard to disable on x86) - The problem is usually somewhere else, e.g. the CPU is not supported or an invalid

Re: [PATCH v5 3/8] clk: davinci: add a reset lookup table for psc0

Quoting Bartosz Golaszewski (2018-03-30 08:28:51) > From: Bartosz Golaszewski > > In order to be able to use the reset framework in legacy boot mode as > well, add the reset lookup table to the psc driver for da850 variant. > > Signed-off-by: Bartosz Golaszewski

Re: [PATCH v5 3/8] clk: davinci: add a reset lookup table for psc0

Quoting Bartosz Golaszewski (2018-03-30 08:28:51) > From: Bartosz Golaszewski > > In order to be able to use the reset framework in legacy boot mode as > well, add the reset lookup table to the psc driver for da850 variant. > > Signed-off-by: Bartosz Golaszewski > --- Applied to clk-next

[PATCH 2/4] perf, tools: Clarify browser help

From: Andi Kleen Clarify in the browser help that ESC in tui mode may go back to the previous screen instead of just exiting (was not clear to me) Signed-off-by: Andi Kleen --- tools/perf/ui/browsers/hists.c | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH 2/4] perf, tools: Clarify browser help

From: Andi Kleen Clarify in the browser help that ESC in tui mode may go back to the previous screen instead of just exiting (was not clear to me) Signed-off-by: Andi Kleen --- tools/perf/ui/browsers/hists.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH 4/4] perf, tools, record: Remove suggestion to enable APIC

From: Andi Kleen perf record suggests to enable the APIC on errors. APIC is practically always used today and the problem is usually somewhere else. Just remove the outdated suggestion. Signed-off-by: Andi Kleen --- tools/perf/util/evsel.c | 3 +--

[PATCH 4/4] perf, tools, record: Remove suggestion to enable APIC

From: Andi Kleen perf record suggests to enable the APIC on errors. APIC is practically always used today and the problem is usually somewhere else. Just remove the outdated suggestion. Signed-off-by: Andi Kleen --- tools/perf/util/evsel.c | 3 +-- 1 file changed, 1 insertion(+), 2

[PATCH] staging: pi433: break long lines

Breaks long lines in rf69.h, fixing checkpatch.pl warnings: "WARNING: line over 80 characters" Signed-off-by: Simon Sandström --- drivers/staging/pi433/rf69.h | 28 +++- 1 file changed, 19 insertions(+), 9 deletions(-) diff --git

[PATCH] staging: pi433: break long lines

Breaks long lines in rf69.h, fixing checkpatch.pl warnings: "WARNING: line over 80 characters" Signed-off-by: Simon Sandström --- drivers/staging/pi433/rf69.h | 28 +++- 1 file changed, 19 insertions(+), 9 deletions(-) diff --git a/drivers/staging/pi433/rf69.h

Re: [PATCH] clk: qcom: Add MSM8998 Global Clock Control (GCC) driver

Quoting Bjorn Andersson (2018-03-27 08:25:18) > From: Joonwoo Park > > Add support for the global clock controller found on MSM8998 > based devices. This should allow most non-multimedia device > drivers to probe and control their clocks. > > Signed-off-by: Joonwoo Park

Re: [PATCH] clk: qcom: Add MSM8998 Global Clock Control (GCC) driver

Quoting Bjorn Andersson (2018-03-27 08:25:18) > From: Joonwoo Park > > Add support for the global clock controller found on MSM8998 > based devices. This should allow most non-multimedia device > drivers to probe and control their clocks. > > Signed-off-by: Joonwoo Park > Signed-off-by: Imran

Re: [PATCH] i8042: Enable MUX on Sony VAIO VGN-CS series to fix touchpad

On Fri, Apr 06, 2018 at 10:16:19PM +0200, Ondrej Zary wrote: >On Friday 06 April 2018 22:05:59 Sasha Levin wrote: >> Hi, >> >> [This is an automated email] >> >> This commit has been processed by the -stable helper bot and determined >> to be a high probability candidate for -stable trees. (score:

Re: [PATCH] i8042: Enable MUX on Sony VAIO VGN-CS series to fix touchpad

On Fri, Apr 06, 2018 at 10:16:19PM +0200, Ondrej Zary wrote: >On Friday 06 April 2018 22:05:59 Sasha Levin wrote: >> Hi, >> >> [This is an automated email] >> >> This commit has been processed by the -stable helper bot and determined >> to be a high probability candidate for -stable trees. (score:

Re: [PATCH 4.15 00/72] 4.15.16-stable review

On Fri, Apr 06, 2018 at 03:23:35PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.15.16 release. > There are 72 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 4.15 00/72] 4.15.16-stable review

On Fri, Apr 06, 2018 at 03:23:35PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.15.16 release. > There are 72 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] i8042: Enable MUX on Sony VAIO VGN-CS series to fix touchpad

On Friday 06 April 2018 22:05:59 Sasha Levin wrote: > Hi, > > [This is an automated email] > > This commit has been processed by the -stable helper bot and determined > to be a high probability candidate for -stable trees. (score: 24.5527) > > The bot has tested the following trees: v4.16,

Re: [PATCH] i8042: Enable MUX on Sony VAIO VGN-CS series to fix touchpad

On Friday 06 April 2018 22:05:59 Sasha Levin wrote: > Hi, > > [This is an automated email] > > This commit has been processed by the -stable helper bot and determined > to be a high probability candidate for -stable trees. (score: 24.5527) > > The bot has tested the following trees: v4.16,

[PATCH] backing: silence compiler warning using __printf

__printf marker was added in commit d2cc4dde9206 ("bdi_register: add __printf verification, fix arg mismatch") for function `bdi_register` since it is useful to verify format and arguments. Apply equivalent gcc attribute to `bdi_register_va`. Remove warning triggered with W=1:

[PATCH] backing: silence compiler warning using __printf

__printf marker was added in commit d2cc4dde9206 ("bdi_register: add __printf verification, fix arg mismatch") for function `bdi_register` since it is useful to verify format and arguments. Apply equivalent gcc attribute to `bdi_register_va`. Remove warning triggered with W=1:

[PATCH] powerpc: add __printf verification to prom_printf

__printf is useful to verify format and arguments. Fix arg mismatch reported by gcc, remove the following warnings (with W=1): arch/powerpc/kernel/prom_init.c:1467:31: error: format ‘%x’ expects argument of type ‘unsigned int’, but argument 2 has type ‘long unsigned int’ [-Werror=format=]

[PATCH] powerpc: add __printf verification to prom_printf

__printf is useful to verify format and arguments. Fix arg mismatch reported by gcc, remove the following warnings (with W=1): arch/powerpc/kernel/prom_init.c:1467:31: error: format ‘%x’ expects argument of type ‘unsigned int’, but argument 2 has type ‘long unsigned int’ [-Werror=format=]

Re: [PATCH v2 0/3] mm/get_user_pages_fast fixes, cleanups

On Fri, 6 Apr 2018 00:03:48 +0300 "Michael S. Tsirkin" wrote: > Turns out get_user_pages_fast and __get_user_pages_fast return different > values on error when given a single page: __get_user_pages_fast returns > 0. get_user_pages_fast returns either 0 or an error. > > Callers

Re: [PATCH v2 0/3] mm/get_user_pages_fast fixes, cleanups

On Fri, 6 Apr 2018 00:03:48 +0300 "Michael S. Tsirkin" wrote: > Turns out get_user_pages_fast and __get_user_pages_fast return different > values on error when given a single page: __get_user_pages_fast returns > 0. get_user_pages_fast returns either 0 or an error. > > Callers of

Re: [PATCH 4.14 00/67] 4.14.33-stable review

On Fri, Apr 06, 2018 at 03:23:30PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.14.33 release. > There are 67 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 v3 4/6] clk: meson-axg: Add AO Clock and Reset controller driver

Quoting Yixun Lan (2018-03-27 19:50:48) > + [CLKID_AO_SAR_ADC_CLK] = _saradc_gate, > +}; > + > +static struct clk_hw_onecell_data axg_aoclk_onecell_data = { const? > + .hws = { > + [CLKID_AO_REMOTE] = _ao.hw, > + [CLKID_AO_I2C_MASTER] =

Re: [PATCH 4.14 00/67] 4.14.33-stable review

On Fri, Apr 06, 2018 at 03:23:30PM +0200, Greg Kroah-Hartman wrote: > This is the start of the stable review cycle for the 4.14.33 release. > There are 67 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 v3 4/6] clk: meson-axg: Add AO Clock and Reset controller driver

Quoting Yixun Lan (2018-03-27 19:50:48) > + [CLKID_AO_SAR_ADC_CLK] = _saradc_gate, > +}; > + > +static struct clk_hw_onecell_data axg_aoclk_onecell_data = { const? > + .hws = { > + [CLKID_AO_REMOTE] = _ao.hw, > + [CLKID_AO_I2C_MASTER] =

Re: [PATCH] i8042: Enable MUX on Sony VAIO VGN-CS series to fix touchpad

Hi, [This is an automated email] This commit has been processed by the -stable helper bot and determined to be a high probability candidate for -stable trees. (score: 24.5527) The bot has tested the following trees: v4.16, v4.15.15, v4.14.32, v4.9.92, v4.4.126. v4.16: Build OK! v4.15.15:

Re: [PATCH] i8042: Enable MUX on Sony VAIO VGN-CS series to fix touchpad

Hi, [This is an automated email] This commit has been processed by the -stable helper bot and determined to be a high probability candidate for -stable trees. (score: 24.5527) The bot has tested the following trees: v4.16, v4.15.15, v4.14.32, v4.9.92, v4.4.126. v4.16: Build OK! v4.15.15:

Re: [PATCH] blk-mq: Directly schedule q->timeout_work when aborting a request

Hi, [This is an automated email] This commit has been processed because it contains a "Fixes:" tag, fixing commit: 358f70da49d7 blk-mq: make blk_abort_request() trigger timeout path. The bot has also determined it's probably a bug fixing patch. (score: 98.7780) The bot has tested the

Re: [PATCH] blk-mq: Directly schedule q->timeout_work when aborting a request

Hi, [This is an automated email] This commit has been processed because it contains a "Fixes:" tag, fixing commit: 358f70da49d7 blk-mq: make blk_abort_request() trigger timeout path. The bot has also determined it's probably a bug fixing patch. (score: 98.7780) The bot has tested the

Re: [PATCH] drm/sti: Depend on OF rather than selecting it

Hi, [This is an automated email] This commit has been processed because it contains a "Fixes:" tag, fixing commit: cc6b741c6f63 drm: sti: remove useless fields from vtg structure. The bot has also determined it's probably a bug fixing patch. (score: 96.6729) The bot has tested the following

Re: [PATCH] drm/sti: Depend on OF rather than selecting it

Hi, [This is an automated email] This commit has been processed because it contains a "Fixes:" tag, fixing commit: cc6b741c6f63 drm: sti: remove useless fields from vtg structure. The bot has also determined it's probably a bug fixing patch. (score: 96.6729) The bot has tested the following

Re: [PATCH] bitmap: fix memset optimization on big-endian systems

Hi, [This is an automated email] This commit has been processed because it contains a "Fixes:" tag, fixing commit: 2a98dc028f91 include/linux/bitmap.h: turn bitmap_set and bitmap_clear into memset when possible. The bot has also determined it's probably a bug fixing patch. (score: 65.4067)

Re: [PATCH] bitmap: fix memset optimization on big-endian systems

Hi, [This is an automated email] This commit has been processed because it contains a "Fixes:" tag, fixing commit: 2a98dc028f91 include/linux/bitmap.h: turn bitmap_set and bitmap_clear into memset when possible. The bot has also determined it's probably a bug fixing patch. (score: 65.4067)

[GIT PULL] fscache: Fixes, traces and development

branch 'userns-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace (2018-04-03 19:15:32 -0700) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git tags/fscache-next-20180406 for you to fetch changes up

Re: [Question] patch posting process

Hi Willy, Thank you for your opinion, it's very helpful. WBR, Vadim On Fri, Apr 06, 2018 at 09:21:46PM +0200, Willy Tarreau wrote: > Hi Vadim, > > On Fri, Apr 06, 2018 at 11:29:16AM -0700, Vadim Lomovtsev wrote: > > Hi all, > > > > I bring my Apologise for wasting your time, but .. > >

[GIT PULL] fscache: Fixes, traces and development

branch 'userns-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace (2018-04-03 19:15:32 -0700) are available in the Git repository at: git://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git tags/fscache-next-20180406 for you to fetch changes up

Re: [Question] patch posting process

Hi Willy, Thank you for your opinion, it's very helpful. WBR, Vadim On Fri, Apr 06, 2018 at 09:21:46PM +0200, Willy Tarreau wrote: > Hi Vadim, > > On Fri, Apr 06, 2018 at 11:29:16AM -0700, Vadim Lomovtsev wrote: > > Hi all, > > > > I bring my Apologise for wasting your time, but .. > >

Re: [PATCH resend] mm/page_alloc: fix comment is __get_free_pages

On Fri, 6 Apr 2018 12:02:36 +0200 Michal Hocko wrote: > On Wed 29-11-17 17:04:46, Michal Hocko wrote: > [...] > > From 000bb422fe07adbfa8cd8ed953b18f48647a45d6 Mon Sep 17 00:00:00 2001 > > From: Michal Hocko > > Date: Wed, 29 Nov 2017 17:02:33 +0100 > >

Re: [PATCH resend] mm/page_alloc: fix comment is __get_free_pages

On Fri, 6 Apr 2018 12:02:36 +0200 Michal Hocko wrote: > On Wed 29-11-17 17:04:46, Michal Hocko wrote: > [...] > > From 000bb422fe07adbfa8cd8ed953b18f48647a45d6 Mon Sep 17 00:00:00 2001 > > From: Michal Hocko > > Date: Wed, 29 Nov 2017 17:02:33 +0100 > > Subject: [PATCH] mm: drop VM_BUG_ON from

[PATCH v4] net: thunderx: rework mac addresses list to u64 array

From: Vadim Lomovtsev It is too expensive to pass u64 values via linked list, instead allocate array for them by overall number of mac addresses from netdev. This eventually removes multiple kmalloc() calls, aviod memory fragmentation and allow to put single null

Re: Problem with commit 31e77c93e432 "sched/fair: Update blocked load when newly idle"

Am 06.04.2018 um 18:03 schrieb Vincent Guittot: > Hi Heiner, > > On 30 March 2018 at 10:37, Heiner Kallweit wrote: >> Am 30.03.2018 um 08:50 schrieb Vincent Guittot: >>> On 29 March 2018 at 19:40, Heiner Kallweit wrote: Am 29.03.2018 um 09:41

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