[OS-BUILD PATCH] [redhat] New configs in security/keys
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.
---
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
redhat/configs/common/generic/CONFIG_KEY_NOTIFICATIONS | 0
1 file changed, 0 insertions(+), 0 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_KEY_NOTIFICATIONS
diff --git a/redhat/configs/common/generic/CONFIG_KEY_NOTIFICATIONS b/redhat/configs/common/generic/CONFIG_KEY_NOTIFICATIONS
new file mode 100644
index 000000000000..e69de29bb2d1
--
GitLab
3 weeks, 6 days
[OS-BUILD PATCH] [redhat] New configs in drivers/spi
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_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
1 month
[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_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
1 month
[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
1 month
[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 month
[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 month
[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 month
[OS-BUILD PATCH] [redhat] New configs in drivers/clk
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_ICST:
Supports clocking on ARM Reference designs:
- Integrator/AP and Integrator/CP
- RealView PB1176, EB, PB11MP and PBX
Symbol: ICST [=n]
Type : bool
Defined at drivers/clk/versatile/Kconfig:7
Prompt: Clock driver for ARM Reference designs ICST
Depends on: COMMON_CLK [=y] && (ARCH_INTEGRATOR || ARCH_REALVIEW || ARCH_VERSATILE || ARCH_VEXPRESS [=y] || COMPILE_TEST [=n])
Location:
-> Device Drivers
-> Common Clock Framework
-> Clock driver for ARM Reference designs
Selects: REGMAP_MMIO [=y]
---
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
redhat/configs/common/generic/CONFIG_ICST | 1 +
.../pending-common/generic/CONFIG_ICST | 20 -------------------
2 files changed, 1 insertion(+), 20 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_ICST
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_ICST
diff --git a/redhat/configs/common/generic/CONFIG_ICST b/redhat/configs/common/generic/CONFIG_ICST
new file mode 100644
index 000000000000..2f0728ae9bb8
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_ICST
@@ -0,0 +1 @@
+# CONFIG_ICST is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_ICST b/redhat/configs/pending-common/generic/CONFIG_ICST
deleted file mode 100644
index f1c4cbd99a08..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_ICST
+++ /dev/null
@@ -1,20 +0,0 @@
-# CONFIG_ICST:
-#
-# Supports clocking on ARM Reference designs:
-# - Integrator/AP and Integrator/CP
-# - RealView PB1176, EB, PB11MP and PBX
-#
-# Symbol: ICST [=n]
-# Type : bool
-# Defined at drivers/clk/versatile/Kconfig:7
-# Prompt: Clock driver for ARM Reference designs ICST
-# Depends on: COMMON_CLK [=y] && (ARCH_INTEGRATOR || ARCH_REALVIEW || ARCH_VERSATILE || ARCH_VEXPRESS [=y] || COMPILE_TEST [=n])
-# Location:
-# -> Device Drivers
-# -> Common Clock Framework
-# -> Clock driver for ARM Reference designs
-# Selects: REGMAP_MMIO [=y]
-#
-#
-#
-# CONFIG_ICST is not set
--
2.26.2
1 month
[OS-BUILD PATCH] [redhat] New configs in net/bluetooth
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_BT_MSFTEXT:
This options enables support for the Microsoft defined HCI
vendor extensions.
Symbol: BT_MSFTEXT [=n]
Type : bool
Defined at net/bluetooth/Kconfig:96
Prompt: Enable Microsoft extensions
Depends on: NET [=y] && BT [=m]
Location:
-> Networking support (NET [=y])
-> Bluetooth subsystem support (BT [=m])
---
Signed-off-by: Justin M. Forbes <jforbes(a)fedoraproject.org>
---
redhat/configs/common/generic/CONFIG_BT_MSFTEXT | 1 +
.../pending-common/generic/CONFIG_BT_MSFTEXT | 17 -----------------
2 files changed, 1 insertion(+), 17 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_BT_MSFTEXT
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_BT_MSFTEXT
diff --git a/redhat/configs/common/generic/CONFIG_BT_MSFTEXT b/redhat/configs/common/generic/CONFIG_BT_MSFTEXT
new file mode 100644
index 000000000000..7fae871b2426
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_BT_MSFTEXT
@@ -0,0 +1 @@
+# CONFIG_BT_MSFTEXT is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_BT_MSFTEXT b/redhat/configs/pending-common/generic/CONFIG_BT_MSFTEXT
deleted file mode 100644
index b93c24c93f7f..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_BT_MSFTEXT
+++ /dev/null
@@ -1,17 +0,0 @@
-# CONFIG_BT_MSFTEXT:
-#
-# This options enables support for the Microsoft defined HCI
-# vendor extensions.
-#
-# Symbol: BT_MSFTEXT [=n]
-# Type : bool
-# Defined at net/bluetooth/Kconfig:96
-# Prompt: Enable Microsoft extensions
-# Depends on: NET [=y] && BT [=m]
-# Location:
-# -> Networking support (NET [=y])
-# -> Bluetooth subsystem support (BT [=m])
-#
-#
-#
-# CONFIG_BT_MSFTEXT is not set
--
2.26.2
1 month
[OS-BUILD PATCH] [redhat] New configs in drivers/net/phy
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_BCM54140_PHY:
Support the Broadcom BCM54140 Quad SGMII/QSGMII PHY.
This driver also supports the hardware monitoring of this PHY and
exposes voltage and temperature sensors.
Symbol: BCM54140_PHY [=n]
Type : tristate
Defined at drivers/net/phy/Kconfig:357
Prompt: Broadcom BCM54140 PHY
Depends on: NETDEVICES [=y] && PHYLIB [=y] && (HWMON [=y] || HWMON [=y]=n)
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> PHY Device support and infrastructure (PHYLIB [=y])
Selects: BCM_NET_PHYLIB [=m]
---
CONFIG_MDIO_IPQ4019:
This driver supports the MDIO interface found in Qualcomm
IPQ40xx series Soc-s.
Symbol: MDIO_IPQ4019 [=n]
Type : tristate
Defined at drivers/net/phy/Kconfig:160
Prompt: Qualcomm IPQ4019 MDIO interface support
Depends on: NETDEVICES [=y] && MDIO_DEVICE [=y] && MDIO_BUS [=y] && HAS_IOMEM [=y] && OF_MDIO [=y]
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> MDIO bus device drivers (MDIO_DEVICE [=y])
---
Signed-off-by: Justin M. Forbes <jforbes(a)fedoraproject.org>
---
.../common/generic/CONFIG_BCM54140_PHY | 1 +
.../common/generic/CONFIG_MDIO_IPQ4019 | 1 +
.../generic/CONFIG_BCM54140_PHY | 21 -------------------
.../generic/CONFIG_MDIO_IPQ4019 | 18 ----------------
4 files changed, 2 insertions(+), 39 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_BCM54140_PHY
create mode 100644 redhat/configs/common/generic/CONFIG_MDIO_IPQ4019
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_BCM54140_PHY
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_MDIO_IPQ4019
diff --git a/redhat/configs/common/generic/CONFIG_BCM54140_PHY b/redhat/configs/common/generic/CONFIG_BCM54140_PHY
new file mode 100644
index 000000000000..ebd2ac9225ca
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_BCM54140_PHY
@@ -0,0 +1 @@
+# CONFIG_BCM54140_PHY is not set
diff --git a/redhat/configs/common/generic/CONFIG_MDIO_IPQ4019 b/redhat/configs/common/generic/CONFIG_MDIO_IPQ4019
new file mode 100644
index 000000000000..7bdf4704b651
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_MDIO_IPQ4019
@@ -0,0 +1 @@
+# CONFIG_MDIO_IPQ4019 is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_BCM54140_PHY b/redhat/configs/pending-common/generic/CONFIG_BCM54140_PHY
deleted file mode 100644
index f86e00bfb361..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_BCM54140_PHY
+++ /dev/null
@@ -1,21 +0,0 @@
-# CONFIG_BCM54140_PHY:
-#
-# Support the Broadcom BCM54140 Quad SGMII/QSGMII PHY.
-#
-# This driver also supports the hardware monitoring of this PHY and
-# exposes voltage and temperature sensors.
-#
-# Symbol: BCM54140_PHY [=n]
-# Type : tristate
-# Defined at drivers/net/phy/Kconfig:357
-# Prompt: Broadcom BCM54140 PHY
-# Depends on: NETDEVICES [=y] && PHYLIB [=y] && (HWMON [=y] || HWMON [=y]=n)
-# Location:
-# -> Device Drivers
-# -> Network device support (NETDEVICES [=y])
-# -> PHY Device support and infrastructure (PHYLIB [=y])
-# Selects: BCM_NET_PHYLIB [=m]
-#
-#
-#
-# CONFIG_BCM54140_PHY is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_MDIO_IPQ4019 b/redhat/configs/pending-common/generic/CONFIG_MDIO_IPQ4019
deleted file mode 100644
index e7792d132188..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_MDIO_IPQ4019
+++ /dev/null
@@ -1,18 +0,0 @@
-# CONFIG_MDIO_IPQ4019:
-#
-# This driver supports the MDIO interface found in Qualcomm
-# IPQ40xx series Soc-s.
-#
-# Symbol: MDIO_IPQ4019 [=n]
-# Type : tristate
-# Defined at drivers/net/phy/Kconfig:160
-# Prompt: Qualcomm IPQ4019 MDIO interface support
-# Depends on: NETDEVICES [=y] && MDIO_DEVICE [=y] && MDIO_BUS [=y] && HAS_IOMEM [=y] && OF_MDIO [=y]
-# Location:
-# -> Device Drivers
-# -> Network device support (NETDEVICES [=y])
-# -> MDIO bus device drivers (MDIO_DEVICE [=y])
-#
-#
-#
-# CONFIG_MDIO_IPQ4019 is not set
--
2.26.2
1 month