[OS-BUILD PATCH] [redhat] New configs in drivers/firmware
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_SMCCC_SOC_ID:
Include support for the SoC bus on the ARM SMCCC firmware based
platforms providing some sysfs information about the SoC variant.
Symbol: ARM_SMCCC_SOC_ID [=y]
Type : bool
Defined at drivers/firmware/smccc/Kconfig:18
Prompt: SoC bus device for the ARM SMCCC SOC_ID
Depends on: HAVE_ARM_SMCCC_DISCOVERY [=y]
Location:
-> Firmware Drivers
Selects: SOC_BUS [=y]
---
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_ARM_SMCCC_SOC_ID | 1 +
.../generic/CONFIG_ARM_SMCCC_SOC_ID | 17 -----------------
2 files changed, 1 insertion(+), 17 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_ARM_SMCCC_SOC_ID
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_ARM_SMCCC_SOC_ID
diff --git a/redhat/configs/common/generic/CONFIG_ARM_SMCCC_SOC_ID b/redhat/configs/common/generic/CONFIG_ARM_SMCCC_SOC_ID
new file mode 100644
index 000000000000..c53e28f0b599
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_ARM_SMCCC_SOC_ID
@@ -0,0 +1 @@
+CONFIG_ARM_SMCCC_SOC_ID=y
diff --git a/redhat/configs/pending-common/generic/CONFIG_ARM_SMCCC_SOC_ID b/redhat/configs/pending-common/generic/CONFIG_ARM_SMCCC_SOC_ID
deleted file mode 100644
index 4e91da8ca0de..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_ARM_SMCCC_SOC_ID
+++ /dev/null
@@ -1,17 +0,0 @@
-# CONFIG_ARM_SMCCC_SOC_ID:
-#
-# Include support for the SoC bus on the ARM SMCCC firmware based
-# platforms providing some sysfs information about the SoC variant.
-#
-# Symbol: ARM_SMCCC_SOC_ID [=y]
-# Type : bool
-# Defined at drivers/firmware/smccc/Kconfig:18
-# Prompt: SoC bus device for the ARM SMCCC SOC_ID
-# Depends on: HAVE_ARM_SMCCC_DISCOVERY [=y]
-# Location:
-# -> Firmware Drivers
-# Selects: SOC_BUS [=y]
-#
-#
-#
-CONFIG_ARM_SMCCC_SOC_ID=y
--
GitLab
3 years, 7 months
[OS-BUILD PATCH] [redhat] New configs in arch/arm64
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_ARCH_KEEMBAY:
This enables support for Intel Movidius SoC code-named Keem Bay.
Symbol: ARCH_KEEMBAY [=n]
Type : bool
Defined at arch/arm64/Kconfig.platforms:139
Prompt: Keem Bay SoC
Location:
-> Platform selection
---
CONFIG_ARCH_SPARX5:
This enables support for the Microchip Sparx5 ARMv8-based
SoC family of TSN-capable gigabit switches.
The SparX-5 Ethernet switch family provides a rich set of
switching features such as advanced TCAM-based VLAN and QoS
processing enabling delivery of differentiated services, and
security through TCAM-based frame processing using versatile
content aware processor (VCAP).
Symbol: ARCH_SPARX5 [=n]
Type : bool
Defined at arch/arm64/Kconfig.platforms:92
Prompt: ARMv8 based Microchip Sparx5 SoC family
Location:
-> Platform selection
Selects: PINCTRL [=y] && DW_APB_TIMER_OF [=n]
---
Cc: Mark Salter <msalter(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_ARCH_KEEMBAY | 1 +
.../configs/common/generic/CONFIG_ARCH_SPARX5 | 1 +
.../generic/CONFIG_ARCH_KEEMBAY | 14 ------------
.../pending-common/generic/CONFIG_ARCH_SPARX5 | 22 -------------------
4 files changed, 2 insertions(+), 36 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_ARCH_KEEMBAY
create mode 100644 redhat/configs/common/generic/CONFIG_ARCH_SPARX5
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_ARCH_KEEMBAY
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_ARCH_SPARX5
diff --git a/redhat/configs/common/generic/CONFIG_ARCH_KEEMBAY b/redhat/configs/common/generic/CONFIG_ARCH_KEEMBAY
new file mode 100644
index 000000000000..08875182cdd8
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_ARCH_KEEMBAY
@@ -0,0 +1 @@
+# CONFIG_ARCH_KEEMBAY is not set
diff --git a/redhat/configs/common/generic/CONFIG_ARCH_SPARX5 b/redhat/configs/common/generic/CONFIG_ARCH_SPARX5
new file mode 100644
index 000000000000..cb416e9915a0
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_ARCH_SPARX5
@@ -0,0 +1 @@
+# CONFIG_ARCH_SPARX5 is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_ARCH_KEEMBAY b/redhat/configs/pending-common/generic/CONFIG_ARCH_KEEMBAY
deleted file mode 100644
index 689aa41294fe..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_ARCH_KEEMBAY
+++ /dev/null
@@ -1,14 +0,0 @@
-# CONFIG_ARCH_KEEMBAY:
-#
-# This enables support for Intel Movidius SoC code-named Keem Bay.
-#
-# Symbol: ARCH_KEEMBAY [=n]
-# Type : bool
-# Defined at arch/arm64/Kconfig.platforms:139
-# Prompt: Keem Bay SoC
-# Location:
-# -> Platform selection
-#
-#
-#
-# CONFIG_ARCH_KEEMBAY is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_ARCH_SPARX5 b/redhat/configs/pending-common/generic/CONFIG_ARCH_SPARX5
deleted file mode 100644
index 69cb4654eeb5..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_ARCH_SPARX5
+++ /dev/null
@@ -1,22 +0,0 @@
-# CONFIG_ARCH_SPARX5:
-#
-# This enables support for the Microchip Sparx5 ARMv8-based
-# SoC family of TSN-capable gigabit switches.
-#
-# The SparX-5 Ethernet switch family provides a rich set of
-# switching features such as advanced TCAM-based VLAN and QoS
-# processing enabling delivery of differentiated services, and
-# security through TCAM-based frame processing using versatile
-# content aware processor (VCAP).
-#
-# Symbol: ARCH_SPARX5 [=n]
-# Type : bool
-# Defined at arch/arm64/Kconfig.platforms:92
-# Prompt: ARMv8 based Microchip Sparx5 SoC family
-# Location:
-# -> Platform selection
-# Selects: PINCTRL [=y] && DW_APB_TIMER_OF [=n]
-#
-#
-#
-# CONFIG_ARCH_SPARX5 is not set
--
GitLab
3 years, 7 months
[OS-BUILD PATCH] Use the configs/generic config for SND_HDA_INTEL
everywhere
by GitLab Bridge on behalf of pbrobinson
From: Peter Robinson <pbrobinson(a)gmail.com>
The SND_HDA_INTEL is actually badly named as it covers HDMI audio in a number
of use cases such as discrete nvidia and amd GPUs on POWER and aarch64. It
may have originally been an Intel only option but now it's basically appears
to be a generic HDMI Audio config option so basically we should enable it
where ever we enable sound, it's enabled as a module already in configs/generic,
so we shouldn't actually need to override it anywhere so remove the other options
they are either the same or do override it.
Signed-off-by: Peter Robinson <pbrobinson(a)gmail.com>
---
redhat/configs/ark/generic/powerpc/CONFIG_SND_HDA_INTEL | 1 -
redhat/configs/fedora/generic/CONFIG_SND_HDA_INTEL | 1 -
redhat/configs/fedora/generic/powerpc/CONFIG_SND_HDA_INTEL | 1 -
redhat/configs/fedora/generic/x86/CONFIG_SND_HDA_INTEL | 1 -
4 files changed, 4 deletions(-)
delete mode 100644 redhat/configs/ark/generic/powerpc/CONFIG_SND_HDA_INTEL
delete mode 100644 redhat/configs/fedora/generic/CONFIG_SND_HDA_INTEL
delete mode 100644 redhat/configs/fedora/generic/powerpc/CONFIG_SND_HDA_INTEL
delete mode 100644 redhat/configs/fedora/generic/x86/CONFIG_SND_HDA_INTEL
diff --git a/redhat/configs/ark/generic/powerpc/CONFIG_SND_HDA_INTEL b/redhat/configs/ark/generic/powerpc/CONFIG_SND_HDA_INTEL
deleted file mode 100644
index 6f057ecfeaaa..000000000000
--- a/redhat/configs/ark/generic/powerpc/CONFIG_SND_HDA_INTEL
+++ /dev/null
@@ -1 +0,0 @@
-# CONFIG_SND_HDA_INTEL is not set
diff --git a/redhat/configs/fedora/generic/CONFIG_SND_HDA_INTEL b/redhat/configs/fedora/generic/CONFIG_SND_HDA_INTEL
deleted file mode 100644
index 6f057ecfeaaa..000000000000
--- a/redhat/configs/fedora/generic/CONFIG_SND_HDA_INTEL
+++ /dev/null
@@ -1 +0,0 @@
-# CONFIG_SND_HDA_INTEL is not set
diff --git a/redhat/configs/fedora/generic/powerpc/CONFIG_SND_HDA_INTEL b/redhat/configs/fedora/generic/powerpc/CONFIG_SND_HDA_INTEL
deleted file mode 100644
index dfe74ea98408..000000000000
--- a/redhat/configs/fedora/generic/powerpc/CONFIG_SND_HDA_INTEL
+++ /dev/null
@@ -1 +0,0 @@
-CONFIG_SND_HDA_INTEL=m
diff --git a/redhat/configs/fedora/generic/x86/CONFIG_SND_HDA_INTEL b/redhat/configs/fedora/generic/x86/CONFIG_SND_HDA_INTEL
deleted file mode 100644
index dfe74ea98408..000000000000
--- a/redhat/configs/fedora/generic/x86/CONFIG_SND_HDA_INTEL
+++ /dev/null
@@ -1 +0,0 @@
-CONFIG_SND_HDA_INTEL=m
--
GitLab
3 years, 7 months
[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_TEST_FPU:
Enable this option to add /sys/kernel/debug/selftest_helpers/test_fpu
which will trigger a sequence of floating point operations. This is used
for self-testing floating point control register setting in
kernel_fpu_begin().
If unsure, say N.
Symbol: TEST_FPU [=n]
Type : tristate
Defined at lib/Kconfig.debug:2317
Prompt: Test floating point operations in kernel space
Depends on: RUNTIME_TESTING_MENU [=y] && X86 [=y] && !KCOV_INSTRUMENT_ALL [=n]
Location:
-> Kernel hacking
-> Kernel Testing and Coverage
-> Runtime Testing (RUNTIME_TESTING_MENU [=y])
---
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
redhat/configs/common/generic/CONFIG_TEST_FPU | 1 +
.../pending-common/generic/CONFIG_TEST_FPU | 22 -------------------
2 files changed, 1 insertion(+), 22 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_TEST_FPU
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_TEST_FPU
diff --git a/redhat/configs/common/generic/CONFIG_TEST_FPU b/redhat/configs/common/generic/CONFIG_TEST_FPU
new file mode 100644
index 000000000000..8091d4abf379
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_TEST_FPU
@@ -0,0 +1 @@
+# CONFIG_TEST_FPU is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_TEST_FPU b/redhat/configs/pending-common/generic/CONFIG_TEST_FPU
deleted file mode 100644
index e8667e1a0a34..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_TEST_FPU
+++ /dev/null
@@ -1,22 +0,0 @@
-# CONFIG_TEST_FPU:
-#
-# Enable this option to add /sys/kernel/debug/selftest_helpers/test_fpu
-# which will trigger a sequence of floating point operations. This is used
-# for self-testing floating point control register setting in
-# kernel_fpu_begin().
-#
-# If unsure, say N.
-#
-# Symbol: TEST_FPU [=n]
-# Type : tristate
-# Defined at lib/Kconfig.debug:2317
-# Prompt: Test floating point operations in kernel space
-# Depends on: RUNTIME_TESTING_MENU [=y] && X86 [=y] && !KCOV_INSTRUMENT_ALL [=n]
-# Location:
-# -> Kernel hacking
-# -> Kernel Testing and Coverage
-# -> Runtime Testing (RUNTIME_TESTING_MENU [=y])
-#
-#
-#
-# CONFIG_TEST_FPU is not set
--
GitLab
3 years, 7 months
[OS-BUILD PATCH] [redhat] New configs in drivers/char
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_HW_RANDOM_BA431:
This driver provides kernel-side support for the Random Number
Generator hardware based on Silex Insight BA431 IP.
To compile this driver as a module, choose M here: the
module will be called ba431-rng.
Symbol: HW_RANDOM_BA431 [=n]
Type : tristate
Defined at drivers/char/hw_random/Kconfig:77
Prompt: Silex Insight BA431 Random Number Generator support
Depends on: HW_RANDOM [=y] && HAS_IOMEM [=y]
Location:
-> Device Drivers
-> Character devices
-> Hardware Random Number Generator Core support (HW_RANDOM [=y])
---
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_HW_RANDOM_BA431 | 1 +
.../generic/CONFIG_HW_RANDOM_BA431 | 21 -------------------
2 files changed, 1 insertion(+), 21 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_HW_RANDOM_BA431
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_HW_RANDOM_BA431
diff --git a/redhat/configs/common/generic/CONFIG_HW_RANDOM_BA431 b/redhat/configs/common/generic/CONFIG_HW_RANDOM_BA431
new file mode 100644
index 000000000000..ccafb50a2a93
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_HW_RANDOM_BA431
@@ -0,0 +1 @@
+# CONFIG_HW_RANDOM_BA431 is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_HW_RANDOM_BA431 b/redhat/configs/pending-common/generic/CONFIG_HW_RANDOM_BA431
deleted file mode 100644
index 0ddc011f3703..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_HW_RANDOM_BA431
+++ /dev/null
@@ -1,21 +0,0 @@
-# CONFIG_HW_RANDOM_BA431:
-#
-# This driver provides kernel-side support for the Random Number
-# Generator hardware based on Silex Insight BA431 IP.
-#
-# To compile this driver as a module, choose M here: the
-# module will be called ba431-rng.
-#
-# Symbol: HW_RANDOM_BA431 [=n]
-# Type : tristate
-# Defined at drivers/char/hw_random/Kconfig:77
-# Prompt: Silex Insight BA431 Random Number Generator support
-# Depends on: HW_RANDOM [=y] && HAS_IOMEM [=y]
-# Location:
-# -> Device Drivers
-# -> Character devices
-# -> Hardware Random Number Generator Core support (HW_RANDOM [=y])
-#
-#
-#
-# CONFIG_HW_RANDOM_BA431 is not set
--
GitLab
3 years, 7 months
❌ FAIL: Test report for kernel (ark)
by CKI Project
Hello,
We ran automated tests on a recent commit from this kernel tree:
Kernel repo: https://gitlab.com/cki-project/kernel-ark.git
Commit: d6389487de36 - [redhat] kernel-5.9.0-0.rc0.20200805git2324d50d051e.1
The results of these automated tests are provided below.
Overall result: FAILED (see details below)
Merge: OK
Compile: FAILED
All kernel binaries, config files, and logs are available for download here:
https://cki-artifacts.s3.us-east-2.amazonaws.com/index.html?prefix=datawa...
We attempted to compile the kernel for multiple architectures, but the compile
failed on one or more architectures:
Source RPM: FAILED (see build-generic.log.xz attachment)
We hope that these logs can help you find the problem quickly. For the full
detail on our testing procedures, please scroll to the bottom of this message.
Please reply to this email if you have any questions about the tests that we
ran or if you have any suggestions on how to make future tests more effective.
,-. ,-.
( C ) ( K ) Continuous
`-',-.`-' Kernel
( I ) Integration
`-'
______________________________________________________________________________
Compile testing
---------------
We tried to create the SRPM package but failed.
3 years, 7 months
[OS-BUILD PATCH] [redhat] New configs in kernel/rcu
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_RCU_REF_SCALE_TEST:
This option provides a kernel module that runs performance tests
useful comparing RCU with various read-side synchronization mechanisms.
The kernel module may be built after the fact on the running kernel to be
tested, if desired.
Say Y here if you want these performance tests built into the kernel.
Say M if you want to build it as a module instead.
Say N if you are unsure.
Symbol: RCU_REF_SCALE_TEST [=n]
Type : tristate
Defined at kernel/rcu/Kconfig.debug:64
Prompt: Scalability tests for read-side synchronization (RCU and others)
Depends on: DEBUG_KERNEL [=y]
Location:
-> Kernel hacking
-> RCU Debugging
Selects: TORTURE_TEST [=n] && SRCU [=y] && TASKS_RCU [=n] && TASKS_RUDE_RCU [=y] && TASKS_TRACE_RCU [=n]
---
Cc: Waiman Long <longman(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_RCU_REF_SCALE_TEST | 1 +
.../generic/CONFIG_RCU_REF_SCALE_TEST | 24 -------------------
2 files changed, 1 insertion(+), 24 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_RCU_REF_SCALE_TEST
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_RCU_REF_SCALE_TEST
diff --git a/redhat/configs/common/generic/CONFIG_RCU_REF_SCALE_TEST b/redhat/configs/common/generic/CONFIG_RCU_REF_SCALE_TEST
new file mode 100644
index 000000000000..50d7d874be7a
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_RCU_REF_SCALE_TEST
@@ -0,0 +1 @@
+# CONFIG_RCU_REF_SCALE_TEST is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_RCU_REF_SCALE_TEST b/redhat/configs/pending-common/generic/CONFIG_RCU_REF_SCALE_TEST
deleted file mode 100644
index f418e9fe4f5e..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_RCU_REF_SCALE_TEST
+++ /dev/null
@@ -1,24 +0,0 @@
-# CONFIG_RCU_REF_SCALE_TEST:
-#
-# This option provides a kernel module that runs performance tests
-# useful comparing RCU with various read-side synchronization mechanisms.
-# The kernel module may be built after the fact on the running kernel to be
-# tested, if desired.
-#
-# Say Y here if you want these performance tests built into the kernel.
-# Say M if you want to build it as a module instead.
-# Say N if you are unsure.
-#
-# Symbol: RCU_REF_SCALE_TEST [=n]
-# Type : tristate
-# Defined at kernel/rcu/Kconfig.debug:64
-# Prompt: Scalability tests for read-side synchronization (RCU and others)
-# Depends on: DEBUG_KERNEL [=y]
-# Location:
-# -> Kernel hacking
-# -> RCU Debugging
-# Selects: TORTURE_TEST [=n] && SRCU [=y] && TASKS_RCU [=n] && TASKS_RUDE_RCU [=y] && TASKS_TRACE_RCU [=n]
-#
-#
-#
-# CONFIG_RCU_REF_SCALE_TEST is not set
--
GitLab
3 years, 7 months
[ARK PATCH] Fixes "acpi: prefer booting with ACPI over DTS" to be
RHEL only
by GitLab Bridge on behalf of pbrobinson
From: Peter Robinson <pbrobinson(a)gmail.com>
The ACPI prefernce is RHEL specific, in Fedora we use upstream defaults so
it doesn't randomly change the expectations as to how certain hardware works
that generally isn't classed as "enterprise". So wrap it in the special RHEL
check as it should be for the ARK kernels.
Signed-off-by: Peter Robinson <pbrobinson(a)gmail.com>
CC: Mark Salter <msalter(a)redhat.com>
---
arch/arm64/kernel/acpi.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/arch/arm64/kernel/acpi.c b/arch/arm64/kernel/acpi.c
index be65df48588f..4c41ad355258 100644
--- a/arch/arm64/kernel/acpi.c
+++ b/arch/arm64/kernel/acpi.c
@@ -40,7 +40,11 @@ int acpi_pci_disabled = 1; /* skip ACPI PCI scan and IRQ initialization */
EXPORT_SYMBOL(acpi_pci_disabled);
static bool param_acpi_off __initdata;
+#ifdef CONFIG_RHEL_DIFFERENCES
static bool param_acpi_on __initdata = true;
+#else
+static bool param_acpi_on __initdata;
+#endif
static bool param_acpi_force __initdata;
static int __init parse_acpi(char *arg)
--
GitLab
3 years, 7 months
[OS-BUILD PATCH] kernel.spec: Remove kernel-keys directory on rpm
erase
by GitLab Bridge on behalf of prarit
From: Prarit Bhargava <prarit(a)redhat.com>
An empty /usr/share/doc/kernel-keys/VR directory is left after executing
an 'rpm -e kernel-core-VR'.
Remove the directory when the rpm is erased.
v2: Only list directory and simplify code (bmeneg)
Signed-off-by: Prarit Bhargava <prarit(a)redhat.com>
Cc: Bruno Meneguele <bmeneg(a)redhat.com>
Cc: "Herton R. Krzesinski" <herton(a)redhat.com>
---
redhat/kernel.spec.template | 7 +------
1 file changed, 1 insertion(+), 6 deletions(-)
diff --git a/redhat/kernel.spec.template b/redhat/kernel.spec.template
index d47c9cce8a0e..3d0723678e96 100644
--- a/redhat/kernel.spec.template
+++ b/redhat/kernel.spec.template
@@ -2601,12 +2601,7 @@ fi
/lib/modules/%{KVERREL}%{?3:+%{3}}/updates\
/lib/modules/%{KVERREL}%{?3:+%{3}}/bls.conf\
/lib/modules/%{KVERREL}%{?3:+%{3}}/weak-updates\
-%{_datadir}/doc/kernel-keys/%{KVERREL}%{?3:+%{3}}/kernel-signing-ca*.cer\
-%ifarch s390x ppc64le\
-%if 0%{!?4:1}\
-%{_datadir}/doc/kernel-keys/%{KVERREL}%{?3:+%{3}}/%{signing_key_filename} \
-%endif\
-%endif\
+%{_datadir}/doc/kernel-keys/%{KVERREL}%{?3:+%{3}}\
%if %{1}\
/lib/modules/%{KVERREL}%{?3:+%{3}}/vdso\
%endif\
--
GitLab
3 years, 7 months
[OS-BUILD PATCH 0/3] Prepare to separate out merge upstream step
by GitLab Bridge on behalf of dzickusrh
From: dzickusrh on gitlab.com
I am trying to modify the workflow to use a single branch for
development as opposed to 'os-build' and 'ark-patches'. The first step
I want to take is to split apart the merge-upstream step and release
step. This makes it easier to convert the merge-upstream step to a
single branch later.
This patchset prepares the scripts to separate the steps by making the
scripts less dependent on 'os-build' and more robust for repeated runs.
And importantly adds a Makefile command that the gitlab-ci.yml can use
too.
The next step is to update the kernel-ark-ci tree with gitlab-ci.yml
changes to utilize these changes. The third step is to actually split
them apart. Finally updating the release steps.
3 years, 7 months