[OS-BUILD PATCH] Fix branch creation for releases based on tags
by GitLab Bridge on behalf of jeremycline
From: Jeremy Cline <jcline(a)redhat.com>
The release scripts are supposed create a set of branches if the release
is based of a tag rather than a snapshot. davidlt noted on IRC that
branches were missing for recent tags, namely rc3 and rc4. The reason is
that the check for a signed tag expects $UPSTREAM_REF to be the tag.
Resolve $UPSTREAM_REF to a tag (if it exists) prior to verifying the
tag.
Signed-off-by: Jeremy Cline <jcline(a)redhat.com>
---
redhat/scripts/ci/ark-create-release.sh | 2 +-
redhat/scripts/ci/ark-rebase-patches.sh | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/redhat/scripts/ci/ark-create-release.sh b/redhat/scripts/ci/ark-create-release.sh
index fd57e533ddb4..83b102ceb54f 100755
--- a/redhat/scripts/ci/ark-create-release.sh
+++ b/redhat/scripts/ci/ark-create-release.sh
@@ -37,7 +37,7 @@ git checkout os-build
git checkout os-build
./redhat/scripts/ci/ark-update-configs.sh "$UPSTREAM_REF" "$PROJECT_ID"
-if git tag -v "$UPSTREAM_REF" > /dev/null 2>&1; then
+if git tag -v "$(git describe --exact-match "$UPSTREAM_REF")"; then
git checkout -b ark/"$UPSTREAM_REF" ark/patches/"$UPSTREAM_REF"
RELEASE_BRANCHES=" ark/$UPSTREAM_REF ark/patches/$UPSTREAM_REF"
else
diff --git a/redhat/scripts/ci/ark-rebase-patches.sh b/redhat/scripts/ci/ark-rebase-patches.sh
index 2ac22bcba3bd..4a02176bde88 100755
--- a/redhat/scripts/ci/ark-rebase-patches.sh
+++ b/redhat/scripts/ci/ark-rebase-patches.sh
@@ -102,7 +102,7 @@ else
exit 2
fi
-if git tag -v "$UPSTREAM_REF" > /dev/null 2>&1; then
+if git tag -v "$(git describe --exact-match "$UPSTREAM_REF")"; then
printf "Creating branch \"ark/patches/%s\"\n" "$UPSTREAM_REF"
git branch ark/patches/"$UPSTREAM_REF"
printf "Don't forget to run 'git push <remote> ark/patches/%s'\n" "$UPSTREAM_REF"
--
2.26.2
2 years, 7 months
[OS-BUILD PATCH] [redhat] New configs in drivers/bus
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_VEXPRESS_CONFIG:
Platform configuration infrastructure for the ARM Ltd.
Versatile Express.
Symbol: VEXPRESS_CONFIG [=y]
Type : tristate
Defined at drivers/bus/Kconfig:224
Prompt: Versatile Express configuration bus
Depends on: (ARM || ARM64 [=y]) && OF [=y]
Location:
-> Device Drivers
-> Bus devices
Selects: REGMAP [=y]
---
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_VEXPRESS_CONFIG | 1 +
.../generic/CONFIG_VEXPRESS_CONFIG | 18 ------------------
2 files changed, 1 insertion(+), 18 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_VEXPRESS_CONFIG
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_VEXPRESS_CONFIG
diff --git a/redhat/configs/common/generic/CONFIG_VEXPRESS_CONFIG b/redhat/configs/common/generic/CONFIG_VEXPRESS_CONFIG
new file mode 100644
index 000000000000..389660309f56
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_VEXPRESS_CONFIG
@@ -0,0 +1 @@
+CONFIG_VEXPRESS_CONFIG=y
diff --git a/redhat/configs/pending-common/generic/CONFIG_VEXPRESS_CONFIG b/redhat/configs/pending-common/generic/CONFIG_VEXPRESS_CONFIG
deleted file mode 100644
index a2c1cb307e90..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_VEXPRESS_CONFIG
+++ /dev/null
@@ -1,18 +0,0 @@
-# CONFIG_VEXPRESS_CONFIG:
-#
-# Platform configuration infrastructure for the ARM Ltd.
-# Versatile Express.
-#
-# Symbol: VEXPRESS_CONFIG [=y]
-# Type : tristate
-# Defined at drivers/bus/Kconfig:224
-# Prompt: Versatile Express configuration bus
-# Depends on: (ARM || ARM64 [=y]) && OF [=y]
-# Location:
-# -> Device Drivers
-# -> Bus devices
-# Selects: REGMAP [=y]
-#
-#
-#
-CONFIG_VEXPRESS_CONFIG=y
--
2.26.2
2 years, 7 months
[OS-BUILD PATCH] [redhat] New configs in drivers/power
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_POWER_RESET_VEXPRESS:
Power off and reset support for the ARM Ltd. Versatile
Express boards.
Symbol: POWER_RESET_VEXPRESS [=n]
Type : bool
Defined at drivers/power/reset/Kconfig:184
Prompt: ARM Versatile Express power-off and reset driver
Depends on: POWER_RESET [=y] && (ARM || ARM64 [=y]) && VEXPRESS_CONFIG [=y]=y
Location:
-> Device Drivers
-> Board level reset or power off (POWER_RESET [=y])
---
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_POWER_RESET_VEXPRESS | 1 +
.../generic/CONFIG_POWER_RESET_VEXPRESS | 17 -----------------
2 files changed, 1 insertion(+), 17 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_POWER_RESET_VEXPRESS
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_POWER_RESET_VEXPRESS
diff --git a/redhat/configs/common/generic/CONFIG_POWER_RESET_VEXPRESS b/redhat/configs/common/generic/CONFIG_POWER_RESET_VEXPRESS
new file mode 100644
index 000000000000..6b285d5c913a
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_POWER_RESET_VEXPRESS
@@ -0,0 +1 @@
+# CONFIG_POWER_RESET_VEXPRESS is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_POWER_RESET_VEXPRESS b/redhat/configs/pending-common/generic/CONFIG_POWER_RESET_VEXPRESS
deleted file mode 100644
index 80e0a957fff8..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_POWER_RESET_VEXPRESS
+++ /dev/null
@@ -1,17 +0,0 @@
-# CONFIG_POWER_RESET_VEXPRESS:
-#
-# Power off and reset support for the ARM Ltd. Versatile
-# Express boards.
-#
-# Symbol: POWER_RESET_VEXPRESS [=n]
-# Type : bool
-# Defined at drivers/power/reset/Kconfig:184
-# Prompt: ARM Versatile Express power-off and reset driver
-# Depends on: POWER_RESET [=y] && (ARM || ARM64 [=y]) && VEXPRESS_CONFIG [=y]=y
-# Location:
-# -> Device Drivers
-# -> Board level reset or power off (POWER_RESET [=y])
-#
-#
-#
-# CONFIG_POWER_RESET_VEXPRESS is not set
--
2.26.2
2 years, 8 months
[OS-BUILD PATCH] [redhat] New configs in arch/arm64
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_ARM64_BTI:
Branch Target Identification (part of the ARMv8.5 Extensions)
provides a mechanism to limit the set of locations to which computed
branch instructions such as BR or BLR can jump.
To make use of BTI on CPUs that support it, say Y.
BTI is intended to provide complementary protection to other control
flow integrity protection mechanisms, such as the Pointer
authentication mechanism provided as part of the ARMv8.3 Extensions.
For this reason, it does not make sense to enable this option without
also enabling support for pointer authentication. Thus, when
enabling this option you should also select ARM64_PTR_AUTH=y.
Userspace binaries must also be specifically compiled to make use of
this mechanism. If you say N here or the hardware does not support
BTI, such binaries can still run, but you get no additional
enforcement of branch destinations.
Symbol: ARM64_BTI [=y]
Type : bool
Defined at arch/arm64/Kconfig:1594
Prompt: Branch Target Identification support
Location:
-> Kernel Features
-> ARMv8.5 architectural features
---
Cc: Mark Salter <msalter(a)redhat.com>
Signed-off-by: CKI@GitLab <cki-project(a)redhat.com>
---
.../configs/common/generic/CONFIG_ARM64_BTI | 1 +
.../pending-common/generic/CONFIG_ARM64_BTI | 31 -------------------
2 files changed, 1 insertion(+), 31 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_ARM64_BTI
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_ARM64_BTI
diff --git a/redhat/configs/common/generic/CONFIG_ARM64_BTI b/redhat/configs/common/generic/CONFIG_ARM64_BTI
new file mode 100644
index 000000000000..fb0274de0d49
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_ARM64_BTI
@@ -0,0 +1 @@
+CONFIG_ARM64_BTI=y
diff --git a/redhat/configs/pending-common/generic/CONFIG_ARM64_BTI b/redhat/configs/pending-common/generic/CONFIG_ARM64_BTI
deleted file mode 100644
index 5af4d535b648..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_ARM64_BTI
+++ /dev/null
@@ -1,31 +0,0 @@
-# CONFIG_ARM64_BTI:
-#
-# Branch Target Identification (part of the ARMv8.5 Extensions)
-# provides a mechanism to limit the set of locations to which computed
-# branch instructions such as BR or BLR can jump.
-#
-# To make use of BTI on CPUs that support it, say Y.
-#
-# BTI is intended to provide complementary protection to other control
-# flow integrity protection mechanisms, such as the Pointer
-# authentication mechanism provided as part of the ARMv8.3 Extensions.
-# For this reason, it does not make sense to enable this option without
-# also enabling support for pointer authentication. Thus, when
-# enabling this option you should also select ARM64_PTR_AUTH=y.
-#
-# Userspace binaries must also be specifically compiled to make use of
-# this mechanism. If you say N here or the hardware does not support
-# BTI, such binaries can still run, but you get no additional
-# enforcement of branch destinations.
-#
-# Symbol: ARM64_BTI [=y]
-# Type : bool
-# Defined at arch/arm64/Kconfig:1594
-# Prompt: Branch Target Identification support
-# Location:
-# -> Kernel Features
-# -> ARMv8.5 architectural features
-#
-#
-#
-CONFIG_ARM64_BTI=y
--
2.26.2
2 years, 8 months
[OS-BUILD PATCH] [redhat] New configs in drivers/watchdog
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_ARM_SMC_WATCHDOG:
Say Y here to include support for a watchdog timer
implemented by the EL3 Secure Monitor on ARM platforms.
Requires firmware support.
To compile this driver as a module, choose M here: the
module will be called arm_smc_wdt.
Symbol: ARM_SMC_WATCHDOG [=n]
Type : tristate
Defined at drivers/watchdog/Kconfig:871
Prompt: ARM Secure Monitor Call based watchdog support
Depends on: WATCHDOG [=y] && (ARM || ARM64 [=y]) && OF [=y] && HAVE_ARM_SMCCC [=y]
Location:
-> Device Drivers
-> Watchdog Timer Support (WATCHDOG [=y])
Selects: WATCHDOG_CORE [=y]
---
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_ARM_SMC_WATCHDOG | 1 +
.../generic/CONFIG_ARM_SMC_WATCHDOG | 21 -------------------
2 files changed, 1 insertion(+), 21 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_ARM_SMC_WATCHDOG
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_ARM_SMC_WATCHDOG
diff --git a/redhat/configs/common/generic/CONFIG_ARM_SMC_WATCHDOG b/redhat/configs/common/generic/CONFIG_ARM_SMC_WATCHDOG
new file mode 100644
index 000000000000..5292578ce994
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_ARM_SMC_WATCHDOG
@@ -0,0 +1 @@
+# CONFIG_ARM_SMC_WATCHDOG is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_ARM_SMC_WATCHDOG b/redhat/configs/pending-common/generic/CONFIG_ARM_SMC_WATCHDOG
deleted file mode 100644
index af24ce5fab9c..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_ARM_SMC_WATCHDOG
+++ /dev/null
@@ -1,21 +0,0 @@
-# CONFIG_ARM_SMC_WATCHDOG:
-#
-# Say Y here to include support for a watchdog timer
-# implemented by the EL3 Secure Monitor on ARM platforms.
-# Requires firmware support.
-# To compile this driver as a module, choose M here: the
-# module will be called arm_smc_wdt.
-#
-# Symbol: ARM_SMC_WATCHDOG [=n]
-# Type : tristate
-# Defined at drivers/watchdog/Kconfig:871
-# Prompt: ARM Secure Monitor Call based watchdog support
-# Depends on: WATCHDOG [=y] && (ARM || ARM64 [=y]) && OF [=y] && HAVE_ARM_SMCCC [=y]
-# Location:
-# -> Device Drivers
-# -> Watchdog Timer Support (WATCHDOG [=y])
-# Selects: WATCHDOG_CORE [=y]
-#
-#
-#
-# CONFIG_ARM_SMC_WATCHDOG is not set
--
2.26.2
2 years, 8 months
[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
2 years, 8 months
[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
2 years, 8 months
[OS-BUILD PATCH] [redhat] New configs in drivers/input
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_INPUT_IQS269A:
Say Y to enable support for the Azoteq IQS269A capacitive
touch controller.
To compile this driver as a module, choose M here: the
module will be called iqs269a.
Symbol: INPUT_IQS269A [=n]
Type : tristate
Defined at drivers/input/misc/Kconfig:721
Prompt: Azoteq IQS269A capacitive touch controller
Depends on: !UML && INPUT [=y] && INPUT_MISC [=y] && I2C [=y]
Location:
-> Device Drivers
-> Input device support
-> Generic input layer (needed for keyboard, mouse, ...) (INPUT [=y])
-> Miscellaneous devices (INPUT_MISC [=y])
Selects: REGMAP_I2C [=m]
---
CONFIG_TOUCHSCREEN_CY8CTMA140:
Say Y here if you have a Cypress CY8CTMA140 capacitive
touchscreen also just known as "TMA140"
If unsure, say N.
To compile this driver as a module, choose M here: the
module will be called cy8ctma140.
Symbol: TOUCHSCREEN_CY8CTMA140 [=n]
Type : tristate
Defined at drivers/input/touchscreen/Kconfig:204
Prompt: cy8ctma140 touchscreen
Depends on: !UML && INPUT [=y] && INPUT_TOUCHSCREEN [=y] && I2C [=y]
Location:
-> Device Drivers
-> Input device support
-> Generic input layer (needed for keyboard, mouse, ...) (INPUT [=y])
-> Touchscreens (INPUT_TOUCHSCREEN [=y])
---
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_INPUT_IQS269A | 1 +
.../generic/CONFIG_TOUCHSCREEN_CY8CTMA140 | 1 +
.../generic/CONFIG_INPUT_IQS269A | 23 ------------------
.../generic/CONFIG_TOUCHSCREEN_CY8CTMA140 | 24 -------------------
4 files changed, 2 insertions(+), 47 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_INPUT_IQS269A
create mode 100644 redhat/configs/common/generic/CONFIG_TOUCHSCREEN_CY8CTMA140
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_INPUT_IQS269A
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_TOUCHSCREEN_CY8CTMA140
diff --git a/redhat/configs/common/generic/CONFIG_INPUT_IQS269A b/redhat/configs/common/generic/CONFIG_INPUT_IQS269A
new file mode 100644
index 000000000000..8b78e198494a
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_INPUT_IQS269A
@@ -0,0 +1 @@
+# CONFIG_INPUT_IQS269A is not set
diff --git a/redhat/configs/common/generic/CONFIG_TOUCHSCREEN_CY8CTMA140 b/redhat/configs/common/generic/CONFIG_TOUCHSCREEN_CY8CTMA140
new file mode 100644
index 000000000000..fa03c444e54b
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_TOUCHSCREEN_CY8CTMA140
@@ -0,0 +1 @@
+# CONFIG_TOUCHSCREEN_CY8CTMA140 is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_INPUT_IQS269A b/redhat/configs/pending-common/generic/CONFIG_INPUT_IQS269A
deleted file mode 100644
index 445a42fa0119..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_INPUT_IQS269A
+++ /dev/null
@@ -1,23 +0,0 @@
-# CONFIG_INPUT_IQS269A:
-#
-# Say Y to enable support for the Azoteq IQS269A capacitive
-# touch controller.
-#
-# To compile this driver as a module, choose M here: the
-# module will be called iqs269a.
-#
-# Symbol: INPUT_IQS269A [=n]
-# Type : tristate
-# Defined at drivers/input/misc/Kconfig:721
-# Prompt: Azoteq IQS269A capacitive touch controller
-# Depends on: !UML && INPUT [=y] && INPUT_MISC [=y] && I2C [=y]
-# Location:
-# -> Device Drivers
-# -> Input device support
-# -> Generic input layer (needed for keyboard, mouse, ...) (INPUT [=y])
-# -> Miscellaneous devices (INPUT_MISC [=y])
-# Selects: REGMAP_I2C [=m]
-#
-#
-#
-# CONFIG_INPUT_IQS269A is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_TOUCHSCREEN_CY8CTMA140 b/redhat/configs/pending-common/generic/CONFIG_TOUCHSCREEN_CY8CTMA140
deleted file mode 100644
index bb0283fcabba..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_TOUCHSCREEN_CY8CTMA140
+++ /dev/null
@@ -1,24 +0,0 @@
-# CONFIG_TOUCHSCREEN_CY8CTMA140:
-#
-# Say Y here if you have a Cypress CY8CTMA140 capacitive
-# touchscreen also just known as "TMA140"
-#
-# If unsure, say N.
-#
-# To compile this driver as a module, choose M here: the
-# module will be called cy8ctma140.
-#
-# Symbol: TOUCHSCREEN_CY8CTMA140 [=n]
-# Type : tristate
-# Defined at drivers/input/touchscreen/Kconfig:204
-# Prompt: cy8ctma140 touchscreen
-# Depends on: !UML && INPUT [=y] && INPUT_TOUCHSCREEN [=y] && I2C [=y]
-# Location:
-# -> Device Drivers
-# -> Input device support
-# -> Generic input layer (needed for keyboard, mouse, ...) (INPUT [=y])
-# -> Touchscreens (INPUT_TOUCHSCREEN [=y])
-#
-#
-#
-# CONFIG_TOUCHSCREEN_CY8CTMA140 is not set
--
2.27.0
2 years, 8 months
[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
2 years, 8 months