[OS-BUILD PATCH] New configs in arch/arm64
by GitLab Bridge on behalf of jmflinuxtx
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_KVM_ARM_PMU:
Adds support for a virtual Performance Monitoring Unit (PMU) in
virtual machines.
Symbol: KVM_ARM_PMU [=y]
Type : bool
Defined at arch/arm64/kvm/Kconfig:52
Prompt: Virtual Performance Monitoring Unit (PMU) support
Depends on: VIRTUALIZATION [=y] && KVM [=y] && HW_PERF_EVENTS [=y]
Location:
-> Virtualization (VIRTUALIZATION [=y])
-> Kernel-based Virtual Machine (KVM) support (KVM [=y])
Cc: Mark Salter <msalter(a)redhat.com>
---
.../configs/common/generic/CONFIG_KVM_ARM_PMU | 1 +
.../CONFIG_BLK_INLINE_ENCRYPTION_FALLBACK | 1 +
.../pending-common/generic/CONFIG_KVM_ARM_PMU | 17 -----------------
3 files changed, 2 insertions(+), 17 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_KVM_ARM_PMU
create mode 100644 redhat/configs/fedora/generic/CONFIG_BLK_INLINE_ENCRYPTION_FALLBACK
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_KVM_ARM_PMU
diff --git a/redhat/configs/common/generic/CONFIG_KVM_ARM_PMU b/redhat/configs/common/generic/CONFIG_KVM_ARM_PMU
new file mode 100644
index 000000000000..184bfbb54973
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_KVM_ARM_PMU
@@ -0,0 +1 @@
+CONFIG_KVM_ARM_PMU=y
diff --git a/redhat/configs/fedora/generic/CONFIG_BLK_INLINE_ENCRYPTION_FALLBACK b/redhat/configs/fedora/generic/CONFIG_BLK_INLINE_ENCRYPTION_FALLBACK
new file mode 100644
index 000000000000..6f26275b1c75
--- /dev/null
+++ b/redhat/configs/fedora/generic/CONFIG_BLK_INLINE_ENCRYPTION_FALLBACK
@@ -0,0 +1 @@
+CONFIG_BLK_INLINE_ENCRYPTION_FALLBACK=y
diff --git a/redhat/configs/pending-common/generic/CONFIG_KVM_ARM_PMU b/redhat/configs/pending-common/generic/CONFIG_KVM_ARM_PMU
deleted file mode 100644
index c60b45de4995..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_KVM_ARM_PMU
+++ /dev/null
@@ -1,17 +0,0 @@
-# CONFIG_KVM_ARM_PMU:
-#
-# Adds support for a virtual Performance Monitoring Unit (PMU) in
-# virtual machines.
-#
-# Symbol: KVM_ARM_PMU [=y]
-# Type : bool
-# Defined at arch/arm64/kvm/Kconfig:52
-# Prompt: Virtual Performance Monitoring Unit (PMU) support
-# Depends on: VIRTUALIZATION [=y] && KVM [=y] && HW_PERF_EVENTS [=y]
-# Location:
-# -> Virtualization (VIRTUALIZATION [=y])
-# -> Kernel-based Virtual Machine (KVM) support (KVM [=y])
-#
-#
-#
-CONFIG_KVM_ARM_PMU=y
--
GitLab
11 hours, 10 minutes
[OS-BUILD PATCH] [redhat] New configs in drivers/clk
by GitLab Bridge on behalf of jmflinuxtx
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
11 hours, 22 minutes
[OS-BUILD PATCH] [redhat] New configs in drivers/dma-buf
by GitLab Bridge on behalf of jeremycline
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_DMABUF_HEAPS_SYSTEM:
Choose this option to enable the system dmabuf heap. The system heap
is backed by pages from the buddy allocator. If in doubt, say Y.
Symbol: DMABUF_HEAPS_SYSTEM [=n]
Type : bool
Defined at drivers/dma-buf/heaps/Kconfig:1
Prompt: DMA-BUF System Heap
Depends on: DMABUF_HEAPS [=y]
Location:
-> Device Drivers
-> DMABUF options
-> DMA-BUF Userland Memory Heaps (DMABUF_HEAPS [=y])
---
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_DMABUF_HEAPS_SYSTEM | 1 +
.../generic/CONFIG_DMABUF_HEAPS_SYSTEM | 18 ------------------
2 files changed, 1 insertion(+), 18 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_DMABUF_HEAPS_SYSTEM
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_DMABUF_HEAPS_SYSTEM
diff --git a/redhat/configs/common/generic/CONFIG_DMABUF_HEAPS_SYSTEM b/redhat/configs/common/generic/CONFIG_DMABUF_HEAPS_SYSTEM
new file mode 100644
index 000000000000..0e816f5b8e09
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_DMABUF_HEAPS_SYSTEM
@@ -0,0 +1 @@
+# CONFIG_DMABUF_HEAPS_SYSTEM is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_DMABUF_HEAPS_SYSTEM b/redhat/configs/pending-common/generic/CONFIG_DMABUF_HEAPS_SYSTEM
deleted file mode 100644
index 0d3ac7684131..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_DMABUF_HEAPS_SYSTEM
+++ /dev/null
@@ -1,18 +0,0 @@
-# CONFIG_DMABUF_HEAPS_SYSTEM:
-#
-# Choose this option to enable the system dmabuf heap. The system heap
-# is backed by pages from the buddy allocator. If in doubt, say Y.
-#
-# Symbol: DMABUF_HEAPS_SYSTEM [=n]
-# Type : bool
-# Defined at drivers/dma-buf/heaps/Kconfig:1
-# Prompt: DMA-BUF System Heap
-# Depends on: DMABUF_HEAPS [=y]
-# Location:
-# -> Device Drivers
-# -> DMABUF options
-# -> DMA-BUF Userland Memory Heaps (DMABUF_HEAPS [=y])
-#
-#
-#
-# CONFIG_DMABUF_HEAPS_SYSTEM is not set
--
GitLab
1 day, 11 hours
[OS-BUILD PATCH] [redhat] New configs in lib/Kconfig.debug
by GitLab Bridge on behalf of jeremycline
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
1 day, 16 hours
[OS-BUILD PATCH] [redhat] New configs in init/Kconfig
by GitLab Bridge on behalf of jeremycline
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_WATCH_QUEUE:
This is a general notification queue for the kernel to pass events to
userspace by splicing them into pipes. It can be used in conjunction
with watches for key/keyring change notifications and device
notifications.
See Documentation/watch_queue.rst
Symbol: WATCH_QUEUE [=n]
Type : bool
Defined at init/Kconfig:370
Prompt: General notification queue
Location:
-> General setup
---
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../configs/common/generic/CONFIG_WATCH_QUEUE | 1 +
.../pending-common/generic/CONFIG_WATCH_QUEUE | 20 -------------------
2 files changed, 1 insertion(+), 20 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_WATCH_QUEUE
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_WATCH_QUEUE
diff --git a/redhat/configs/common/generic/CONFIG_WATCH_QUEUE b/redhat/configs/common/generic/CONFIG_WATCH_QUEUE
new file mode 100644
index 000000000000..4e2060b85ff3
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_WATCH_QUEUE
@@ -0,0 +1 @@
+# CONFIG_WATCH_QUEUE is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_WATCH_QUEUE b/redhat/configs/pending-common/generic/CONFIG_WATCH_QUEUE
deleted file mode 100644
index 11707e6429cb..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_WATCH_QUEUE
+++ /dev/null
@@ -1,20 +0,0 @@
-# CONFIG_WATCH_QUEUE:
-#
-#
-# This is a general notification queue for the kernel to pass events to
-# userspace by splicing them into pipes. It can be used in conjunction
-# with watches for key/keyring change notifications and device
-# notifications.
-#
-# See Documentation/watch_queue.rst
-#
-# Symbol: WATCH_QUEUE [=n]
-# Type : bool
-# Defined at init/Kconfig:370
-# Prompt: General notification queue
-# Location:
-# -> General setup
-#
-#
-#
-# CONFIG_WATCH_QUEUE is not set
--
GitLab
1 day, 16 hours
[OS-BUILD PATCH] [redhat] New configs in drivers/pinctrl
by GitLab Bridge on behalf of jeremycline
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_PINCTRL_EMMITSBURG:
This pinctrl driver provides an interface that allows configuring
of Intel Emmitsburg pins and using them as GPIOs.
Symbol: PINCTRL_EMMITSBURG [=n]
Type : tristate
Defined at drivers/pinctrl/intel/Kconfig:98
Prompt: Intel Emmitsburg pinctrl and GPIO driver
Depends on: PINCTRL [=y] && (X86 [=y] || COMPILE_TEST [=n]) && ACPI [=y]
Location:
-> Device Drivers
-> Pin controllers (PINCTRL [=y])
Selects: PINCTRL_INTEL [=m]
---
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_PINCTRL_EMMITSBURG | 1 +
.../generic/CONFIG_PINCTRL_EMMITSBURG | 18 ------------------
2 files changed, 1 insertion(+), 18 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_PINCTRL_EMMITSBURG
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_PINCTRL_EMMITSBURG
diff --git a/redhat/configs/common/generic/CONFIG_PINCTRL_EMMITSBURG b/redhat/configs/common/generic/CONFIG_PINCTRL_EMMITSBURG
new file mode 100644
index 000000000000..c347d0b35ef0
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_PINCTRL_EMMITSBURG
@@ -0,0 +1 @@
+# CONFIG_PINCTRL_EMMITSBURG is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_PINCTRL_EMMITSBURG b/redhat/configs/pending-common/generic/CONFIG_PINCTRL_EMMITSBURG
deleted file mode 100644
index 2e35f852e601..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_PINCTRL_EMMITSBURG
+++ /dev/null
@@ -1,18 +0,0 @@
-# CONFIG_PINCTRL_EMMITSBURG:
-#
-# This pinctrl driver provides an interface that allows configuring
-# of Intel Emmitsburg pins and using them as GPIOs.
-#
-# Symbol: PINCTRL_EMMITSBURG [=n]
-# Type : tristate
-# Defined at drivers/pinctrl/intel/Kconfig:98
-# Prompt: Intel Emmitsburg pinctrl and GPIO driver
-# Depends on: PINCTRL [=y] && (X86 [=y] || COMPILE_TEST [=n]) && ACPI [=y]
-# Location:
-# -> Device Drivers
-# -> Pin controllers (PINCTRL [=y])
-# Selects: PINCTRL_INTEL [=m]
-#
-#
-#
-# CONFIG_PINCTRL_EMMITSBURG is not set
--
GitLab
1 day, 16 hours
[OS-BUILD PATCH] New configs in arch/powerpc
by GitLab Bridge on behalf of jeremycline
From: Jeremy Cline <jcline(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_PMU_SYSFS:
This option enables sysfs file creation for PMU SPRs like MMCR* and PMC*.
Symbol: PMU_SYSFS [=n]
Type : bool
Defined at arch/powerpc/platforms/Kconfig.cputype:428
Prompt: Create PMU SPRs sysfs file
Location:
-> Processor support
Cc: kernel-patches(a)redhat.com
---
redhat/configs/common/generic/CONFIG_PMU_SYSFS | 1 +
.../pending-common/generic/CONFIG_PMU_SYSFS | 14 --------------
2 files changed, 1 insertion(+), 14 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_PMU_SYSFS
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_PMU_SYSFS
diff --git a/redhat/configs/common/generic/CONFIG_PMU_SYSFS b/redhat/configs/common/generic/CONFIG_PMU_SYSFS
new file mode 100644
index 000000000000..d192b509fed0
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_PMU_SYSFS
@@ -0,0 +1 @@
+# CONFIG_PMU_SYSFS is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_PMU_SYSFS b/redhat/configs/pending-common/generic/CONFIG_PMU_SYSFS
deleted file mode 100644
index 1f1a0f6cec8a..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_PMU_SYSFS
+++ /dev/null
@@ -1,14 +0,0 @@
-# CONFIG_PMU_SYSFS:
-#
-# This option enables sysfs file creation for PMU SPRs like MMCR* and PMC*.
-#
-# Symbol: PMU_SYSFS [=n]
-# Type : bool
-# Defined at arch/powerpc/platforms/Kconfig.cputype:428
-# Prompt: Create PMU SPRs sysfs file
-# Location:
-# -> Processor support
-#
-#
-#
-# CONFIG_PMU_SYSFS is not set
--
GitLab
1 day, 16 hours
[OS-BUILD PATCH] [redhat] New configs in fs/Kconfig
by GitLab Bridge on behalf of jeremycline
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_TMPFS_INODE64:
tmpfs has historically used only inode numbers as wide as an unsigned
int. In some cases this can cause wraparound, potentially resulting
in multiple files with the same inode number on a single device. This
option makes tmpfs use the full width of ino_t by default, without
needing to specify the inode64 option when mounting.
But if a long-lived tmpfs is to be accessed by 32-bit applications so
ancient that opening a file larger than 2GiB fails with EINVAL, then
the INODE64 config option and inode64 mount option risk operations
failing with EOVERFLOW once 33-bit inode numbers are reached.
To override this configured default, use the inode32 or inode64
option when mounting.
If unsure, say N.
Symbol: TMPFS_INODE64 [=n]
Type : bool
Defined at fs/Kconfig:204
Prompt: Use 64-bit ino_t by default in tmpfs
Depends on: TMPFS [=y] && 64BIT [=y]
Location:
-> File systems
-> Pseudo filesystems
-> Tmpfs virtual memory file system support (former shm fs) (TMPFS [=y])
---
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_TMPFS_INODE64 | 1 +
.../generic/CONFIG_TMPFS_INODE64 | 31 -------------------
2 files changed, 1 insertion(+), 31 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_TMPFS_INODE64
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_TMPFS_INODE64
diff --git a/redhat/configs/common/generic/CONFIG_TMPFS_INODE64 b/redhat/configs/common/generic/CONFIG_TMPFS_INODE64
new file mode 100644
index 000000000000..cce8a2274ff4
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_TMPFS_INODE64
@@ -0,0 +1 @@
+# CONFIG_TMPFS_INODE64 is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_TMPFS_INODE64 b/redhat/configs/pending-common/generic/CONFIG_TMPFS_INODE64
deleted file mode 100644
index a1c19f28cc41..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_TMPFS_INODE64
+++ /dev/null
@@ -1,31 +0,0 @@
-# CONFIG_TMPFS_INODE64:
-#
-# tmpfs has historically used only inode numbers as wide as an unsigned
-# int. In some cases this can cause wraparound, potentially resulting
-# in multiple files with the same inode number on a single device. This
-# option makes tmpfs use the full width of ino_t by default, without
-# needing to specify the inode64 option when mounting.
-#
-# But if a long-lived tmpfs is to be accessed by 32-bit applications so
-# ancient that opening a file larger than 2GiB fails with EINVAL, then
-# the INODE64 config option and inode64 mount option risk operations
-# failing with EOVERFLOW once 33-bit inode numbers are reached.
-#
-# To override this configured default, use the inode32 or inode64
-# option when mounting.
-#
-# If unsure, say N.
-#
-# Symbol: TMPFS_INODE64 [=n]
-# Type : bool
-# Defined at fs/Kconfig:204
-# Prompt: Use 64-bit ino_t by default in tmpfs
-# Depends on: TMPFS [=y] && 64BIT [=y]
-# Location:
-# -> File systems
-# -> Pseudo filesystems
-# -> Tmpfs virtual memory file system support (former shm fs) (TMPFS [=y])
-#
-#
-#
-# CONFIG_TMPFS_INODE64 is not set
--
GitLab
1 day, 16 hours
[OS-BUILD PATCH] New configs in arch/powerpc
by GitLab Bridge on behalf of jeremycline
From: Jeremy Cline <jcline(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_COMPAT:
Enable support for 32bit binaries
Symbol: COMPAT [=n]
Type : bool
Defined at arch/powerpc/Kconfig:268
Depends on: PPC64
Default: y if !CPU_LITTLE_ENDIAN
Selects: COMPAT_BINFMT_ELF
ARCH_WANT_OLD_COMPAT_IPC
COMPAT_OLD_SIGACTION
Cc: kernel-patches(a)redhat.com
---
redhat/configs/common/generic/powerpc/CONFIG_COMPAT | 1 +
.../pending-common/generic/powerpc/CONFIG_COMPAT | 12 ------------
2 files changed, 1 insertion(+), 12 deletions(-)
create mode 100644 redhat/configs/common/generic/powerpc/CONFIG_COMPAT
delete mode 100644 redhat/configs/pending-common/generic/powerpc/CONFIG_COMPAT
diff --git a/redhat/configs/common/generic/powerpc/CONFIG_COMPAT b/redhat/configs/common/generic/powerpc/CONFIG_COMPAT
new file mode 100644
index 000000000000..3e041f1b653b
--- /dev/null
+++ b/redhat/configs/common/generic/powerpc/CONFIG_COMPAT
@@ -0,0 +1 @@
+# CONFIG_COMPAT is not set
diff --git a/redhat/configs/pending-common/generic/powerpc/CONFIG_COMPAT b/redhat/configs/pending-common/generic/powerpc/CONFIG_COMPAT
deleted file mode 100644
index f59088da33db..000000000000
--- a/redhat/configs/pending-common/generic/powerpc/CONFIG_COMPAT
+++ /dev/null
@@ -1,12 +0,0 @@
-# CONFIG_COMPAT:
-#
-# Enable support for 32bit binaries
-#
-# Symbol: COMPAT [=n]
-# Type : bool
-# Defined at arch/powerpc/Kconfig:268
-# Depends on: PPC64
-# Default: y if !CPU_LITTLE_ENDIAN
-# Selects: COMPAT_BINFMT_ELF, ARCH_WANT_OLD_COMPAT_IPC, COMPAT_OLD_SIGACTION
-#
-# CONFIG_COMPAT is not set
--
GitLab
1 day, 17 hours
[OS-BUILD PATCH] [redhat] New configs in mm/Kconfig
by GitLab Bridge on behalf of jeremycline
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_ZSMALLOC_PGTABLE_MAPPING:
By default, zsmalloc uses a copy-based object mapping method to
access allocations that span two pages. However, if a particular
architecture (ex, ARM) performs VM mapping faster than copying,
then you should select this. This causes zsmalloc to use page table
mapping rather than copying for object mapping.
You can check speed with zsmalloc benchmark:
https://github.com/spartacus06/zsmapbench
Symbol: ZSMALLOC_PGTABLE_MAPPING [=n]
Type : bool
Defined at mm/Kconfig:708
Prompt: Use page table mapping to access object in zsmalloc
Depends on: ZSMALLOC [=y]=y
Location:
-> Memory Management options
-> Memory allocator for compressed pages (ZSMALLOC [=y])
---
Signed-off-by: CKI@GitLab <cki-project(a)redhat.com>
---
.../generic/CONFIG_ZSMALLOC_PGTABLE_MAPPING | 1 +
.../generic/CONFIG_ZSMALLOC_PGTABLE_MAPPING | 23 -------------------
2 files changed, 1 insertion(+), 23 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_ZSMALLOC_PGTABLE_MAPPING
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_ZSMALLOC_PGTABLE_MAPPING
diff --git a/redhat/configs/common/generic/CONFIG_ZSMALLOC_PGTABLE_MAPPING b/redhat/configs/common/generic/CONFIG_ZSMALLOC_PGTABLE_MAPPING
new file mode 100644
index 000000000000..502c3e374887
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_ZSMALLOC_PGTABLE_MAPPING
@@ -0,0 +1 @@
+# CONFIG_ZSMALLOC_PGTABLE_MAPPING is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_ZSMALLOC_PGTABLE_MAPPING b/redhat/configs/pending-common/generic/CONFIG_ZSMALLOC_PGTABLE_MAPPING
deleted file mode 100644
index 2f3d89cf6004..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_ZSMALLOC_PGTABLE_MAPPING
+++ /dev/null
@@ -1,23 +0,0 @@
-# CONFIG_ZSMALLOC_PGTABLE_MAPPING:
-#
-# By default, zsmalloc uses a copy-based object mapping method to
-# access allocations that span two pages. However, if a particular
-# architecture (ex, ARM) performs VM mapping faster than copying,
-# then you should select this. This causes zsmalloc to use page table
-# mapping rather than copying for object mapping.
-#
-# You can check speed with zsmalloc benchmark:
-# https://github.com/spartacus06/zsmapbench
-#
-# Symbol: ZSMALLOC_PGTABLE_MAPPING [=n]
-# Type : bool
-# Defined at mm/Kconfig:708
-# Prompt: Use page table mapping to access object in zsmalloc
-# Depends on: ZSMALLOC [=y]=y
-# Location:
-# -> Memory Management options
-# -> Memory allocator for compressed pages (ZSMALLOC [=y])
-#
-#
-#
-# CONFIG_ZSMALLOC_PGTABLE_MAPPING is not set
--
2.26.2
1 day, 17 hours