kernel August 2020

kernel@lists.fedoraproject.org

24 participants
137 discussions

Start a nNew thread

[OS-BUILD PATCH] [redhat] New configs in arch/powerpc
by GitLab Bridge on behalf of jeremycline 26 Feb '21

26 Feb '21

4 7

[OS-BUILD PATCH] [redhat] New configs in security/keys
by GitLab Bridge on behalf of jeremycline 02 Feb '21

02 Feb '21

6 8

[OS-BUILD PATCH] [redhat] New configs in drivers/spi
by GitLab Bridge on behalf of jeremycline 29 Jan '21

29 Jan '21

From: "CKI@GitLab" <cki-project(a)redhat.com> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_SPI_AMD: Enables SPI controller driver for AMD SoC. Symbol: SPI_AMD [=n] Type : tristate Defined at drivers/spi/Kconfig:917 Prompt: AMD SPI controller Depends on: SPI [=y] && SPI_MASTER [=y] && (SPI_MASTER [=y] || COMPILE_TEST [=n]) Location: -> Device Drivers -> SPI support (SPI [=y]) --- Signed-off-by: CKI@GitLab <cki-project(a)redhat.com> --- redhat/configs/common/generic/CONFIG_SPI_AMD | 1 + .../pending-common/generic/CONFIG_SPI_AMD | 16 ---------------- 2 files changed, 1 insertion(+), 16 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_SPI_AMD delete mode 100644 redhat/configs/pending-common/generic/CONFIG_SPI_AMD diff --git a/redhat/configs/common/generic/CONFIG_SPI_AMD b/redhat/configs/common/generic/CONFIG_SPI_AMD new file mode 100644 index 000000000000..0dc059dce496 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_SPI_AMD @@ -0,0 +1 @@ +# CONFIG_SPI_AMD is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_SPI_AMD b/redhat/configs/pending-common/generic/CONFIG_SPI_AMD deleted file mode 100644 index ac7ea25e07a7..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_SPI_AMD +++ /dev/null @@ -1,16 +0,0 @@ -# CONFIG_SPI_AMD: -# -# Enables SPI controller driver for AMD SoC. -# -# Symbol: SPI_AMD [=n] -# Type : tristate -# Defined at drivers/spi/Kconfig:917 -# Prompt: AMD SPI controller -# Depends on: SPI [=y] && SPI_MASTER [=y] && (SPI_MASTER [=y] || COMPILE_TEST [=n]) -# Location: -# -> Device Drivers -# -> SPI support (SPI [=y]) -# -# -# -# CONFIG_SPI_AMD is not set -- 2.26.2

6 16

[OS-BUILD PATCH] [redhat] New configs in lib/Kconfig.debug
by GitLab Bridge on behalf of jeremycline 28 Jan '21

28 Jan '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_DEBUG_FS_ALLOW_ALL: No restrictions apply. Both API and filesystem registration is on. This is the normal default operation. Symbol: DEBUG_FS_ALLOW_ALL [=y] Type : bool Defined at lib/Kconfig.debug:500 Prompt: Access normal Depends on: <choice> Location: -> Kernel hacking -> Generic Kernel Debugging Instruments -> Debug Filesystem (DEBUG_FS [=y]) -> Debugfs default access (<choice> [=y]) --- CONFIG_DEBUG_FS_ALLOW_NONE: Access is off. Clients get -PERM when trying to create nodes in debugfs tree and debugfs is not registered as a filesystem. Client can then back-off or continue without debugfs access. Symbol: DEBUG_FS_ALLOW_NONE [=n] Type : bool Defined at lib/Kconfig.debug:513 Prompt: No access Depends on: <choice> Location: -> Kernel hacking -> Generic Kernel Debugging Instruments -> Debug Filesystem (DEBUG_FS [=y]) -> Debugfs default access (<choice> [=y]) --- CONFIG_DEBUG_FS_DISALLOW_MOUNT: The API is open but filesystem is not loaded. Clients can still do their work and read with debug tools that do not need debugfs filesystem. Symbol: DEBUG_FS_DISALLOW_MOUNT [=n] Type : bool Defined at lib/Kconfig.debug:506 Prompt: Do not register debugfs as filesystem Depends on: <choice> Location: -> Kernel hacking -> Generic Kernel Debugging Instruments -> Debug Filesystem (DEBUG_FS [=y]) -> Debugfs default access (<choice> [=y]) --- Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- .../common/generic/CONFIG_DEBUG_FS_ALLOW_ALL | 1 + .../common/generic/CONFIG_DEBUG_FS_ALLOW_NONE | 1 + .../generic/CONFIG_DEBUG_FS_DISALLOW_MOUNT | 1 + .../generic/CONFIG_DEBUG_FS_ALLOW_ALL | 19 ------------------ .../generic/CONFIG_DEBUG_FS_ALLOW_NONE | 20 ------------------- .../generic/CONFIG_DEBUG_FS_DISALLOW_MOUNT | 20 ------------------- 6 files changed, 3 insertions(+), 59 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_DEBUG_FS_ALLOW_ALL create mode 100644 redhat/configs/common/generic/CONFIG_DEBUG_FS_ALLOW_NONE create mode 100644 redhat/configs/common/generic/CONFIG_DEBUG_FS_DISALLOW_MOUNT delete mode 100644 redhat/configs/pending-common/generic/CONFIG_DEBUG_FS_ALLOW_ALL delete mode 100644 redhat/configs/pending-common/generic/CONFIG_DEBUG_FS_ALLOW_NONE delete mode 100644 redhat/configs/pending-common/generic/CONFIG_DEBUG_FS_DISALLOW_MOUNT diff --git a/redhat/configs/common/generic/CONFIG_DEBUG_FS_ALLOW_ALL b/redhat/configs/common/generic/CONFIG_DEBUG_FS_ALLOW_ALL new file mode 100644 index 000000000000..69490c3a53d5 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_DEBUG_FS_ALLOW_ALL @@ -0,0 +1 @@ +CONFIG_DEBUG_FS_ALLOW_ALL=y diff --git a/redhat/configs/common/generic/CONFIG_DEBUG_FS_ALLOW_NONE b/redhat/configs/common/generic/CONFIG_DEBUG_FS_ALLOW_NONE new file mode 100644 index 000000000000..2d2a249b14c9 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_DEBUG_FS_ALLOW_NONE @@ -0,0 +1 @@ +# CONFIG_DEBUG_FS_ALLOW_NONE is not set diff --git a/redhat/configs/common/generic/CONFIG_DEBUG_FS_DISALLOW_MOUNT b/redhat/configs/common/generic/CONFIG_DEBUG_FS_DISALLOW_MOUNT new file mode 100644 index 000000000000..d70cb272a100 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_DEBUG_FS_DISALLOW_MOUNT @@ -0,0 +1 @@ +# CONFIG_DEBUG_FS_DISALLOW_MOUNT is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_DEBUG_FS_ALLOW_ALL b/redhat/configs/pending-common/generic/CONFIG_DEBUG_FS_ALLOW_ALL deleted file mode 100644 index 083ba7cb0dd7..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_DEBUG_FS_ALLOW_ALL +++ /dev/null @@ -1,19 +0,0 @@ -# CONFIG_DEBUG_FS_ALLOW_ALL: -# -# No restrictions apply. Both API and filesystem registration -# is on. This is the normal default operation. -# -# Symbol: DEBUG_FS_ALLOW_ALL [=y] -# Type : bool -# Defined at lib/Kconfig.debug:500 -# Prompt: Access normal -# Depends on: <choice> -# Location: -# -> Kernel hacking -# -> Generic Kernel Debugging Instruments -# -> Debug Filesystem (DEBUG_FS [=y]) -# -> Debugfs default access (<choice> [=y]) -# -# -# -CONFIG_DEBUG_FS_ALLOW_ALL=y diff --git a/redhat/configs/pending-common/generic/CONFIG_DEBUG_FS_ALLOW_NONE b/redhat/configs/pending-common/generic/CONFIG_DEBUG_FS_ALLOW_NONE deleted file mode 100644 index f61111aac6c0..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_DEBUG_FS_ALLOW_NONE +++ /dev/null @@ -1,20 +0,0 @@ -# CONFIG_DEBUG_FS_ALLOW_NONE: -# -# Access is off. Clients get -PERM when trying to create nodes in -# debugfs tree and debugfs is not registered as a filesystem. -# Client can then back-off or continue without debugfs access. -# -# Symbol: DEBUG_FS_ALLOW_NONE [=n] -# Type : bool -# Defined at lib/Kconfig.debug:513 -# Prompt: No access -# Depends on: <choice> -# Location: -# -> Kernel hacking -# -> Generic Kernel Debugging Instruments -# -> Debug Filesystem (DEBUG_FS [=y]) -# -> Debugfs default access (<choice> [=y]) -# -# -# -# CONFIG_DEBUG_FS_ALLOW_NONE is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_DEBUG_FS_DISALLOW_MOUNT b/redhat/configs/pending-common/generic/CONFIG_DEBUG_FS_DISALLOW_MOUNT deleted file mode 100644 index 270523a0536d..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_DEBUG_FS_DISALLOW_MOUNT +++ /dev/null @@ -1,20 +0,0 @@ -# CONFIG_DEBUG_FS_DISALLOW_MOUNT: -# -# The API is open but filesystem is not loaded. Clients can still do -# their work and read with debug tools that do not need -# debugfs filesystem. -# -# Symbol: DEBUG_FS_DISALLOW_MOUNT [=n] -# Type : bool -# Defined at lib/Kconfig.debug:506 -# Prompt: Do not register debugfs as filesystem -# Depends on: <choice> -# Location: -# -> Kernel hacking -# -> Generic Kernel Debugging Instruments -# -> Debug Filesystem (DEBUG_FS [=y]) -# -> Debugfs default access (<choice> [=y]) -# -# -# -# CONFIG_DEBUG_FS_DISALLOW_MOUNT is not set -- GitLab

5 7

[OS-BUILD PATCH] [redhat] New configs in lib/Kconfig.debug
by GitLab Bridge on behalf of jeremycline 28 Jan '21

28 Jan '21

From: Fedora Kernel Team <kernel-team(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_DEBUG_VM_PGTABLE: This option provides a debug method which can be used to test architecture page table helper functions on various platforms in verifying if they comply with expected generic MM semantics. This will help architecture code in making sure that any changes or new additions of these helpers still conform to expected semantics of the generic MM. Platforms will have to opt in for this through ARCH_HAS_DEBUG_VM_PGTABLE. If unsure, say N. Symbol: DEBUG_VM_PGTABLE [=n] Type : bool Defined at lib/Kconfig.debug:702 Prompt: Debug arch page table for semantics compliance Depends on: MMU [=y] && ARCH_HAS_DEBUG_VM_PGTABLE [=y] Location: -> Kernel hacking -> Memory Debugging --- CONFIG_TEST_BITOPS: This builds the "test_bitops" module that is much like the TEST_LKM module except that it does a basic exercise of the clear_bit and set_bit macros to make sure there are no compiler warnings from C=1 sparse checker or -Wextra compilations. It has no dependencies and doesn't run or load unless explicitly requested by name. for example: modprobe test_bitops. If unsure, say N. Symbol: TEST_BITOPS [=n] Type : tristate Defined at lib/Kconfig.debug:2025 Prompt: Test module for compilation of clear_bit/set_bit operations Depends on: RUNTIME_TESTING_MENU [=y] && m && MODULES [=y] Location: -> Kernel hacking -> Kernel Testing and Coverage -> Runtime Testing (RUNTIME_TESTING_MENU [=y]) --- Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org> --- .../common/generic/CONFIG_DEBUG_VM_PGTABLE | 1 + .../configs/common/generic/CONFIG_TEST_BITOPS | 1 + .../generic/CONFIG_DEBUG_VM_PGTABLE | 24 ------------------- .../pending-common/generic/CONFIG_TEST_BITOPS | 24 ------------------- 4 files changed, 2 insertions(+), 48 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_DEBUG_VM_PGTABLE create mode 100644 redhat/configs/common/generic/CONFIG_TEST_BITOPS delete mode 100644 redhat/configs/pending-common/generic/CONFIG_DEBUG_VM_PGTABLE delete mode 100644 redhat/configs/pending-common/generic/CONFIG_TEST_BITOPS diff --git a/redhat/configs/common/generic/CONFIG_DEBUG_VM_PGTABLE b/redhat/configs/common/generic/CONFIG_DEBUG_VM_PGTABLE new file mode 100644 index 000000000000..2dabf3429c81 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_DEBUG_VM_PGTABLE @@ -0,0 +1 @@ +# CONFIG_DEBUG_VM_PGTABLE is not set diff --git a/redhat/configs/common/generic/CONFIG_TEST_BITOPS b/redhat/configs/common/generic/CONFIG_TEST_BITOPS new file mode 100644 index 000000000000..245f24428550 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_TEST_BITOPS @@ -0,0 +1 @@ +# CONFIG_TEST_BITOPS is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_DEBUG_VM_PGTABLE b/redhat/configs/pending-common/generic/CONFIG_DEBUG_VM_PGTABLE deleted file mode 100644 index 9f311469e240..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_DEBUG_VM_PGTABLE +++ /dev/null @@ -1,24 +0,0 @@ -# CONFIG_DEBUG_VM_PGTABLE: -# -# This option provides a debug method which can be used to test -# architecture page table helper functions on various platforms in -# verifying if they comply with expected generic MM semantics. This -# will help architecture code in making sure that any changes or -# new additions of these helpers still conform to expected -# semantics of the generic MM. Platforms will have to opt in for -# this through ARCH_HAS_DEBUG_VM_PGTABLE. -# -# If unsure, say N. -# -# Symbol: DEBUG_VM_PGTABLE [=n] -# Type : bool -# Defined at lib/Kconfig.debug:702 -# Prompt: Debug arch page table for semantics compliance -# Depends on: MMU [=y] && ARCH_HAS_DEBUG_VM_PGTABLE [=y] -# Location: -# -> Kernel hacking -# -> Memory Debugging -# -# -# -# CONFIG_DEBUG_VM_PGTABLE is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_TEST_BITOPS b/redhat/configs/pending-common/generic/CONFIG_TEST_BITOPS deleted file mode 100644 index 86e8dea053dc..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_TEST_BITOPS +++ /dev/null @@ -1,24 +0,0 @@ -# CONFIG_TEST_BITOPS: -# -# This builds the "test_bitops" module that is much like the -# TEST_LKM module except that it does a basic exercise of the -# clear_bit and set_bit macros to make sure there are no compiler -# warnings from C=1 sparse checker or -Wextra compilations. It has -# no dependencies and doesn't run or load unless explicitly requested -# by name. for example: modprobe test_bitops. -# -# If unsure, say N. -# -# Symbol: TEST_BITOPS [=n] -# Type : tristate -# Defined at lib/Kconfig.debug:2025 -# Prompt: Test module for compilation of clear_bit/set_bit operations -# Depends on: RUNTIME_TESTING_MENU [=y] && m && MODULES [=y] -# Location: -# -> Kernel hacking -# -> Kernel Testing and Coverage -# -> Runtime Testing (RUNTIME_TESTING_MENU [=y]) -# -# -# -# CONFIG_TEST_BITOPS is not set -- 2.26.2

7 17

[OS-BUILD PATCH] [redhat] New configs in drivers/clk
by GitLab Bridge on behalf of jmflinuxtx 27 Jan '21

27 Jan '21

From: "Justin M. Forbes" <jforbes(a)fedoraproject.org> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_COMMON_CLK: The common clock framework is a single definition of struct clk, useful across many platforms, as well as an implementation of the clock API in include/linux/clk.h. Architectures utilizing the common struct clk should select this option. Symbol: COMMON_CLK [=n] Type : bool Defined at drivers/clk/Kconfig:25 Prompt: Common Clock Framework Depends on: !HAVE_LEGACY_CLK [=n] Location: -> Device Drivers Selects: HAVE_CLK_PREPARE [=n] && CLKDEV_LOOKUP [=n] && SRCU [=y] && RATIONAL [=n] Selected by [n]: - MFD_INTEL_LPSS [=n] && HAS_IOMEM [=y] - INTEL_ATOMISP [=n] && STAGING [=n] && STAGING_MEDIA [=n] && MEDIA_SUPPORT [=n] && X86 && EFI && PCI [=y] && ACPI - PMC_ATOM [=n] && X86 && PCI [=y] --- Signed-off-by: Justin M. Forbes <jforbes(a)fedoraproject.org> --- .../configs/common/generic/CONFIG_COMMON_CLK | 1 + .../pending-common/generic/CONFIG_COMMON_CLK | 24 ------------------- 2 files changed, 1 insertion(+), 24 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_COMMON_CLK delete mode 100644 redhat/configs/pending-common/generic/CONFIG_COMMON_CLK diff --git a/redhat/configs/common/generic/CONFIG_COMMON_CLK b/redhat/configs/common/generic/CONFIG_COMMON_CLK new file mode 100644 index 000000000000..077e3ea2a4bb --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_COMMON_CLK @@ -0,0 +1 @@ +# CONFIG_COMMON_CLK is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_COMMON_CLK b/redhat/configs/pending-common/generic/CONFIG_COMMON_CLK deleted file mode 100644 index ce3f5f9ca539..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_COMMON_CLK +++ /dev/null @@ -1,24 +0,0 @@ -# CONFIG_COMMON_CLK: -# -# The common clock framework is a single definition of struct -# clk, useful across many platforms, as well as an -# implementation of the clock API in include/linux/clk.h. -# Architectures utilizing the common struct clk should select -# this option. -# -# Symbol: COMMON_CLK [=n] -# Type : bool -# Defined at drivers/clk/Kconfig:25 -# Prompt: Common Clock Framework -# Depends on: !HAVE_LEGACY_CLK [=n] -# Location: -# -> Device Drivers -# Selects: HAVE_CLK_PREPARE [=n] && CLKDEV_LOOKUP [=n] && SRCU [=y] && RATIONAL [=n] -# Selected by [n]: -# - MFD_INTEL_LPSS [=n] && HAS_IOMEM [=y] -# - INTEL_ATOMISP [=n] && STAGING [=n] && STAGING_MEDIA [=n] && MEDIA_SUPPORT [=n] && X86 && EFI && PCI [=y] && ACPI -# - PMC_ATOM [=n] && X86 && PCI [=y] -# -# -# -# CONFIG_COMMON_CLK is not set -- 2.27.0

6 12

[OS-BUILD PATCH] [redhat] New configs in drivers/dma-buf
by GitLab Bridge on behalf of jeremycline 26 Jan '21

26 Jan '21

5 9

[OS-BUILD PATCH] [redhat] New configs in drivers/pinctrl
by GitLab Bridge on behalf of jeremycline 26 Jan '21

26 Jan '21

5 12

[OS-BUILD PATCH] [redhat] New configs in drivers/clk
by GitLab Bridge on behalf of jeremycline 26 Jan '21

26 Jan '21

4 4

[OS-BUILD PATCH] [redhat] New configs in fs/pstore
by GitLab Bridge on behalf of jeremycline 26 Jan '21

26 Jan '21

From: "CKI@GitLab" <cki-project(a)redhat.com> Hi, As part of the ongoing rebase effort, the following configuration options need to be reviewed. As a reminder, the ARK configuration flow involves moving unreviewed configuration options from the pending directory to the ark directory. In the diff below, options are removed from the pending directory and added to the ark hierarchy. The final options that need to be ACKed are the files that are being added to the ark hierarchy. If the value for a file that is added should be changed, please reply with a better option. CONFIG_PSTORE_BLK: This enables panic and oops message to be logged to a block dev where it can be read back at some later point. For more information, see Documentation/admin-guide/pstore-blk.rst If unsure, say N. Symbol: PSTORE_BLK [=n] Type : tristate Defined at fs/pstore/Kconfig:164 Prompt: Log panic/oops to a block device Depends on: MISC_FILESYSTEMS [=y] && PSTORE [=y] && BLOCK [=y] Location: -> File systems -> Miscellaneous filesystems (MISC_FILESYSTEMS [=y]) -> Persistent store support (PSTORE [=y]) Selects: PSTORE_ZONE [=n] --- Signed-off-by: CKI@GitLab <cki-project(a)redhat.com> --- .../configs/common/generic/CONFIG_PSTORE_BLK | 1 + .../pending-common/generic/CONFIG_PSTORE_BLK | 23 ------------------- 2 files changed, 1 insertion(+), 23 deletions(-) create mode 100644 redhat/configs/common/generic/CONFIG_PSTORE_BLK delete mode 100644 redhat/configs/pending-common/generic/CONFIG_PSTORE_BLK diff --git a/redhat/configs/common/generic/CONFIG_PSTORE_BLK b/redhat/configs/common/generic/CONFIG_PSTORE_BLK new file mode 100644 index 000000000000..c227a05adc7f --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_PSTORE_BLK @@ -0,0 +1 @@ +# CONFIG_PSTORE_BLK is not set diff --git a/redhat/configs/pending-common/generic/CONFIG_PSTORE_BLK b/redhat/configs/pending-common/generic/CONFIG_PSTORE_BLK deleted file mode 100644 index 640fb3b3ad69..000000000000 --- a/redhat/configs/pending-common/generic/CONFIG_PSTORE_BLK +++ /dev/null @@ -1,23 +0,0 @@ -# CONFIG_PSTORE_BLK: -# -# This enables panic and oops message to be logged to a block dev -# where it can be read back at some later point. -# -# For more information, see Documentation/admin-guide/pstore-blk.rst -# -# If unsure, say N. -# -# Symbol: PSTORE_BLK [=n] -# Type : tristate -# Defined at fs/pstore/Kconfig:164 -# Prompt: Log panic/oops to a block device -# Depends on: MISC_FILESYSTEMS [=y] && PSTORE [=y] && BLOCK [=y] -# Location: -# -> File systems -# -> Miscellaneous filesystems (MISC_FILESYSTEMS [=y]) -# -> Persistent store support (PSTORE [=y]) -# Selects: PSTORE_ZONE [=n] -# -# -# -# CONFIG_PSTORE_BLK is not set -- 2.26.2

4 4

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

kernel August 2020