[OS-BUILD PATCH] Keep VIRTIO_CONSOLE on s390x available.
by Jakub Cajka (via Email Bridge)
From: Jakub Čajka <jcajka(a)redhat.com>
Keep VIRTIO_CONSOLE on s390x available.
This regression has been hit in the CoreOS pipeline as it utilizes
it to gather build logs from build VMs during build of the CoreOS.
Fixes RHBZ1917575
diff a/redhat/configs/pending-common/generic/s390x/CONFIG_VIRTIO_CONSOLE b/redhat/configs/pending-common/generic/s390x/CONFIG_VIRTIO_CONSOLE
--- a/redhat/configs/pending-common/generic/s390x/CONFIG_VIRTIO_CONSOLE
+++ /dev/null
@@ -1 +0,0 @@
-# CONFIG_VIRTIO_CONSOLE is not set
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/873
20 minutes
[OS-BUILD PATCH] Turn off CONFIG_VIRTIO_CONSOLE for s390x zfcpdump
by Justin Forbes (via Email Bridge)
From: Justin M. Forbes <jforbes(a)fedoraproject.org>
Turn off CONFIG_VIRTIO_CONSOLE for s390x zfcpdump
Upstream commit 9f30eb29c514589e16f2999ea070598583d1f6ec changed
VIRTIO_CONSOLE from depending on VIRTIO to selecting VIRTIO. This made
it possible to build in the console with virtio drivers being modular.
Before this change, VIRTIO_CONSOLE status did not matter for the
zfcpdump kernel, because VIRTIO which it depends on was turned off.
After that change, having VIRTIO_CONSOLE on will select VIRTIO and turn
on those drivers as modules. This really sets things back to the way
they were.
Signed-off-by: Justin M. Forbes <jforbes(a)fedoraproject.org>
diff a/redhat/configs/common/generic/s390x/zfcpdump/CONFIG_VIRTIO_CONSOLE b/redhat/configs/common/generic/s390x/zfcpdump/CONFIG_VIRTIO_CONSOLE
--- /dev/null
+++ b/redhat/configs/common/generic/s390x/zfcpdump/CONFIG_VIRTIO_CONSOLE
@@ -0,0 +1 @@
+# CONFIG_VIRTIO_CONSOLE is not set
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/874
24 minutes
[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
4 hours, 21 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
18 hours, 27 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, 18 hours
[OS-BUILD PATCH] Bluetooth: L2CAP: Try harder to accept device not
knowing
options
by Bastien Nocera (via Email Bridge)
From: Bastien Nocera <hadess(a)hadess.net>
Bluetooth: L2CAP: Try harder to accept device not knowing options
The current implementation of L2CAP options negotiation will continue
the negotiation when a device responds with L2CAP_CONF_UNACCEPT ("unaccepted
options"), but not when the device replies with L2CAP_CONF_UNKNOWN ("unknown
options").
Trying to continue the negotiation without ERTM support will allow
Bluetooth-capable XBox One controllers (notably models 1708 and 1797)
to connect.
btmon before patch:
> ACL Data RX: Handle 256 flags 0x02 dlen 16 #64 [hci0] 59.182702
L2CAP: Connection Response (0x03) ident 2 len 8
Destination CID: 64
Source CID: 64
Result: Connection successful (0x0000)
Status: No further information available (0x0000)
< ACL Data TX: Handle 256 flags 0x00 dlen 23 #65 [hci0] 59.182744
L2CAP: Configure Request (0x04) ident 3 len 15
Destination CID: 64
Flags: 0x0000
Option: Retransmission and Flow Control (0x04) [mandatory]
Mode: Basic (0x00)
TX window size: 0
Max transmit: 0
Retransmission timeout: 0
Monitor timeout: 0
Maximum PDU size: 0
> ACL Data RX: Handle 256 flags 0x02 dlen 16 #66 [hci0] 59.183948
L2CAP: Configure Request (0x04) ident 1 len 8
Destination CID: 64
Flags: 0x0000
Option: Maximum Transmission Unit (0x01) [mandatory]
MTU: 1480
< ACL Data TX: Handle 256 flags 0x00 dlen 18 #67 [hci0] 59.183994
L2CAP: Configure Response (0x05) ident 1 len 10
Source CID: 64
Flags: 0x0000
Result: Success (0x0000)
Option: Maximum Transmission Unit (0x01) [mandatory]
MTU: 1480
> ACL Data RX: Handle 256 flags 0x02 dlen 15 #69 [hci0] 59.187676
L2CAP: Configure Response (0x05) ident 3 len 7
Source CID: 64
Flags: 0x0000
Result: Failure - unknown options (0x0003)
04 .
< ACL Data TX: Handle 256 flags 0x00 dlen 12 #70 [hci0] 59.187722
L2CAP: Disconnection Request (0x06) ident 4 len 4
Destination CID: 64
Source CID: 64
> ACL Data RX: Handle 256 flags 0x02 dlen 12 #73 [hci0] 59.192714
L2CAP: Disconnection Response (0x07) ident 4 len 4
Destination CID: 64
Source CID: 64
btmon after patch:
> ACL Data RX: Handle 256 flags 0x02 dlen 16 #248 [hci0] 103.502970
L2CAP: Connection Response (0x03) ident 5 len 8
Destination CID: 65
Source CID: 65
Result: Connection pending (0x0001)
Status: No further information available (0x0000)
> ACL Data RX: Handle 256 flags 0x02 dlen 16 #249 [hci0] 103.504184
L2CAP: Connection Response (0x03) ident 5 len 8
Destination CID: 65
Source CID: 65
Result: Connection successful (0x0000)
Status: No further information available (0x0000)
< ACL Data TX: Handle 256 flags 0x00 dlen 23 #250 [hci0] 103.504398
L2CAP: Configure Request (0x04) ident 6 len 15
Destination CID: 65
Flags: 0x0000
Option: Retransmission and Flow Control (0x04) [mandatory]
Mode: Basic (0x00)
TX window size: 0
Max transmit: 0
Retransmission timeout: 0
Monitor timeout: 0
Maximum PDU size: 0
> ACL Data RX: Handle 256 flags 0x02 dlen 16 #251 [hci0] 103.505472
L2CAP: Configure Request (0x04) ident 3 len 8
Destination CID: 65
Flags: 0x0000
Option: Maximum Transmission Unit (0x01) [mandatory]
MTU: 1480
< ACL Data TX: Handle 256 flags 0x00 dlen 18 #252 [hci0] 103.505689
L2CAP: Configure Response (0x05) ident 3 len 10
Source CID: 65
Flags: 0x0000
Result: Success (0x0000)
Option: Maximum Transmission Unit (0x01) [mandatory]
MTU: 1480
> ACL Data RX: Handle 256 flags 0x02 dlen 15 #254 [hci0] 103.509165
L2CAP: Configure Response (0x05) ident 6 len 7
Source CID: 65
Flags: 0x0000
Result: Failure - unknown options (0x0003)
04 .
< ACL Data TX: Handle 256 flags 0x00 dlen 12 #255 [hci0] 103.509426
L2CAP: Configure Request (0x04) ident 7 len 4
Destination CID: 65
Flags: 0x0000
< ACL Data TX: Handle 256 flags 0x00 dlen 12 #257 [hci0] 103.511870
L2CAP: Connection Request (0x02) ident 8 len 4
PSM: 1 (0x0001)
Source CID: 66
> ACL Data RX: Handle 256 flags 0x02 dlen 14 #259 [hci0] 103.514121
L2CAP: Configure Response (0x05) ident 7 len 6
Source CID: 65
Flags: 0x0000
Result: Success (0x0000)
Upstream Status: bluetooth/bluetooth-next.git
(cherry picked from commit 98d2c3e1731007acf03addf83c863df6694beb95)
Signed-off-by: Bastien Nocera <hadess(a)hadess.net>
Signed-off-by: Florian Dollinger <dollinger.florian(a)gmx.de>
Co-developed-by: Florian Dollinger <dollinger.florian(a)gmx.de>
Reviewed-by: Luiz Augusto Von Dentz <luiz.von.dentz(a)intel.com>
Signed-off-by: Marcel Holtmann <marcel(a)holtmann.org>
diff a/net/bluetooth/l2cap_core.c b/net/bluetooth/l2cap_core.c
--- a/net/bluetooth/l2cap_core.c
+++ b/net/bluetooth/l2cap_core.c
@@ -4519,6 +4519,7 @@ static inline int l2cap_config_rsp(struct l2cap_conn *conn,
}
goto done;
+ case L2CAP_CONF_UNKNOWN:
case L2CAP_CONF_UNACCEPT:
if (chan->num_conf_rsp <= L2CAP_CONF_MAX_CONF_RSP) {
char req[64];
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/872
1 day, 23 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, 23 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, 23 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, 23 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
2 days