[OS-BUILD PATCH] [redhat] New configs in lib/Kconfig.kgdb
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_KGDB_HONOUR_BLOCKLIST:
If set to Y the debug core will use the kprobe blocklist to
identify symbols where it is unsafe to set breakpoints.
In particular this disallows instrumentation of functions
called during debug trap handling and thus makes it very
difficult to inadvertently provoke recursive trap handling.
If unsure, say Y.
Symbol: KGDB_HONOUR_BLOCKLIST [=y]
Type : bool
Defined at lib/Kconfig.kgdb:27
Prompt: KGDB: use kprobe blocklist to prohibit unsafe breakpoints
Depends on: KGDB [=y] && HAVE_KPROBES [=y] && MODULES [=y]
Location:
-> Kernel hacking
-> Generic Kernel Debugging Instruments
-> KGDB: kernel debugger (KGDB [=y])
Selects: KPROBES [=y]
---
Cc: Prarit Bhargava <prarit(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../generic/CONFIG_KGDB_HONOUR_BLOCKLIST | 1 +
.../generic/CONFIG_KGDB_HONOUR_BLOCKLIST | 24 -------------------
2 files changed, 1 insertion(+), 24 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_KGDB_HONOUR_BLOCKLIST
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_KGDB_HONOUR_BLOCKLIST
diff --git a/redhat/configs/common/generic/CONFIG_KGDB_HONOUR_BLOCKLIST b/redhat/configs/common/generic/CONFIG_KGDB_HONOUR_BLOCKLIST
new file mode 100644
index 000000000000..7da79f661883
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_KGDB_HONOUR_BLOCKLIST
@@ -0,0 +1 @@
+CONFIG_KGDB_HONOUR_BLOCKLIST=y
diff --git a/redhat/configs/pending-common/generic/CONFIG_KGDB_HONOUR_BLOCKLIST b/redhat/configs/pending-common/generic/CONFIG_KGDB_HONOUR_BLOCKLIST
deleted file mode 100644
index 224aca014283..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_KGDB_HONOUR_BLOCKLIST
+++ /dev/null
@@ -1,24 +0,0 @@
-# CONFIG_KGDB_HONOUR_BLOCKLIST:
-#
-# If set to Y the debug core will use the kprobe blocklist to
-# identify symbols where it is unsafe to set breakpoints.
-# In particular this disallows instrumentation of functions
-# called during debug trap handling and thus makes it very
-# difficult to inadvertently provoke recursive trap handling.
-#
-# If unsure, say Y.
-#
-# Symbol: KGDB_HONOUR_BLOCKLIST [=y]
-# Type : bool
-# Defined at lib/Kconfig.kgdb:27
-# Prompt: KGDB: use kprobe blocklist to prohibit unsafe breakpoints
-# Depends on: KGDB [=y] && HAVE_KPROBES [=y] && MODULES [=y]
-# Location:
-# -> Kernel hacking
-# -> Generic Kernel Debugging Instruments
-# -> KGDB: kernel debugger (KGDB [=y])
-# Selects: KPROBES [=y]
-#
-#
-#
-CONFIG_KGDB_HONOUR_BLOCKLIST=y
--
GitLab
3 years
[OS-BUILD PATCH] [redhat] New configs in arch/powerpc
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_PPC_PROT_SAO_LPAR:
This option adds support for PROT_SAO mappings from userspace
inside LPARs on supported CPUs.
This may cause issues when performing guest migration from
a CPU that supports SAO to one that does not.
If unsure, say N here.
Symbol: PPC_PROT_SAO_LPAR [=n]
Type : bool
Defined at arch/powerpc/Kconfig:863
Prompt: Support PROT_SAO mappings in LPARs
Depends on: PPC_BOOK3S_64 [=y]
Location:
-> Kernel options
---
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_PPC_PROT_SAO_LPAR | 1 +
.../generic/CONFIG_PPC_PROT_SAO_LPAR | 21 -------------------
2 files changed, 1 insertion(+), 21 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_PPC_PROT_SAO_LPAR
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_PPC_PROT_SAO_LPAR
diff --git a/redhat/configs/common/generic/CONFIG_PPC_PROT_SAO_LPAR b/redhat/configs/common/generic/CONFIG_PPC_PROT_SAO_LPAR
new file mode 100644
index 000000000000..bea5ce6ad2b5
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_PPC_PROT_SAO_LPAR
@@ -0,0 +1 @@
+# CONFIG_PPC_PROT_SAO_LPAR is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_PPC_PROT_SAO_LPAR b/redhat/configs/pending-common/generic/CONFIG_PPC_PROT_SAO_LPAR
deleted file mode 100644
index 88471b97ec8d..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_PPC_PROT_SAO_LPAR
+++ /dev/null
@@ -1,21 +0,0 @@
-# CONFIG_PPC_PROT_SAO_LPAR:
-#
-# This option adds support for PROT_SAO mappings from userspace
-# inside LPARs on supported CPUs.
-#
-# This may cause issues when performing guest migration from
-# a CPU that supports SAO to one that does not.
-#
-# If unsure, say N here.
-#
-# Symbol: PPC_PROT_SAO_LPAR [=n]
-# Type : bool
-# Defined at arch/powerpc/Kconfig:863
-# Prompt: Support PROT_SAO mappings in LPARs
-# Depends on: PPC_BOOK3S_64 [=y]
-# Location:
-# -> Kernel options
-#
-#
-#
-# CONFIG_PPC_PROT_SAO_LPAR is not set
--
GitLab
3 years
[OS-BUILD PATCH] [redhat] New configs in arch/powerpc
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_PPC_RTAS_FILTER:
The RTAS syscall API has security issues that could be used to
compromise system integrity. This option enforces restrictions on the
RTAS calls and arguments passed by userspace programs to mitigate
these issues.
Say Y unless you know what you are doing and the filter is causing
problems for you.
Symbol: PPC_RTAS_FILTER [=y]
Type : bool
Defined at arch/powerpc/Kconfig:991
Prompt: Enable filtering of RTAS syscalls
Depends on: PPC_RTAS [=y]
Location:
-> Kernel options
---
Cc: kernel-patches(a)redhat.com
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_PPC_RTAS_FILTER | 1 +
.../generic/CONFIG_PPC_RTAS_FILTER | 21 -------------------
2 files changed, 1 insertion(+), 21 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_PPC_RTAS_FILTER
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_PPC_RTAS_FILTER
diff --git a/redhat/configs/common/generic/CONFIG_PPC_RTAS_FILTER b/redhat/configs/common/generic/CONFIG_PPC_RTAS_FILTER
new file mode 100644
index 000000000000..7470f4d4f0fe
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_PPC_RTAS_FILTER
@@ -0,0 +1 @@
+CONFIG_PPC_RTAS_FILTER=y
diff --git a/redhat/configs/pending-common/generic/CONFIG_PPC_RTAS_FILTER b/redhat/configs/pending-common/generic/CONFIG_PPC_RTAS_FILTER
deleted file mode 100644
index 6105fa8baae5..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_PPC_RTAS_FILTER
+++ /dev/null
@@ -1,21 +0,0 @@
-# CONFIG_PPC_RTAS_FILTER:
-#
-# The RTAS syscall API has security issues that could be used to
-# compromise system integrity. This option enforces restrictions on the
-# RTAS calls and arguments passed by userspace programs to mitigate
-# these issues.
-#
-# Say Y unless you know what you are doing and the filter is causing
-# problems for you.
-#
-# Symbol: PPC_RTAS_FILTER [=y]
-# Type : bool
-# Defined at arch/powerpc/Kconfig:991
-# Prompt: Enable filtering of RTAS syscalls
-# Depends on: PPC_RTAS [=y]
-# Location:
-# -> Kernel options
-#
-#
-#
-CONFIG_PPC_RTAS_FILTER=y
--
GitLab
3 years
[OS-BUILD PATCH] Add git config hook
by GitLab Bridge on behalf of dzickusrh
From: Don Zickus <dzickus(a)redhat.com>
The kernel workflow is adding complexity. Let's hide some of that complexity
behind git aliases. Instead of having the developer manually add them all
the time, add a make command to 'include' kernel aliases.
A new command 'make rh-gitsetup' runs
git config --local --add include.path "../redhat/kernel.gitconfig"
and adds an include to the local repo's .git/config file.
Over time more workflow commands can be added to help developers.
Start with a stub config file.
V5: text cleanups
V4: s/gitconfig/gitsetup
V3: expand comment in kernel.gitconfig
Signed-off-by: Don Zickus <dzickus(a)redhat.com>
---
redhat/Makefile | 6 ++++++
redhat/kernel.gitconfig | 10 ++++++++++
2 files changed, 16 insertions(+)
create mode 100644 redhat/kernel.gitconfig
diff --git a/redhat/Makefile b/redhat/Makefile
index 0118e5b9e2e9..9236fdb1418a 100644
--- a/redhat/Makefile
+++ b/redhat/Makefile
@@ -133,6 +133,10 @@ rh-kabi-dw-check: rh-kabi
@echo "**** End of KABI DWARF-based comparison report ****"
@rm -rf $(KABIDW)/base/$(CURARCH).tmp
+rh-gitsetup:
+ @git config --get include.path | grep -q 'redhat/kernel.gitconfig' || \
+ git config --local --add include.path "../redhat/kernel.gitconfig"
+
rh-configs-commit: rh-configs-prep
@cd $(REDHAT)/configs; VERSION=$(KVERSION) ./generate_all_configs.sh $(FLAVOR) 1; \
./process_configs.sh -z $(PACKAGE_NAME) $(KVERSION) "" $(FLAVOR)
@@ -363,6 +367,7 @@ rh-help:
@echo ' rh-cross-all-rpms - Build RPMs for all supported archs using a cross compiler.'
@echo ''
@echo 'Configuration targets:'
+ @echo ' rh-gitsetup - include redhat/kernel.gitconfig in repo git config'
@echo ' rh-configs - Create RHEL config files in redhat/config/.'
@echo ''
@echo 'For detailed description and full list of targets, run `make rh-full-help`.'
@@ -442,6 +447,7 @@ rh-full-help:
@echo ''
@echo 'Configuration targets:'
+ @echo ' rh-gitsetup - include redhat/kernel.gitconfig in repo git config'
@echo ' rh-configs - Creates config files for RHEL $(RHEL_MAJOR) architectures, cleans them'
@echo ' by running make nonint_oldconfig, and copies them to'
@echo ' redhat/configs/ directory. This is the target to use for a config!'
diff --git a/redhat/kernel.gitconfig b/redhat/kernel.gitconfig
new file mode 100644
index 000000000000..6fd63c7ac1aa
--- /dev/null
+++ b/redhat/kernel.gitconfig
@@ -0,0 +1,10 @@
+# The kernel workflow is growing in complexity. Developers can not always
+# remember all the nuisances involved.
+# This file is meant to aid developers by providing wrappers around some
+# parts of the workflow that everyone can use.
+#
+# Examples include 'aliases' for git-push options or a shortcut for
+# executing workflow checks before pushing.
+#
+# Please do not include personal information here.
+[alias]
--
2.26.2
3 years
[OS-BUILD PATCH] [redhat] New configs in drivers/clk
by GitLab Bridge on behalf of redhat-patchlab
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.
---
---
---
---
Cc: Mark Salter <msalter(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
redhat/configs/common/generic/CONFIG_CLK_GFM_LPASS_SM8250 | 0
redhat/configs/common/generic/CONFIG_COMMON_CLK_FSL_FLEXSPI | 0
redhat/configs/common/generic/CONFIG_SC_CAMCC_7180 | 0
redhat/configs/common/generic/CONFIG_SDX_GCC_55 | 0
4 files changed, 0 insertions(+), 0 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_CLK_GFM_LPASS_SM8250
create mode 100644 redhat/configs/common/generic/CONFIG_COMMON_CLK_FSL_FLEXSPI
create mode 100644 redhat/configs/common/generic/CONFIG_SC_CAMCC_7180
create mode 100644 redhat/configs/common/generic/CONFIG_SDX_GCC_55
diff --git a/redhat/configs/common/generic/CONFIG_CLK_GFM_LPASS_SM8250 b/redhat/configs/common/generic/CONFIG_CLK_GFM_LPASS_SM8250
new file mode 100644
index 000000000000..e69de29bb2d1
diff --git a/redhat/configs/common/generic/CONFIG_COMMON_CLK_FSL_FLEXSPI b/redhat/configs/common/generic/CONFIG_COMMON_CLK_FSL_FLEXSPI
new file mode 100644
index 000000000000..e69de29bb2d1
diff --git a/redhat/configs/common/generic/CONFIG_SC_CAMCC_7180 b/redhat/configs/common/generic/CONFIG_SC_CAMCC_7180
new file mode 100644
index 000000000000..e69de29bb2d1
diff --git a/redhat/configs/common/generic/CONFIG_SDX_GCC_55 b/redhat/configs/common/generic/CONFIG_SDX_GCC_55
new file mode 100644
index 000000000000..e69de29bb2d1
--
GitLab
3 years
Is it acceptable to package non-bootable kernels?
by Sergio Lopez
(This message was originally sent to the Packaging mailing list, where
Jason Tibbitts pointed that this is a restriction requested by the
Kernel team, and it'll be your opinion the one that will prevail here)
Hi,
The document "What can be packaged" from "Fedora Packaging
Guidelines", in the section "Only one kernel package" [1], states that
"Fedora allows only a single kernel package; packages containing
alternate kernels are not allowed in the distribution."
While not explicitly stated there, I suspect (please correct me if I'm
wrong) that statement was written with the idea of preventing
alternate kernels that could be used to boot the system. With this
premise in mind, I was wondering if non-bootable kernels (that is,
kernels in a binary format that's not accepted by a conventional boot
loader) would be accepted for packaging.
I'm asking this because I would like to package "libkrunfw" [2], a
dynamic library that bundles an slightly modified minimalist Linux
kernel. The library doesn't really link against the kernel (in the
sense that it doesn't resolve any symbols nor calls to any of its
code), it just bundles it in a binary format that allows it to be
directly injected in a KVM memory region, so it's quite similar to a
compressed image format, but for a different use case.
"libkrunfw" is consumed by "libkrun" [3], another dynamic library that
allows programs to acquire virtualization-based process isolation
capabilites. The main user of "libkrun" is "crun", when built with
"--with-libkrun", an OCI runtime used by "podman". When all pieces are
in place, users can easily run containers with virtualization-based
isolation by adding some additional flags to the "podman" command
line. I have a COPR repository with pre-built alternative packages as
a demonstration [4].
There are a number of reasons why we can't use the kernel that ships
with Fedora:
- We carry a small number of patches with minor changes that modify
the behavior of the kernel for this particular use case. Without
them, we can't provide an streamlined UX for running isolated
processes.
- We need an aggressive minimalist configuration to reduce the memory
footprint of each container/isolated process.
- We need it to be bundled in a dynamic library, so their contents
are mapped into the process memory, enabling programs to switch
between namespaces without the need to carry the kernel binary with
them. The binary object also needs to be properly aligned to allow
direct injection into the KVM memory region without additional
copies.
Given that "libkrunfw" bundles a kernel image that can't be used for
booting the system, would it be acceptable to package it in Fedora?
Thanks,
Sergio.
[1] https://docs.fedoraproject.org/en-US/packaging-guidelines/what-can-be-pac...
[2] https://github.com/containers/libkrunfw
[3] https://github.com/containers/libkrun
[4] https://copr.fedorainfracloud.org/coprs/slp/crun-krun/
3 years
[OS-BUILD PATCH] [redhat] New configs in sound/soc
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_SND_SOC_INTEL_CATPT:
Enable support for Intel(R) Haswell and Broadwell platforms
with I2S codec present. This is a recommended option.
Say Y or m if you have such device.
If unsure, say N.
Symbol: SND_SOC_INTEL_CATPT [=n]
Type : tristate
Defined at sound/soc/intel/Kconfig:37
Prompt: Haswell and Broadwell
Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_SOC_INTEL_SST_TOPLEVEL [=y] && (ACPI [=y] || COMPILE_TEST [=n]) && DMADEVICES [=y] && SND_DMA_SGBUF [=y]
Location:
-> Device Drivers
-> Sound card support (SOUND [=m])
-> Advanced Linux Sound Architecture (SND [=m])
-> ALSA for SoC audio support (SND_SOC [=m])
-> Intel ASoC SST drivers (SND_SOC_INTEL_SST_TOPLEVEL [=y])
Selects: DW_DMAC_CORE [=y] && SND_SOC_ACPI_INTEL_MATCH [=m]
Selected by [n]:
- SND_SOC_INTEL_HASWELL [=n] && SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_SOC_INTEL_SST_TOPLEVEL [=y]
---
Cc: Jaroslav Kysela <jkysela(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_SND_SOC_INTEL_CATPT | 1 +
.../generic/CONFIG_SND_SOC_INTEL_CATPT | 25 -------------------
2 files changed, 1 insertion(+), 25 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_SND_SOC_INTEL_CATPT
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_SND_SOC_INTEL_CATPT
diff --git a/redhat/configs/common/generic/CONFIG_SND_SOC_INTEL_CATPT b/redhat/configs/common/generic/CONFIG_SND_SOC_INTEL_CATPT
new file mode 100644
index 000000000000..86874a8f75ef
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_SND_SOC_INTEL_CATPT
@@ -0,0 +1 @@
+# CONFIG_SND_SOC_INTEL_CATPT is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_SND_SOC_INTEL_CATPT b/redhat/configs/pending-common/generic/CONFIG_SND_SOC_INTEL_CATPT
deleted file mode 100644
index be7a752dde5c..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_SND_SOC_INTEL_CATPT
+++ /dev/null
@@ -1,25 +0,0 @@
-# CONFIG_SND_SOC_INTEL_CATPT:
-#
-# Enable support for Intel(R) Haswell and Broadwell platforms
-# with I2S codec present. This is a recommended option.
-# Say Y or m if you have such device.
-# If unsure, say N.
-#
-# Symbol: SND_SOC_INTEL_CATPT [=n]
-# Type : tristate
-# Defined at sound/soc/intel/Kconfig:37
-# Prompt: Haswell and Broadwell
-# Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_SOC_INTEL_SST_TOPLEVEL [=y] && (ACPI [=y] || COMPILE_TEST [=n]) && DMADEVICES [=y] && SND_DMA_SGBUF [=y]
-# Location:
-# -> Device Drivers
-# -> Sound card support (SOUND [=m])
-# -> Advanced Linux Sound Architecture (SND [=m])
-# -> ALSA for SoC audio support (SND_SOC [=m])
-# -> Intel ASoC SST drivers (SND_SOC_INTEL_SST_TOPLEVEL [=y])
-# Selects: DW_DMAC_CORE [=y] && SND_SOC_ACPI_INTEL_MATCH [=m]
-# Selected by [n]:
-# - SND_SOC_INTEL_HASWELL [=n] && SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_SOC_INTEL_SST_TOPLEVEL [=y]
-#
-#
-#
-# CONFIG_SND_SOC_INTEL_CATPT is not set
--
GitLab
3 years
[OS-BUILD PATCH] [redhat] New configs in drivers/tty
by GitLab Bridge on behalf of redhat-patchlab
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_SERIAL_BCM63XX:
This enables the driver for the onchip UART core found on
the following chipsets:
BCM33xx (cable modem)
BCM63xx/BCM63xxx (DSL)
BCM68xx (PON)
BCM7xxx (STB) - DOCSIS console
Symbol: SERIAL_BCM63XX [=n]
Type : tristate
Defined at drivers/tty/serial/Kconfig:1117
Prompt: Broadcom BCM63xx/BCM33xx UART support
Depends on: TTY [=y] && HAS_IOMEM [=y] && COMMON_CLK [=y]
Location:
-> Device Drivers
-> Character devices
-> Enable TTY (TTY [=y])
-> Serial drivers
Selects: SERIAL_CORE [=y]
---
Cc: John Linville <linville(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_SERIAL_BCM63XX | 1 +
.../generic/CONFIG_SERIAL_BCM63XX | 25 -------------------
2 files changed, 1 insertion(+), 25 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_SERIAL_BCM63XX
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_SERIAL_BCM63XX
diff --git a/redhat/configs/common/generic/CONFIG_SERIAL_BCM63XX b/redhat/configs/common/generic/CONFIG_SERIAL_BCM63XX
new file mode 100644
index 000000000000..514d69a6db4b
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_SERIAL_BCM63XX
@@ -0,0 +1 @@
+# CONFIG_SERIAL_BCM63XX is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_SERIAL_BCM63XX b/redhat/configs/pending-common/generic/CONFIG_SERIAL_BCM63XX
deleted file mode 100644
index 33db6a7e29ae..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_SERIAL_BCM63XX
+++ /dev/null
@@ -1,25 +0,0 @@
-# CONFIG_SERIAL_BCM63XX:
-#
-# This enables the driver for the onchip UART core found on
-# the following chipsets:
-#
-# BCM33xx (cable modem)
-# BCM63xx/BCM63xxx (DSL)
-# BCM68xx (PON)
-# BCM7xxx (STB) - DOCSIS console
-#
-# Symbol: SERIAL_BCM63XX [=n]
-# Type : tristate
-# Defined at drivers/tty/serial/Kconfig:1117
-# Prompt: Broadcom BCM63xx/BCM33xx UART support
-# Depends on: TTY [=y] && HAS_IOMEM [=y] && COMMON_CLK [=y]
-# Location:
-# -> Device Drivers
-# -> Character devices
-# -> Enable TTY (TTY [=y])
-# -> Serial drivers
-# Selects: SERIAL_CORE [=y]
-#
-#
-#
-# CONFIG_SERIAL_BCM63XX is not set
--
GitLab
3 years
[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
3 years
[OS-BUILD PATCH] [redhat] New configs in mm/Kconfig
by GitLab Bridge on behalf of redhat-patchlab
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_GUP_TEST:
Provides /sys/kernel/debug/gup_test, which in turn provides a way
to make ioctl calls that can launch kernel-based unit tests for
the get_user_pages*() and pin_user_pages*() family of API calls.
These tests include benchmark testing of the _fast variants of
get_user_pages*() and pin_user_pages*(), as well as smoke tests of
the non-_fast variants.
There is also a sub-test that allows running dump_page() on any
of up to eight pages (selected by command line args) within the
range of user-space addresses. These pages are either pinned via
pin_user_pages*(), or pinned via get_user_pages*(), as specified
by other command line arguments.
See tools/testing/selftests/vm/gup_test.c
Symbol: GUP_TEST [=n]
Type : bool
Defined at mm/Kconfig:824
Prompt: Enable infrastructure for get_user_pages()-related unit tests
Depends on: DEBUG_FS [=y]
Location:
-> Memory Management options
---
Cc: Rafael Aquini <aquini(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
redhat/configs/common/generic/CONFIG_GUP_TEST | 1 +
.../pending-common/generic/CONFIG_GUP_TEST | 29 -------------------
2 files changed, 1 insertion(+), 29 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_GUP_TEST
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_GUP_TEST
diff --git a/redhat/configs/common/generic/CONFIG_GUP_TEST b/redhat/configs/common/generic/CONFIG_GUP_TEST
new file mode 100644
index 000000000000..5df4896bb447
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_GUP_TEST
@@ -0,0 +1 @@
+# CONFIG_GUP_TEST is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_GUP_TEST b/redhat/configs/pending-common/generic/CONFIG_GUP_TEST
deleted file mode 100644
index 11570ef11beb..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_GUP_TEST
+++ /dev/null
@@ -1,29 +0,0 @@
-# CONFIG_GUP_TEST:
-#
-# Provides /sys/kernel/debug/gup_test, which in turn provides a way
-# to make ioctl calls that can launch kernel-based unit tests for
-# the get_user_pages*() and pin_user_pages*() family of API calls.
-#
-# These tests include benchmark testing of the _fast variants of
-# get_user_pages*() and pin_user_pages*(), as well as smoke tests of
-# the non-_fast variants.
-#
-# There is also a sub-test that allows running dump_page() on any
-# of up to eight pages (selected by command line args) within the
-# range of user-space addresses. These pages are either pinned via
-# pin_user_pages*(), or pinned via get_user_pages*(), as specified
-# by other command line arguments.
-#
-# See tools/testing/selftests/vm/gup_test.c
-#
-# Symbol: GUP_TEST [=n]
-# Type : bool
-# Defined at mm/Kconfig:824
-# Prompt: Enable infrastructure for get_user_pages()-related unit tests
-# Depends on: DEBUG_FS [=y]
-# Location:
-# -> Memory Management options
-#
-#
-#
-# CONFIG_GUP_TEST is not set
--
GitLab
3 years