[PATCH 60/64] drivers/xen: use mm locking wrappers

From: Davidlohr Bueso All callers use mmap_sem within the same function context. No change in semantics. Signed-off-by: Davidlohr Bueso --- drivers/xen/gntdev.c | 5 +++-- drivers/xen/privcmd.c | 12 +++- 2 files changed, 10 insertions(+), 7

[PATCH 54/64] arch/arm: use mm locking wrappers

From: Davidlohr Bueso This becomes quite straightforward with the mmrange in place. For those mmap_sem users that need mmrange, we simply add it to the function as the mmap_sem usage is in the same context. Signed-off-by: Davidlohr Bueso --- arch/arm/kernel/process.c | 5 +++--

[PATCH 60/64] drivers/xen: use mm locking wrappers

From: Davidlohr Bueso All callers use mmap_sem within the same function context. No change in semantics. Signed-off-by: Davidlohr Bueso --- drivers/xen/gntdev.c | 5 +++-- drivers/xen/privcmd.c | 12 +++- 2 files changed, 10 insertions(+), 7 deletions(-) diff --git

[PATCH 35/64] arch/ia64: use mm locking wrappers

From: Davidlohr Bueso This becomes quite straightforward with the mmrange in place. Signed-off-by: Davidlohr Bueso --- arch/ia64/kernel/perfmon.c | 10 +- arch/ia64/mm/fault.c | 8 arch/ia64/mm/init.c| 13 +++-- 3 files changed, 16 insertions(+), 15

[PATCH 48/64] arch/tile: use mm locking wrappers

From: Davidlohr Bueso * THIS IS A HACK * Breaks arch/um/. See comment in fix_range_common(). Signed-off-by: Davidlohr Bueso --- arch/um/include/asm/mmu_context.h | 5 +++-- arch/um/kernel/tlb.c | 12 +++- arch/um/kernel/trap.c

[PATCH 48/64] arch/tile: use mm locking wrappers

From: Davidlohr Bueso * THIS IS A HACK * Breaks arch/um/. See comment in fix_range_common(). Signed-off-by: Davidlohr Bueso --- arch/um/include/asm/mmu_context.h | 5 +++-- arch/um/kernel/tlb.c | 12 +++- arch/um/kernel/trap.c | 6 +++--- 3 files changed,

[PATCH 53/64] arch/nios2: use mm locking wrappers

From: Davidlohr Bueso This becomes quite straightforward with the mmrange in place. Signed-off-by: Davidlohr Bueso --- arch/nios2/mm/fault.c | 12 ++-- arch/nios2/mm/init.c | 5 +++-- 2 files changed, 9 insertions(+), 8 deletions(-) diff --git

[PATCH 45/64] arch/m32r: use mm locking wrappers

From: Davidlohr Bueso This becomes quite straightforward with the mmrange in place. Signed-off-by: Davidlohr Bueso --- arch/m32r/mm/fault.c | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/arch/m32r/mm/fault.c

[PATCH 52/64] arch/openrisc: use mm locking wrappers

From: Davidlohr Bueso This becomes quite straightforward with the mmrange in place. Signed-off-by: Davidlohr Bueso --- arch/openrisc/kernel/dma.c | 6 -- arch/openrisc/mm/fault.c | 10 +- 2 files changed, 9 insertions(+), 7 deletions(-) diff

[PATCH 53/64] arch/nios2: use mm locking wrappers

From: Davidlohr Bueso This becomes quite straightforward with the mmrange in place. Signed-off-by: Davidlohr Bueso --- arch/nios2/mm/fault.c | 12 ++-- arch/nios2/mm/init.c | 5 +++-- 2 files changed, 9 insertions(+), 8 deletions(-) diff --git a/arch/nios2/mm/fault.c

[PATCH 45/64] arch/m32r: use mm locking wrappers

From: Davidlohr Bueso This becomes quite straightforward with the mmrange in place. Signed-off-by: Davidlohr Bueso --- arch/m32r/mm/fault.c | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/arch/m32r/mm/fault.c b/arch/m32r/mm/fault.c index

[PATCH 52/64] arch/openrisc: use mm locking wrappers

From: Davidlohr Bueso This becomes quite straightforward with the mmrange in place. Signed-off-by: Davidlohr Bueso --- arch/openrisc/kernel/dma.c | 6 -- arch/openrisc/mm/fault.c | 10 +- 2 files changed, 9 insertions(+), 7 deletions(-) diff --git a/arch/openrisc/kernel/dma.c

[PATCH 50/64] arch/unicore32: use mm locking wrappers

From: Davidlohr Bueso This becomes quite straightforward with the mmrange in place. Signed-off-by: Davidlohr Bueso --- arch/unicore32/mm/fault.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/arch/unicore32/mm/fault.c

[PATCH 59/64] drivers/iommu: use mm locking helpers

From: Davidlohr Bueso This becomes quite straightforward with the mmrange in place. Signed-off-by: Davidlohr Bueso --- drivers/iommu/amd_iommu_v2.c | 4 ++-- drivers/iommu/intel-svm.c| 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git

[PATCH 50/64] arch/unicore32: use mm locking wrappers

From: Davidlohr Bueso This becomes quite straightforward with the mmrange in place. Signed-off-by: Davidlohr Bueso --- arch/unicore32/mm/fault.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/arch/unicore32/mm/fault.c b/arch/unicore32/mm/fault.c index

[PATCH 59/64] drivers/iommu: use mm locking helpers

From: Davidlohr Bueso This becomes quite straightforward with the mmrange in place. Signed-off-by: Davidlohr Bueso --- drivers/iommu/amd_iommu_v2.c | 4 ++-- drivers/iommu/intel-svm.c| 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/iommu/amd_iommu_v2.c

[PATCH 61/64] staging/lustre: use generic range lock

From: Davidlohr Bueso This replaces the in-house version. It also adds the mmrange and makes use of mm locking wrappers. Signed-off-by: Davidlohr Bueso --- drivers/staging/lustre/lustre/llite/Makefile | 2 +-

[PATCH 56/64] drivers/android: use mm locking wrappers

From: Davidlohr Bueso The binder_alloc_free_page() shrinker callback can call zap_page_range(), which needs mmap_sem. Use mm locking wrappers, no change in semantics. Signed-off-by: Davidlohr Bueso --- drivers/android/binder_alloc.c | 12 +++- 1 file

[PATCH 61/64] staging/lustre: use generic range lock

From: Davidlohr Bueso This replaces the in-house version. It also adds the mmrange and makes use of mm locking wrappers. Signed-off-by: Davidlohr Bueso --- drivers/staging/lustre/lustre/llite/Makefile | 2 +- drivers/staging/lustre/lustre/llite/file.c | 16 +-

[PATCH 56/64] drivers/android: use mm locking wrappers

From: Davidlohr Bueso The binder_alloc_free_page() shrinker callback can call zap_page_range(), which needs mmap_sem. Use mm locking wrappers, no change in semantics. Signed-off-by: Davidlohr Bueso --- drivers/android/binder_alloc.c | 12 +++- 1 file changed, 7 insertions(+), 5

Re: [PATCH 1/2] /proc/kcore: Fix SMAP violation when dumping vsyscall user page

Hi Jiri, The maintainers are too busy to review this patchset. You are the author of the commit df04abfd181a. Please help to review this patchset. Thanks, Jia On 2018/1/30 下午2:42, Jia Zhang wrote: > The commit df04abfd181a > ("fs/proc/kcore.c: Add bounce buffer for ktext data") introduces a >

Re: [PATCH 1/2] /proc/kcore: Fix SMAP violation when dumping vsyscall user page

Hi Jiri, The maintainers are too busy to review this patchset. You are the author of the commit df04abfd181a. Please help to review this patchset. Thanks, Jia On 2018/1/30 下午2:42, Jia Zhang wrote: > The commit df04abfd181a > ("fs/proc/kcore.c: Add bounce buffer for ktext data") introduces a >

Re: [PATCH 07/20] riscv: Remove ARCH_WANT_OPTIONAL_GPIOLIB select

On Mon, Feb 5, 2018 at 2:21 AM, Ulf Magnusson wrote: > The ARCH_WANT_OPTIONAL_GPIOLIB symbol was removed in commit 65053e1a7743 > ("gpio: delete ARCH_[WANTS_OPTIONAL|REQUIRE]_GPIOLIB"). GPIOLIB should > just be selected explicitly if needed. > > Remove the

Re: [PATCH 07/20] riscv: Remove ARCH_WANT_OPTIONAL_GPIOLIB select

On Mon, Feb 5, 2018 at 2:21 AM, Ulf Magnusson wrote: > The ARCH_WANT_OPTIONAL_GPIOLIB symbol was removed in commit 65053e1a7743 > ("gpio: delete ARCH_[WANTS_OPTIONAL|REQUIRE]_GPIOLIB"). GPIOLIB should > just be selected explicitly if needed. > > Remove the ARCH_WANT_OPTIONAL_GPIOLIB select from

[PATCH 57/64] drivers/gpu: use mm locking wrappers

From: Davidlohr Bueso This becomes quite straightforward with the mmrange in place. Those mmap_sem users that don't know about mmrange are updated trivially as the sem is used in the same context of the caller. Signed-off-by: Davidlohr Bueso ---

[PATCH 55/64] arch/riscv: use mm locking wrappers

From: Davidlohr Bueso This becomes quite straightforward with the mmrange in place. Signed-off-by: Davidlohr Bueso --- arch/riscv/kernel/vdso.c | 5 +++-- arch/riscv/mm/fault.c| 10 +- 2 files changed, 8 insertions(+), 7 deletions(-) diff --git

[PATCH 57/64] drivers/gpu: use mm locking wrappers

From: Davidlohr Bueso This becomes quite straightforward with the mmrange in place. Those mmap_sem users that don't know about mmrange are updated trivially as the sem is used in the same context of the caller. Signed-off-by: Davidlohr Bueso --- drivers/gpu/drm/amd/amdgpu/amdgpu_mn.c | 7

[PATCH 55/64] arch/riscv: use mm locking wrappers

From: Davidlohr Bueso This becomes quite straightforward with the mmrange in place. Signed-off-by: Davidlohr Bueso --- arch/riscv/kernel/vdso.c | 5 +++-- arch/riscv/mm/fault.c| 10 +- 2 files changed, 8 insertions(+), 7 deletions(-) diff --git a/arch/riscv/kernel/vdso.c

[PATCH 58/64] drivers/infiniband: use mm locking wrappers

From: Davidlohr Bueso This becomes quite straightforward with the mmrange in place. Signed-off-by: Davidlohr Bueso --- drivers/infiniband/core/umem.c | 16 +--- drivers/infiniband/core/umem_odp.c | 11 ++-

[PATCH 58/64] drivers/infiniband: use mm locking wrappers

From: Davidlohr Bueso This becomes quite straightforward with the mmrange in place. Signed-off-by: Davidlohr Bueso --- drivers/infiniband/core/umem.c | 16 +--- drivers/infiniband/core/umem_odp.c | 11 ++- drivers/infiniband/hw/hfi1/user_pages.c| 15

[PATCH 63/64] mm/mmap: hack drop down_write_nest_lock()

From: Davidlohr Bueso * THIS IS A HACK * Directly call down_write() on i_mmap_rwsem (such that we don't have to convert it to a range lock) Signed-off-by: Davidlohr Bueso --- mm/mmap.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

[PATCH 63/64] mm/mmap: hack drop down_write_nest_lock()

From: Davidlohr Bueso * THIS IS A HACK * Directly call down_write() on i_mmap_rwsem (such that we don't have to convert it to a range lock) Signed-off-by: Davidlohr Bueso --- mm/mmap.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/mm/mmap.c b/mm/mmap.c index

[PATCH 64/64] mm: convert mmap_sem to range mmap_lock

From: Davidlohr Bueso With mmrange now in place and everyone using the mm locking wrappers, we can convert the rwsem to a the range locking scheme. Every single user of mmap_sem will use a full range, which means that there is no more parallelism than what we already had. This

[PATCH 64/64] mm: convert mmap_sem to range mmap_lock

From: Davidlohr Bueso With mmrange now in place and everyone using the mm locking wrappers, we can convert the rwsem to a the range locking scheme. Every single user of mmap_sem will use a full range, which means that there is no more parallelism than what we already had. This is the worst case

[PATCH 18/64] mm/ksm: teach about range locking

From: Davidlohr Bueso Conversion is straightforward as most calls use mmap_sem within the same function context. No changes in semantics. Signed-off-by: Davidlohr Bueso --- mm/ksm.c | 40 +++- 1 file changed, 23

[PATCH 18/64] mm/ksm: teach about range locking

From: Davidlohr Bueso Conversion is straightforward as most calls use mmap_sem within the same function context. No changes in semantics. Signed-off-by: Davidlohr Bueso --- mm/ksm.c | 40 +++- 1 file changed, 23 insertions(+), 17 deletions(-) diff --git

[PATCH 01/64] interval-tree: build unconditionally

From: Davidlohr Bueso In preparation for range locking, this patch gets rid of CONFIG_INTERVAL_TREE option as we will unconditionally build it. Signed-off-by: Davidlohr Bueso --- drivers/gpu/drm/Kconfig | 2 -- drivers/gpu/drm/i915/Kconfig | 1 -

[PATCH 13/64] fs/proc: teach about range locking

From: Davidlohr Bueso And use mm locking wrappers -- no change in semantics. Signed-off-by: Davidlohr Bueso --- fs/proc/base.c | 33 - fs/proc/task_mmu.c | 22 +++--- fs/proc/task_nommu.c | 22

[RFC PATCH 00/64] mm: towards parallel address space operations

From: Davidlohr Bueso Hi, This patchset is a new version of both the range locking machinery as well as a full mmap_sem conversion that makes use of it -- as the worst case scenario as all mmap_sem calls are converted to a full range mmap_lock equivalent. As such, while there

[PATCH 08/64] mm: teach lock_page_or_retry() about range locking

From: Davidlohr Bueso The mmap_sem locking rules for lock_page_or_retry() depends on the page being locked upon return, and can get funky. As such we need to teach the function about mmrange, which is passed on via vm_fault. Signed-off-by: Davidlohr Bueso ---

[PATCH 01/64] interval-tree: build unconditionally

From: Davidlohr Bueso In preparation for range locking, this patch gets rid of CONFIG_INTERVAL_TREE option as we will unconditionally build it. Signed-off-by: Davidlohr Bueso --- drivers/gpu/drm/Kconfig | 2 -- drivers/gpu/drm/i915/Kconfig | 1 - lib/Kconfig | 14

[PATCH 13/64] fs/proc: teach about range locking

From: Davidlohr Bueso And use mm locking wrappers -- no change in semantics. Signed-off-by: Davidlohr Bueso --- fs/proc/base.c | 33 - fs/proc/task_mmu.c | 22 +++--- fs/proc/task_nommu.c | 22 +- 3 files changed, 44

[RFC PATCH 00/64] mm: towards parallel address space operations

From: Davidlohr Bueso Hi, This patchset is a new version of both the range locking machinery as well as a full mmap_sem conversion that makes use of it -- as the worst case scenario as all mmap_sem calls are converted to a full range mmap_lock equivalent. As such, while there is no improvement

[PATCH 08/64] mm: teach lock_page_or_retry() about range locking

From: Davidlohr Bueso The mmap_sem locking rules for lock_page_or_retry() depends on the page being locked upon return, and can get funky. As such we need to teach the function about mmrange, which is passed on via vm_fault. Signed-off-by: Davidlohr Bueso --- include/linux/pagemap.h | 7

[PATCH 03/64] mm: introduce mm locking wrappers

From: Davidlohr Bueso This patch adds the necessary wrappers to encapsulate mmap_sem locking and will enable any future changes to be a lot more confined to here. In addition, future users will incrementally be added in the next patches. mm_[read/write]_[un]lock() naming is

[PATCH 03/64] mm: introduce mm locking wrappers

From: Davidlohr Bueso This patch adds the necessary wrappers to encapsulate mmap_sem locking and will enable any future changes to be a lot more confined to here. In addition, future users will incrementally be added in the next patches. mm_[read/write]_[un]lock() naming is used. Signed-off-by:

[PATCH 05/64] mm,khugepaged: prepare passing of rangelock field to vm_fault

From: Davidlohr Bueso When collapsing huge pages from swapin, a vm_fault structure is built and passed to do_swap_page(). The new range field of the vm_fault structure must be set correctly when dealing with range_lock. We teach the main workhorse, khugepaged_scan_mm_slot(),

[PATCH 05/64] mm,khugepaged: prepare passing of rangelock field to vm_fault

From: Davidlohr Bueso When collapsing huge pages from swapin, a vm_fault structure is built and passed to do_swap_page(). The new range field of the vm_fault structure must be set correctly when dealing with range_lock. We teach the main workhorse, khugepaged_scan_mm_slot(), to pass on a full

[PATCH 15/64] ipc: use mm locking wrappers

From: Davidlohr Bueso This is straightforward as the necessary syscalls already know about mmrange. No change in semantics. Signed-off-by: Davidlohr Bueso --- ipc/shm.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/ipc/shm.c

[PATCH 15/64] ipc: use mm locking wrappers

From: Davidlohr Bueso This is straightforward as the necessary syscalls already know about mmrange. No change in semantics. Signed-off-by: Davidlohr Bueso --- ipc/shm.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/ipc/shm.c b/ipc/shm.c index

[PATCH 02/64] Introduce range reader/writer lock

From: Davidlohr Bueso This implements a sleepable range rwlock, based on interval tree, serializing conflicting/intersecting/overlapping ranges within the tree. The largest range is given by [0, ~0] (inclusive). Unlike traditional locks, range locking involves dealing with the

[PATCH 07/64] mm/hugetlb: teach hugetlb_fault() about range locking

From: Davidlohr Bueso Such that we can pass the mmrange along to vm_fault for page in userfault range (handle_userfault()) which gets funky with mmap_sem - just look at the locking rules. Signed-off-by: Davidlohr Bueso --- include/linux/hugetlb.h | 9

[PATCH 07/64] mm/hugetlb: teach hugetlb_fault() about range locking

From: Davidlohr Bueso Such that we can pass the mmrange along to vm_fault for page in userfault range (handle_userfault()) which gets funky with mmap_sem - just look at the locking rules. Signed-off-by: Davidlohr Bueso --- include/linux/hugetlb.h | 9 + mm/gup.c| 3

[PATCH 02/64] Introduce range reader/writer lock

From: Davidlohr Bueso This implements a sleepable range rwlock, based on interval tree, serializing conflicting/intersecting/overlapping ranges within the tree. The largest range is given by [0, ~0] (inclusive). Unlike traditional locks, range locking involves dealing with the tree itself and

[PATCH 09/64] mm/mmu_notifier: teach oom reaper about range locking

From: Davidlohr Bueso Also begin using mm_is_locked() wrappers (which is sometimes the only reason why mm_has_blockable_invalidate_notifiers() needs to be aware of the range passed back in oom_reap_task_mm(). Signed-off-by: Davidlohr Bueso ---

[PATCH 14/20] iio: gyro: mpu3050: Remove INPUT_MPU3050 dep. from I2C

The INPUT_MPU3050 symbol was removed in commit b1fe0cf06f92 ("Input: delete MPU3050 driver"). Remove the negative dependency on it from the MPU3050_I2C symbol. It is always satisfied now. Discovered with the https://github.com/ulfalizer/Kconfiglib/blob/master/examples/list_undefined.py script.

[PATCH 09/64] mm/mmu_notifier: teach oom reaper about range locking

From: Davidlohr Bueso Also begin using mm_is_locked() wrappers (which is sometimes the only reason why mm_has_blockable_invalidate_notifiers() needs to be aware of the range passed back in oom_reap_task_mm(). Signed-off-by: Davidlohr Bueso --- include/linux/mmu_notifier.h | 6 --

[PATCH 14/20] iio: gyro: mpu3050: Remove INPUT_MPU3050 dep. from I2C

The INPUT_MPU3050 symbol was removed in commit b1fe0cf06f92 ("Input: delete MPU3050 driver"). Remove the negative dependency on it from the MPU3050_I2C symbol. It is always satisfied now. Discovered with the https://github.com/ulfalizer/Kconfiglib/blob/master/examples/list_undefined.py script.

[PATCH 04/64] mm: add a range parameter to the vm_fault structure

From: Davidlohr Bueso When handling a page fault, it happens that the mmap_sem is released during the processing. As moving to range lock requires to pass the range parameter to the lock/unlock operation, this patch add a pointer to the range structure used when locking the

[PATCH 04/64] mm: add a range parameter to the vm_fault structure

From: Davidlohr Bueso When handling a page fault, it happens that the mmap_sem is released during the processing. As moving to range lock requires to pass the range parameter to the lock/unlock operation, this patch add a pointer to the range structure used when locking the mmap_sem to vm_fault

[PATCH 19/20] ARC: Fix malformed ARC_EMUL_UNALIGNED default

'default N' should be 'default n', though they happen to have the same effect here, due to undefined symbols (N in this case) evaluating to n in a tristate sense. Remove the default from ARC_EMUL_UNALIGNED instead of changing it. bool and tristate symbols implicitly default to n. Discovered with

[PATCH 18/20] iwlwifi: fix malformed CONFIG_IWLWIFI_PCIE_RTPM default

'default false' should be 'default n', though they happen to have the same effect here, due to undefined symbols ('false' in this case) evaluating to n in a tristate sense. Remove the default instead of changing it. bool and tristate symbols implicitly default to n. Discovered with the

[PATCH 19/20] ARC: Fix malformed ARC_EMUL_UNALIGNED default

'default N' should be 'default n', though they happen to have the same effect here, due to undefined symbols (N in this case) evaluating to n in a tristate sense. Remove the default from ARC_EMUL_UNALIGNED instead of changing it. bool and tristate symbols implicitly default to n. Discovered with

[PATCH 18/20] iwlwifi: fix malformed CONFIG_IWLWIFI_PCIE_RTPM default

'default false' should be 'default n', though they happen to have the same effect here, due to undefined symbols ('false' in this case) evaluating to n in a tristate sense. Remove the default instead of changing it. bool and tristate symbols implicitly default to n. Discovered with the

[PATCH 17/20] media: sec: Remove PLAT_S5P dependency

The PLAT_S5P symbol was removed in commit d78c16ccde96 ("ARM: SAMSUNG: Remove remaining legacy code"). Remove the PLAT_S5P dependency from VIDEO_SAMSUNG_S5P_CEC. Discovered with the https://github.com/ulfalizer/Kconfiglib/blob/master/examples/list_undefined.py script. Signed-off-by: Ulf

[PATCH 16/20] auxdisplay: img-ascii-lcd: Remove MIPS_SEAD3 dep.

The MIPS_SEAD3 symbol was removed in commit 64601cb1343f ("leds: Remove SEAD-3 driver"). Remove the MIPS_SEAD3 dependency from IMG_ASCII_LCD. Discovered with the https://github.com/ulfalizer/Kconfiglib/blob/master/examples/list_undefined.py script. Signed-off-by: Ulf Magnusson

[PATCH 17/20] media: sec: Remove PLAT_S5P dependency

The PLAT_S5P symbol was removed in commit d78c16ccde96 ("ARM: SAMSUNG: Remove remaining legacy code"). Remove the PLAT_S5P dependency from VIDEO_SAMSUNG_S5P_CEC. Discovered with the https://github.com/ulfalizer/Kconfiglib/blob/master/examples/list_undefined.py script. Signed-off-by: Ulf

[PATCH 16/20] auxdisplay: img-ascii-lcd: Remove MIPS_SEAD3 dep.

The MIPS_SEAD3 symbol was removed in commit 64601cb1343f ("leds: Remove SEAD-3 driver"). Remove the MIPS_SEAD3 dependency from IMG_ASCII_LCD. Discovered with the https://github.com/ulfalizer/Kconfiglib/blob/master/examples/list_undefined.py script. Signed-off-by: Ulf Magnusson ---

[PATCH 20/20] x86/PCI: VMD: Fix malformed default

'default N' should be 'default n', though they happen to have the same effect here, due to undefined symbols (N in this case) evaluating to n in a tristate sense. Remove the default from VMD instead of changing it. bool and tristate symbols implicitly default to n. Discovered with the

[PATCH 20/20] x86/PCI: VMD: Fix malformed default

'default N' should be 'default n', though they happen to have the same effect here, due to undefined symbols (N in this case) evaluating to n in a tristate sense. Remove the default from VMD instead of changing it. bool and tristate symbols implicitly default to n. Discovered with the

[PATCH 15/20] phy: Remove SOC_EXYNOS4212 dep. from PHY_EXYNOS4X12_USB

Exynos4212 support was removed by commit bca9085e0ae9 ("ARM: dts: exynos: remove Exynos4212 support (dead code)"). Remove the SOC_EXYNOS4212 dependency from PHY_EXYNOS4X12_USB. Discovered with the https://github.com/ulfalizer/Kconfiglib/blob/master/examples/list_undefined.py script.

[PATCH 15/20] phy: Remove SOC_EXYNOS4212 dep. from PHY_EXYNOS4X12_USB

Exynos4212 support was removed by commit bca9085e0ae9 ("ARM: dts: exynos: remove Exynos4212 support (dead code)"). Remove the SOC_EXYNOS4212 dependency from PHY_EXYNOS4X12_USB. Discovered with the https://github.com/ulfalizer/Kconfiglib/blob/master/examples/list_undefined.py script.

[PATCH 12/20] ARM: debug: Remove ARCH_MSM dep. from UNCOMPRESS_INCLUDE

The ARCH_MSM symbol was removed in commit c0c89fafa289 ("ARM: Remove mach-msm and associated ARM architecture code"), but a default in UNCOMPRESS_INCLUDE still depends on it. Remove the ARCH_MSM dependency from the default in UNCOMPRESS_INCLUDE. Discovered with the

[PATCH 10/20] lib/Kconfig: Remove leftover select of GENERIC_IO

GENERIC_IO was removed by commit 9de8da47742b ("kconfig: kill off GENERIC_IO option"), but HAS_IOMEM still selects it. Remove the select of GENERIC_IO from HAS_IOMEM. Discovered with the https://github.com/ulfalizer/Kconfiglib/blob/master/examples/list_undefined.py script. Signed-off-by: Ulf

[PATCH 12/20] ARM: debug: Remove ARCH_MSM dep. from UNCOMPRESS_INCLUDE

The ARCH_MSM symbol was removed in commit c0c89fafa289 ("ARM: Remove mach-msm and associated ARM architecture code"), but a default in UNCOMPRESS_INCLUDE still depends on it. Remove the ARCH_MSM dependency from the default in UNCOMPRESS_INCLUDE. Discovered with the

[PATCH 10/20] lib/Kconfig: Remove leftover select of GENERIC_IO

GENERIC_IO was removed by commit 9de8da47742b ("kconfig: kill off GENERIC_IO option"), but HAS_IOMEM still selects it. Remove the select of GENERIC_IO from HAS_IOMEM. Discovered with the https://github.com/ulfalizer/Kconfiglib/blob/master/examples/list_undefined.py script. Signed-off-by: Ulf

[PATCH 13/20] ore: Remove PNFS_OBJLAYOUT dependency

The PNFS_OBJLAYOUT symbol was removed in commit 6d22323b2e9f ("nfs: remove the objlayout driver"), but the ORE symbol still depends on it. Remove the PNFS_OBJLAYOUT dependency from ORE. Discovered with the https://github.com/ulfalizer/Kconfiglib/blob/master/examples/list_undefined.py script.

[PATCH 09/20] clk: sunxi-ng: Remove SUNXI_CCU_* selects

The selected symbols were removed in commit 06e226c7fb23 ("clk: sunxi-ng: Move all clock types to a library"). Remove the selects from SUN4I_A10_CCU. Discovered with the https://github.com/ulfalizer/Kconfiglib/blob/master/examples/list_undefined.py script. Signed-off-by: Ulf Magnusson

[PATCH 13/20] ore: Remove PNFS_OBJLAYOUT dependency

The PNFS_OBJLAYOUT symbol was removed in commit 6d22323b2e9f ("nfs: remove the objlayout driver"), but the ORE symbol still depends on it. Remove the PNFS_OBJLAYOUT dependency from ORE. Discovered with the https://github.com/ulfalizer/Kconfiglib/blob/master/examples/list_undefined.py script.

[PATCH 09/20] clk: sunxi-ng: Remove SUNXI_CCU_* selects

The selected symbols were removed in commit 06e226c7fb23 ("clk: sunxi-ng: Move all clock types to a library"). Remove the selects from SUN4I_A10_CCU. Discovered with the https://github.com/ulfalizer/Kconfiglib/blob/master/examples/list_undefined.py script. Signed-off-by: Ulf Magnusson ---

[PATCH 11/20] usb: gadget: udc: Remove USB_GADGET_DUALSPEED select

USB_GADGET_DUALSPEED was removed by commit 85b8614d7223 ("usb: gadget: get rid of USB_GADGET_{DUAL,SUPER}SPEED"), but the USB_SNP_UDC_PLAT symbol still selects it. Remove the USB_GADGET_DUALSPEED select from USB_SNP_UDC_PLAT. Discovered with the

[PATCH 11/20] usb: gadget: udc: Remove USB_GADGET_DUALSPEED select

USB_GADGET_DUALSPEED was removed by commit 85b8614d7223 ("usb: gadget: get rid of USB_GADGET_{DUAL,SUPER}SPEED"), but the USB_SNP_UDC_PLAT symbol still selects it. Remove the USB_GADGET_DUALSPEED select from USB_SNP_UDC_PLAT. Discovered with the

[PATCH 06/20] riscv: Remove ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE select

The ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE symbol was removed in commit 51a021244b9d ("atomic64: no need for CONFIG_ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE"). Remove the ARCH_HAS_ATOMIC64_DEC_IS_POSITIVE select from RISCV. Discovered with the

[PATCH 06/20] riscv: Remove ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE select

The ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE symbol was removed in commit 51a021244b9d ("atomic64: no need for CONFIG_ARCH_HAS_ATOMIC64_DEC_IF_POSITIVE"). Remove the ARCH_HAS_ATOMIC64_DEC_IS_POSITIVE select from RISCV. Discovered with the

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

The PLATFORM_AT32AP symbol went away when AVR32 was removed in commit 26202873bb51 ("avr32: remove support for AVR32 architecture"). Remove the RTC_DRV_AT32AP700X dependency from RTC_DRV_AT32AP700X. Discovered with the

[PATCH 07/20] riscv: Remove ARCH_WANT_OPTIONAL_GPIOLIB select

The ARCH_WANT_OPTIONAL_GPIOLIB symbol was removed in commit 65053e1a7743 ("gpio: delete ARCH_[WANTS_OPTIONAL|REQUIRE]_GPIOLIB"). GPIOLIB should just be selected explicitly if needed. Remove the ARCH_WANT_OPTIONAL_GPIOLIB select from RISCV. See commit 0145071b3314 ("x86: Do away with

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

The PLATFORM_AT32AP symbol went away when AVR32 was removed in commit 26202873bb51 ("avr32: remove support for AVR32 architecture"). Remove the RTC_DRV_AT32AP700X dependency from RTC_DRV_AT32AP700X. Discovered with the

[PATCH 07/20] riscv: Remove ARCH_WANT_OPTIONAL_GPIOLIB select

The ARCH_WANT_OPTIONAL_GPIOLIB symbol was removed in commit 65053e1a7743 ("gpio: delete ARCH_[WANTS_OPTIONAL|REQUIRE]_GPIOLIB"). GPIOLIB should just be selected explicitly if needed. Remove the ARCH_WANT_OPTIONAL_GPIOLIB select from RISCV. See commit 0145071b3314 ("x86: Do away with

[PATCH 08/20] s390/kconfig: Remove ARCH_WANTS_PROT_NUMA_PROT_NONE select

The ARCH_WANTS_PROT_NUMA_PROT_NONE symbol was removed by commit 6a33979d5bd7 ("mm: remove misleading ARCH_USES_NUMA_PROT_NONE"), but S390 still selects it. Remove the ARCH_WANTS_PROT_NUMA_PROT_NONE select from the S390 symbol. Discovered with the

[PATCH 08/20] s390/kconfig: Remove ARCH_WANTS_PROT_NUMA_PROT_NONE select

The ARCH_WANTS_PROT_NUMA_PROT_NONE symbol was removed by commit 6a33979d5bd7 ("mm: remove misleading ARCH_USES_NUMA_PROT_NONE"), but S390 still selects it. Remove the ARCH_WANTS_PROT_NUMA_PROT_NONE select from the S390 symbol. Discovered with the

[PATCH 04/20] misc: atmel: Remove CPU_AT32AP700X (AVR32) reference

The CPU_AT32AP700X symbol symbol went away when when AVR32 was removed in commit 26202873bb51 ("avr32: remove support for AVR32 architecture") Remove the prompt from ATMEL_TCB_CLKSRC_BLOCK. The prompt condition could never be satisfied now. Discovered with the

[PATCH 04/20] misc: atmel: Remove CPU_AT32AP700X (AVR32) reference

The CPU_AT32AP700X symbol symbol went away when when AVR32 was removed in commit 26202873bb51 ("avr32: remove support for AVR32 architecture") Remove the prompt from ATMEL_TCB_CLKSRC_BLOCK. The prompt condition could never be satisfied now. Discovered with the

[PATCH 02/20] KVM: PPC: Book3S PR: Fix broken select due to misspelling

Commit 76d837a4c0f9 ("KVM: PPC: Book3S PR: Don't include SPAPR TCE code on non-pseries platforms") added a reference to the globally undefined symbol PPC_SERIES. Looking at the rest of the commit, PPC_PSERIES was probably intended. Change PPC_SERIES to PPC_PSERIES. Discovered with the

[PATCH 02/20] KVM: PPC: Book3S PR: Fix broken select due to misspelling

Commit 76d837a4c0f9 ("KVM: PPC: Book3S PR: Don't include SPAPR TCE code on non-pseries platforms") added a reference to the globally undefined symbol PPC_SERIES. Looking at the rest of the commit, PPC_PSERIES was probably intended. Change PPC_SERIES to PPC_PSERIES. Discovered with the

[PATCH 03/20] kconfig: Remove leftover references to AVR32 symbol

The AVR32 symbol was removed in commit 26202873bb51 ("avr32: remove support for AVR32 architecture"). Remove the remaining references to it from the Kconfig files. No references remain to the removed AVR32_AT32AP_CPUFREQ symbol either, so remove that one too. Discovered with the

[PATCH 03/20] kconfig: Remove leftover references to AVR32 symbol

The AVR32 symbol was removed in commit 26202873bb51 ("avr32: remove support for AVR32 architecture"). Remove the remaining references to it from the Kconfig files. No references remain to the removed AVR32_AT32AP_CPUFREQ symbol either, so remove that one too. Discovered with the

[PATCH 01/20] ARM: mvebu: Fix broken PL310_ERRATA_753970 selects

The MACH_ARMADA_375 and MACH_ARMADA_38X boards select ARM_ERRATA_753970, but it was renamed to PL310_ERRATA_753970 by commit fa0ce4035d48 ("ARM: 7162/1: errata: tidy up Kconfig options for PL310 errata workarounds"). Fix the selects to use the new name. Discovered with the

[PATCH 01/20] ARM: mvebu: Fix broken PL310_ERRATA_753970 selects

The MACH_ARMADA_375 and MACH_ARMADA_38X boards select ARM_ERRATA_753970, but it was renamed to PL310_ERRATA_753970 by commit fa0ce4035d48 ("ARM: 7162/1: errata: tidy up Kconfig options for PL310 errata workarounds"). Fix the selects to use the new name. Discovered with the

[PATCH 00/20] Remove references to undefined symbols and fix two potential bugs

Hello, This patchset fixes most references to globally undefined symbols in Kconfig files, as reported by the https://github.com/ulfalizer/Kconfiglib/blob/master/examples/list_undefined.py script. I will send emails in reply to the patchset for some cases where I'm not sure what the proper fix

[PATCH 00/20] Remove references to undefined symbols and fix two potential bugs

Hello, This patchset fixes most references to globally undefined symbols in Kconfig files, as reported by the https://github.com/ulfalizer/Kconfiglib/blob/master/examples/list_undefined.py script. I will send emails in reply to the patchset for some cases where I'm not sure what the proper fix

<    1   2   3   4   5   6   7   8   9   >