[OS-BUILD PATCH 0/14] 5.11 acpi cleanup
by GitLab Bridge on behalf of pbrobinson
From: pbrobinson on gitlab.com
Clean up the duplicated ACPI options across Fedora and ARK kernels. The
two architectures supported are aarc64/x86. Putting these options in
common/generic and common/debug doesn't affect non ACPI architectures
due to CONFIG_ACPI and associated Kconfig deps. The first big commit
doesn't change anything just moves the duplicated options to common/ and
removes the dupes.
From there each of the patches are documented, some remove dead options,
some adjust things like ACPI_EC_DEBUGFS that make sense for security and
so platforms aren't accidentally bricked. There's a couple that change
ark/aarch64 with appropriate maintainers cc:ed and really just bring it
inline with other arches, and finally there's a few minor Fedora tweaks
with Justin cc:ed in.
3 years, 3 months
✅ PASS: Test report for kernel 5.10.6-200.fc33 (fedora-33)
by CKI Project
Hello,
We ran automated tests on the following kernel build:
Kernel package: kernel-5.10.6-200.fc33
Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=59458893
The results of these automated tests are provided below.
Overall result: PASSED
Tests: OK
All kernel binaries, config files, and logs are available for download here:
https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?pre...
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.
For the full detail on our testing procedures, please scroll to the bottom of
this message.
,-. ,-.
( C ) ( K ) Continuous
`-',-.`-' Kernel
( I ) Integration
`-'
______________________________________________________________________________
Hardware testing
----------------
We booted each kernel and ran the following tests:
aarch64:
Host 1:
✅ Boot test
✅ stress: stress-ng
🚧 ✅ xfstests - ext4
🚧 ✅ xfstests - xfs
🚧 ✅ xfstests - btrfs
🚧 ✅ Storage blktests
🚧 ✅ Storage block - filesystem fio test
🚧 ✅ Storage block - queue scheduler test
🚧 ✅ Storage nvme - tcp
🚧 ✅ Storage: swraid mdadm raid_module test
Host 2:
✅ Boot test
✅ ACPI table test
✅ LTP
✅ Loopdev Sanity
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
🚧 ✅ CIFS Connectathon
🚧 ✅ Ethernet drivers sanity
ppc64le:
Host 1:
✅ Boot test
🚧 ✅ xfstests - ext4
🚧 ✅ xfstests - xfs
🚧 ✅ xfstests - btrfs
🚧 ✅ Storage blktests
🚧 ✅ Storage block - filesystem fio test
🚧 ✅ Storage block - queue scheduler test
🚧 ✅ Storage nvme - tcp
🚧 ✅ Storage: swraid mdadm raid_module test
Host 2:
⚡ Internal infrastructure issues prevented one or more tests (marked
with ⚡⚡⚡) from running on this architecture.
This is not the fault of the kernel that was tested.
⚡⚡⚡ Boot test
⚡⚡⚡ LTP
⚡⚡⚡ Loopdev Sanity
⚡⚡⚡ Memory: fork_mem
⚡⚡⚡ Memory function: memfd_create
⚡⚡⚡ AMTU (Abstract Machine Test Utility)
🚧 ⚡⚡⚡ CIFS Connectathon
🚧 ⚡⚡⚡ Ethernet drivers sanity
Host 3:
⚡ Internal infrastructure issues prevented one or more tests (marked
with ⚡⚡⚡) from running on this architecture.
This is not the fault of the kernel that was tested.
⚡⚡⚡ Boot test
⚡⚡⚡ LTP
⚡⚡⚡ Loopdev Sanity
⚡⚡⚡ Memory: fork_mem
⚡⚡⚡ Memory function: memfd_create
⚡⚡⚡ AMTU (Abstract Machine Test Utility)
🚧 ⚡⚡⚡ CIFS Connectathon
🚧 ⚡⚡⚡ Ethernet drivers sanity
Host 4:
✅ Boot test
✅ LTP
✅ Loopdev Sanity
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
🚧 ✅ CIFS Connectathon
🚧 ✅ Ethernet drivers sanity
s390x:
Host 1:
✅ Boot test
✅ LTP
✅ Loopdev Sanity
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
🚧 ✅ CIFS Connectathon
🚧 ✅ Ethernet drivers sanity
Host 2:
✅ Boot test
✅ stress: stress-ng
🚧 ✅ Storage blktests
🚧 ❌ Storage nvme - tcp
🚧 ✅ Storage: swraid mdadm raid_module test
Host 3:
✅ Boot test
✅ kdump - sysrq-c
x86_64:
Host 1:
✅ Boot test
✅ stress: stress-ng
🚧 ✅ xfstests - ext4
🚧 ✅ xfstests - xfs
🚧 ✅ xfstests - btrfs
🚧 ✅ xfstests - nfsv4.2
🚧 ✅ xfstests - cifsv3.11
🚧 ✅ Storage blktests
🚧 ✅ Storage block - filesystem fio test
🚧 ✅ Storage block - queue scheduler test
🚧 ✅ Storage nvme - tcp
🚧 ✅ Storage: swraid mdadm raid_module test
Host 2:
✅ Boot test
✅ ACPI table test
✅ LTP
✅ Loopdev Sanity
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
🚧 ✅ CIFS Connectathon
🚧 ✅ Ethernet drivers sanity
Host 3:
✅ Boot test
🚧 ✅ kdump - sysrq-c
Test sources: https://gitlab.com/cki-project/kernel-tests
💚 Pull requests are welcome for new tests or improvements to existing tests!
Aborted tests
-------------
Tests that didn't complete running successfully are marked with ⚡⚡⚡.
If this was caused by an infrastructure issue, we try to mark that
explicitly in the report.
Waived tests
------------
If the test run included waived tests, they are marked with 🚧. Such tests are
executed but their results are not taken into account. Tests are waived when
their results are not reliable enough, e.g. when they're just introduced or are
being fixed.
Testing timeout
---------------
We aim to provide a report within reasonable timeframe. Tests that haven't
finished running yet are marked with ⏱.
3 years, 3 months
[OS-BUILD PATCH] Enable the vkms module in Fedora
by GitLab Bridge on behalf of jeremycline
From: Jeremy Cline <jcline(a)redhat.com>
This is built as a module on RHEL and is useful for testing and for
running X (or similar) on headless machines.
Signed-off-by: Jeremy Cline <jcline(a)redhat.com>
---
redhat/configs/fedora/generic/CONFIG_DRM_VKMS | 1 -
1 file changed, 1 deletion(-)
delete mode 100644 redhat/configs/fedora/generic/CONFIG_DRM_VKMS
diff --git a/redhat/configs/fedora/generic/CONFIG_DRM_VKMS b/redhat/configs/fedora/generic/CONFIG_DRM_VKMS
deleted file mode 100644
index 36903b31ce38..000000000000
--- a/redhat/configs/fedora/generic/CONFIG_DRM_VKMS
+++ /dev/null
@@ -1 +0,0 @@
-# CONFIG_DRM_VKMS is not set
--
GitLab
3 years, 3 months
[OS-BUILD PATCH] [redhat] New configs in drivers/hwmon
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_SENSORS_CORSAIR_PSU:
If you say yes here you get support for Corsair PSUs with a HID
interface.
Currently this driver supports the (RM/HX)550i, (RM/HX)650i,
(RM/HX)750i, (RM/HX)850i, (RM/HX)1000i and HX1200i power supplies
by Corsair.
This driver can also be built as a module. If so, the module
will be called corsair-psu.
Symbol: SENSORS_CORSAIR_PSU [=n]
Type : tristate
Defined at drivers/hwmon/Kconfig:452
Prompt: Corsair PSU HID controller
Depends on: HWMON [=y] && HID [=y]
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
---
CONFIG_SENSORS_LTC2992:
If you say yes here you get support for Linear Technology LTC2992
I2C System Monitor. The LTC2992 measures current, voltage, and
power of two supplies.
This driver can also be built as a module. If so, the module will
be called ltc2992.
Symbol: SENSORS_LTC2992 [=n]
Type : tristate
Defined at drivers/hwmon/Kconfig:874
Prompt: Linear Technology LTC2992
Depends on: HWMON [=y] && I2C [=y] && GPIOLIB [=y]
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
---
CONFIG_SENSORS_MAX127:
Say y here to support Maxim's MAX127 DAS chips.
This driver can also be built as a module. If so, the module
will be called max127.
Symbol: SENSORS_MAX127 [=n]
Type : tristate
Defined at drivers/hwmon/Kconfig:965
Prompt: Maxim MAX127 12-bit 8-channel Data Acquisition System
Depends on: HWMON [=y] && I2C [=y]
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
---
CONFIG_SENSORS_PM6764TR:
If you say yes here you get hardware monitoring support for ST
PM6764TR.
This driver can also be built as a module. If so, the module will
be called pm6764tr.
Symbol: SENSORS_PM6764TR [=n]
Type : tristate
Defined at drivers/hwmon/pmbus/Kconfig:223
Prompt: ST PM6764TR
Depends on: HWMON [=y] && PMBUS [=m]
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
-> PMBus support (PMBUS [=m])
---
CONFIG_SENSORS_Q54SJ108A2:
If you say yes here you get hardware monitoring support for Delta
Q54SJ108A2 series Power Supplies.
This driver can also be built as a module. If so, the module will
be called q54sj108a2.
Symbol: SENSORS_Q54SJ108A2 [=n]
Type : tristate
Defined at drivers/hwmon/pmbus/Kconfig:241
Prompt: Delta Power Supplies Q54SJ108A2
Depends on: HWMON [=y] && PMBUS [=m]
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
-> PMBus support (PMBUS [=m])
---
CONFIG_SENSORS_SBTSI:
If you say yes here you get support for emulated temperature
sensors on AMD SoCs with SB-TSI interface connected to a BMC device.
This driver can also be built as a module. If so, the module will
be called sbtsi_temp.
Symbol: SENSORS_SBTSI [=n]
Type : tristate
Defined at drivers/hwmon/Kconfig:1536
Prompt: Emulated SB-TSI temperature sensor
Depends on: HWMON [=y] && I2C [=y]
Location:
-> Device Drivers
-> Hardware Monitoring support (HWMON [=y])
---
Cc: Dean Nelson <dnelson(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_SENSORS_CORSAIR_PSU | 1 +
.../common/generic/CONFIG_SENSORS_LTC2992 | 1 +
.../common/generic/CONFIG_SENSORS_MAX127 | 1 +
.../common/generic/CONFIG_SENSORS_PM6764TR | 1 +
.../common/generic/CONFIG_SENSORS_Q54SJ108A2 | 1 +
.../common/generic/CONFIG_SENSORS_SBTSI | 1 +
.../generic/CONFIG_SENSORS_CORSAIR_PSU | 23 -------------------
.../generic/CONFIG_SENSORS_LTC2992 | 21 -----------------
.../generic/CONFIG_SENSORS_MAX127 | 19 ---------------
.../generic/CONFIG_SENSORS_PM6764TR | 21 -----------------
.../generic/CONFIG_SENSORS_Q54SJ108A2 | 21 -----------------
.../generic/CONFIG_SENSORS_SBTSI | 20 ----------------
12 files changed, 6 insertions(+), 125 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_SENSORS_CORSAIR_PSU
create mode 100644 redhat/configs/common/generic/CONFIG_SENSORS_LTC2992
create mode 100644 redhat/configs/common/generic/CONFIG_SENSORS_MAX127
create mode 100644 redhat/configs/common/generic/CONFIG_SENSORS_PM6764TR
create mode 100644 redhat/configs/common/generic/CONFIG_SENSORS_Q54SJ108A2
create mode 100644 redhat/configs/common/generic/CONFIG_SENSORS_SBTSI
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_SENSORS_CORSAIR_PSU
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_SENSORS_LTC2992
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_SENSORS_MAX127
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_SENSORS_PM6764TR
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_SENSORS_Q54SJ108A2
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_SENSORS_SBTSI
diff --git a/redhat/configs/common/generic/CONFIG_SENSORS_CORSAIR_PSU b/redhat/configs/common/generic/CONFIG_SENSORS_CORSAIR_PSU
new file mode 100644
index 000000000000..4bc9dc6f6bfd
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_SENSORS_CORSAIR_PSU
@@ -0,0 +1 @@
+# CONFIG_SENSORS_CORSAIR_PSU is not set
diff --git a/redhat/configs/common/generic/CONFIG_SENSORS_LTC2992 b/redhat/configs/common/generic/CONFIG_SENSORS_LTC2992
new file mode 100644
index 000000000000..ea1d267ab8e1
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_SENSORS_LTC2992
@@ -0,0 +1 @@
+# CONFIG_SENSORS_LTC2992 is not set
diff --git a/redhat/configs/common/generic/CONFIG_SENSORS_MAX127 b/redhat/configs/common/generic/CONFIG_SENSORS_MAX127
new file mode 100644
index 000000000000..2886282bde7d
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_SENSORS_MAX127
@@ -0,0 +1 @@
+# CONFIG_SENSORS_MAX127 is not set
diff --git a/redhat/configs/common/generic/CONFIG_SENSORS_PM6764TR b/redhat/configs/common/generic/CONFIG_SENSORS_PM6764TR
new file mode 100644
index 000000000000..0af0b3e7870e
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_SENSORS_PM6764TR
@@ -0,0 +1 @@
+# CONFIG_SENSORS_PM6764TR is not set
diff --git a/redhat/configs/common/generic/CONFIG_SENSORS_Q54SJ108A2 b/redhat/configs/common/generic/CONFIG_SENSORS_Q54SJ108A2
new file mode 100644
index 000000000000..0033b87cbac9
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_SENSORS_Q54SJ108A2
@@ -0,0 +1 @@
+# CONFIG_SENSORS_Q54SJ108A2 is not set
diff --git a/redhat/configs/common/generic/CONFIG_SENSORS_SBTSI b/redhat/configs/common/generic/CONFIG_SENSORS_SBTSI
new file mode 100644
index 000000000000..434ec0ad9b6e
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_SENSORS_SBTSI
@@ -0,0 +1 @@
+# CONFIG_SENSORS_SBTSI is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_SENSORS_CORSAIR_PSU b/redhat/configs/pending-common/generic/CONFIG_SENSORS_CORSAIR_PSU
deleted file mode 100644
index 654d9fc9f672..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_SENSORS_CORSAIR_PSU
+++ /dev/null
@@ -1,23 +0,0 @@
-# CONFIG_SENSORS_CORSAIR_PSU:
-#
-# If you say yes here you get support for Corsair PSUs with a HID
-# interface.
-# Currently this driver supports the (RM/HX)550i, (RM/HX)650i,
-# (RM/HX)750i, (RM/HX)850i, (RM/HX)1000i and HX1200i power supplies
-# by Corsair.
-#
-# This driver can also be built as a module. If so, the module
-# will be called corsair-psu.
-#
-# Symbol: SENSORS_CORSAIR_PSU [=n]
-# Type : tristate
-# Defined at drivers/hwmon/Kconfig:452
-# Prompt: Corsair PSU HID controller
-# Depends on: HWMON [=y] && HID [=y]
-# Location:
-# -> Device Drivers
-# -> Hardware Monitoring support (HWMON [=y])
-#
-#
-#
-# CONFIG_SENSORS_CORSAIR_PSU is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_SENSORS_LTC2992 b/redhat/configs/pending-common/generic/CONFIG_SENSORS_LTC2992
deleted file mode 100644
index 04003c507356..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_SENSORS_LTC2992
+++ /dev/null
@@ -1,21 +0,0 @@
-# CONFIG_SENSORS_LTC2992:
-#
-# If you say yes here you get support for Linear Technology LTC2992
-# I2C System Monitor. The LTC2992 measures current, voltage, and
-# power of two supplies.
-#
-# This driver can also be built as a module. If so, the module will
-# be called ltc2992.
-#
-# Symbol: SENSORS_LTC2992 [=n]
-# Type : tristate
-# Defined at drivers/hwmon/Kconfig:874
-# Prompt: Linear Technology LTC2992
-# Depends on: HWMON [=y] && I2C [=y] && GPIOLIB [=y]
-# Location:
-# -> Device Drivers
-# -> Hardware Monitoring support (HWMON [=y])
-#
-#
-#
-# CONFIG_SENSORS_LTC2992 is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_SENSORS_MAX127 b/redhat/configs/pending-common/generic/CONFIG_SENSORS_MAX127
deleted file mode 100644
index 54691a2d5733..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_SENSORS_MAX127
+++ /dev/null
@@ -1,19 +0,0 @@
-# CONFIG_SENSORS_MAX127:
-#
-# Say y here to support Maxim's MAX127 DAS chips.
-#
-# This driver can also be built as a module. If so, the module
-# will be called max127.
-#
-# Symbol: SENSORS_MAX127 [=n]
-# Type : tristate
-# Defined at drivers/hwmon/Kconfig:965
-# Prompt: Maxim MAX127 12-bit 8-channel Data Acquisition System
-# Depends on: HWMON [=y] && I2C [=y]
-# Location:
-# -> Device Drivers
-# -> Hardware Monitoring support (HWMON [=y])
-#
-#
-#
-# CONFIG_SENSORS_MAX127 is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_SENSORS_PM6764TR b/redhat/configs/pending-common/generic/CONFIG_SENSORS_PM6764TR
deleted file mode 100644
index 3618ca807083..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_SENSORS_PM6764TR
+++ /dev/null
@@ -1,21 +0,0 @@
-# CONFIG_SENSORS_PM6764TR:
-#
-# If you say yes here you get hardware monitoring support for ST
-# PM6764TR.
-#
-# This driver can also be built as a module. If so, the module will
-# be called pm6764tr.
-#
-# Symbol: SENSORS_PM6764TR [=n]
-# Type : tristate
-# Defined at drivers/hwmon/pmbus/Kconfig:223
-# Prompt: ST PM6764TR
-# Depends on: HWMON [=y] && PMBUS [=m]
-# Location:
-# -> Device Drivers
-# -> Hardware Monitoring support (HWMON [=y])
-# -> PMBus support (PMBUS [=m])
-#
-#
-#
-# CONFIG_SENSORS_PM6764TR is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_SENSORS_Q54SJ108A2 b/redhat/configs/pending-common/generic/CONFIG_SENSORS_Q54SJ108A2
deleted file mode 100644
index da11b527954e..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_SENSORS_Q54SJ108A2
+++ /dev/null
@@ -1,21 +0,0 @@
-# CONFIG_SENSORS_Q54SJ108A2:
-#
-# If you say yes here you get hardware monitoring support for Delta
-# Q54SJ108A2 series Power Supplies.
-#
-# This driver can also be built as a module. If so, the module will
-# be called q54sj108a2.
-#
-# Symbol: SENSORS_Q54SJ108A2 [=n]
-# Type : tristate
-# Defined at drivers/hwmon/pmbus/Kconfig:241
-# Prompt: Delta Power Supplies Q54SJ108A2
-# Depends on: HWMON [=y] && PMBUS [=m]
-# Location:
-# -> Device Drivers
-# -> Hardware Monitoring support (HWMON [=y])
-# -> PMBus support (PMBUS [=m])
-#
-#
-#
-# CONFIG_SENSORS_Q54SJ108A2 is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_SENSORS_SBTSI b/redhat/configs/pending-common/generic/CONFIG_SENSORS_SBTSI
deleted file mode 100644
index 3842d64bacf7..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_SENSORS_SBTSI
+++ /dev/null
@@ -1,20 +0,0 @@
-# CONFIG_SENSORS_SBTSI:
-#
-# If you say yes here you get support for emulated temperature
-# sensors on AMD SoCs with SB-TSI interface connected to a BMC device.
-#
-# This driver can also be built as a module. If so, the module will
-# be called sbtsi_temp.
-#
-# Symbol: SENSORS_SBTSI [=n]
-# Type : tristate
-# Defined at drivers/hwmon/Kconfig:1536
-# Prompt: Emulated SB-TSI temperature sensor
-# Depends on: HWMON [=y] && I2C [=y]
-# Location:
-# -> Device Drivers
-# -> Hardware Monitoring support (HWMON [=y])
-#
-#
-#
-# CONFIG_SENSORS_SBTSI is not set
--
GitLab
3 years, 3 months
[OS-BUILD PATCH] [redhat] New configs in arch/x86
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_X86_SGX:
Intel(R) Software Guard eXtensions (SGX) is a set of CPU instructions
that can be used by applications to set aside private regions of code
and data, referred to as enclaves. An enclave's private memory can
only be accessed by code running within the enclave. Accesses from
outside the enclave, including other enclaves, are disallowed by
hardware.
If unsure, say N.
Symbol: X86_SGX [=n]
Type : bool
Defined at arch/x86/Kconfig:1937
Prompt: Software Guard eXtensions (SGX)
Depends on: X86_64 [=y] && CPU_SUP_INTEL [=y] && CRYPTO [=y]=y && CRYPTO_SHA256 [=y]=y
Location:
-> Processor type and features
Selects: SRCU [=y] && MMU_NOTIFIER [=y]
---
Cc: David Arcari <darcari(a)redhat.com>
Cc: Prarit Bhargava <prarit(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
redhat/configs/common/generic/CONFIG_X86_SGX | 1 +
.../pending-common/generic/CONFIG_X86_SGX | 23 -------------------
2 files changed, 1 insertion(+), 23 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_X86_SGX
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_X86_SGX
diff --git a/redhat/configs/common/generic/CONFIG_X86_SGX b/redhat/configs/common/generic/CONFIG_X86_SGX
new file mode 100644
index 000000000000..631f4c45acc5
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_X86_SGX
@@ -0,0 +1 @@
+# CONFIG_X86_SGX is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_X86_SGX b/redhat/configs/pending-common/generic/CONFIG_X86_SGX
deleted file mode 100644
index 860ef06185c1..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_X86_SGX
+++ /dev/null
@@ -1,23 +0,0 @@
-# CONFIG_X86_SGX:
-#
-# Intel(R) Software Guard eXtensions (SGX) is a set of CPU instructions
-# that can be used by applications to set aside private regions of code
-# and data, referred to as enclaves. An enclave's private memory can
-# only be accessed by code running within the enclave. Accesses from
-# outside the enclave, including other enclaves, are disallowed by
-# hardware.
-#
-# If unsure, say N.
-#
-# Symbol: X86_SGX [=n]
-# Type : bool
-# Defined at arch/x86/Kconfig:1937
-# Prompt: Software Guard eXtensions (SGX)
-# Depends on: X86_64 [=y] && CPU_SUP_INTEL [=y] && CRYPTO [=y]=y && CRYPTO_SHA256 [=y]=y
-# Location:
-# -> Processor type and features
-# Selects: SRCU [=y] && MMU_NOTIFIER [=y]
-#
-#
-#
-# CONFIG_X86_SGX is not set
--
GitLab
3 years, 3 months
[OS-BUILD PATCH] [redhat] New configs in sound/soc
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_SND_SOC_ADI:
Audio support for various reference designs by Analog Devices.
Symbol: SND_SOC_ADI [=n]
Type : tristate
Defined at sound/soc/adi/Kconfig:2
Prompt: Audio support for Analog Devices reference designs
Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m]
Location:
-> Device Drivers
-> Sound card support (SOUND [=m])
-> Advanced Linux Sound Architecture (SND [=m])
-> ALSA for SoC audio support (SND_SOC [=m])
---
CONFIG_SND_SOC_FSL_XCVR:
Say Y if you want to add Audio Transceiver (XCVR) support for NXP
iMX CPUs. XCVR is a digital module that supports HDMI2.1 eARC,
HDMI1.4 ARC and SPDIF.
Symbol: SND_SOC_FSL_XCVR [=n]
Type : tristate
Defined at sound/soc/fsl/Kconfig:98
Prompt: NXP Audio Transceiver (XCVR) module support
Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m]
Location:
-> Device Drivers
-> Sound card support (SOUND [=m])
-> Advanced Linux Sound Architecture (SND [=m])
-> ALSA for SoC audio support (SND_SOC [=m])
-> SoC Audio for Freescale CPUs
Selects: REGMAP_MMIO [=n] && SND_SOC_IMX_PCM_DMA [=n] && SND_SOC_GENERIC_DMAENGINE_PCM [=n]
---
CONFIG_SND_SOC_SOF_ALDERLAKE_SUPPORT:
This adds support for Sound Open Firmware for Intel(R) platforms
using the Alderlake processors.
Say Y if you have such a device.
If unsure select "N".
Symbol: SND_SOC_SOF_ALDERLAKE_SUPPORT [=n]
Type : bool
Defined at sound/soc/sof/intel/Kconfig:274
Prompt: SOF support for Alderlake
Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_SOC_SOF_TOPLEVEL [=y] && SND_SOC_SOF_INTEL_TOPLEVEL [=y] && SND_SOC_SOF_INTEL_PCI [=m]
Location:
-> Device Drivers
-> Sound card support (SOUND [=m])
-> Advanced Linux Sound Architecture (SND [=m])
-> ALSA for SoC audio support (SND_SOC [=m])
-> Sound Open Firmware Support (SND_SOC_SOF_TOPLEVEL [=y])
-> SOF support for Intel audio DSPs (SND_SOC_SOF_INTEL_TOPLEVEL [=y])
---
Cc: Jaroslav Kysela <jkysela(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../configs/common/generic/CONFIG_SND_SOC_ADI | 1 +
.../common/generic/CONFIG_SND_SOC_FSL_XCVR | 1 +
.../CONFIG_SND_SOC_SOF_ALDERLAKE_SUPPORT | 1 +
.../pending-common/generic/CONFIG_SND_SOC_ADI | 18 ---------------
.../generic/CONFIG_SND_SOC_FSL_XCVR | 22 ------------------
.../CONFIG_SND_SOC_SOF_ALDERLAKE_SUPPORT | 23 -------------------
6 files changed, 3 insertions(+), 63 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_SND_SOC_ADI
create mode 100644 redhat/configs/common/generic/CONFIG_SND_SOC_FSL_XCVR
create mode 100644 redhat/configs/common/generic/CONFIG_SND_SOC_SOF_ALDERLAKE_SUPPORT
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_SND_SOC_ADI
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_SND_SOC_FSL_XCVR
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_SND_SOC_SOF_ALDERLAKE_SUPPORT
diff --git a/redhat/configs/common/generic/CONFIG_SND_SOC_ADI b/redhat/configs/common/generic/CONFIG_SND_SOC_ADI
new file mode 100644
index 000000000000..cee478e8274d
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_SND_SOC_ADI
@@ -0,0 +1 @@
+# CONFIG_SND_SOC_ADI is not set
diff --git a/redhat/configs/common/generic/CONFIG_SND_SOC_FSL_XCVR b/redhat/configs/common/generic/CONFIG_SND_SOC_FSL_XCVR
new file mode 100644
index 000000000000..38a6154ef459
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_SND_SOC_FSL_XCVR
@@ -0,0 +1 @@
+# CONFIG_SND_SOC_FSL_XCVR is not set
diff --git a/redhat/configs/common/generic/CONFIG_SND_SOC_SOF_ALDERLAKE_SUPPORT b/redhat/configs/common/generic/CONFIG_SND_SOC_SOF_ALDERLAKE_SUPPORT
new file mode 100644
index 000000000000..9fcfd92a373d
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_SND_SOC_SOF_ALDERLAKE_SUPPORT
@@ -0,0 +1 @@
+# CONFIG_SND_SOC_SOF_ALDERLAKE_SUPPORT is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_SND_SOC_ADI b/redhat/configs/pending-common/generic/CONFIG_SND_SOC_ADI
deleted file mode 100644
index 1419ed113d5d..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_SND_SOC_ADI
+++ /dev/null
@@ -1,18 +0,0 @@
-# CONFIG_SND_SOC_ADI:
-#
-# Audio support for various reference designs by Analog Devices.
-#
-# Symbol: SND_SOC_ADI [=n]
-# Type : tristate
-# Defined at sound/soc/adi/Kconfig:2
-# Prompt: Audio support for Analog Devices reference designs
-# Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m]
-# Location:
-# -> Device Drivers
-# -> Sound card support (SOUND [=m])
-# -> Advanced Linux Sound Architecture (SND [=m])
-# -> ALSA for SoC audio support (SND_SOC [=m])
-#
-#
-#
-# CONFIG_SND_SOC_ADI is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_SND_SOC_FSL_XCVR b/redhat/configs/pending-common/generic/CONFIG_SND_SOC_FSL_XCVR
deleted file mode 100644
index 40a0b2a43d44..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_SND_SOC_FSL_XCVR
+++ /dev/null
@@ -1,22 +0,0 @@
-# CONFIG_SND_SOC_FSL_XCVR:
-#
-# Say Y if you want to add Audio Transceiver (XCVR) support for NXP
-# iMX CPUs. XCVR is a digital module that supports HDMI2.1 eARC,
-# HDMI1.4 ARC and SPDIF.
-#
-# Symbol: SND_SOC_FSL_XCVR [=n]
-# Type : tristate
-# Defined at sound/soc/fsl/Kconfig:98
-# Prompt: NXP Audio Transceiver (XCVR) module support
-# Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m]
-# Location:
-# -> Device Drivers
-# -> Sound card support (SOUND [=m])
-# -> Advanced Linux Sound Architecture (SND [=m])
-# -> ALSA for SoC audio support (SND_SOC [=m])
-# -> SoC Audio for Freescale CPUs
-# Selects: REGMAP_MMIO [=n] && SND_SOC_IMX_PCM_DMA [=n] && SND_SOC_GENERIC_DMAENGINE_PCM [=n]
-#
-#
-#
-# CONFIG_SND_SOC_FSL_XCVR is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_SND_SOC_SOF_ALDERLAKE_SUPPORT b/redhat/configs/pending-common/generic/CONFIG_SND_SOC_SOF_ALDERLAKE_SUPPORT
deleted file mode 100644
index 5a9a8b6fd941..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_SND_SOC_SOF_ALDERLAKE_SUPPORT
+++ /dev/null
@@ -1,23 +0,0 @@
-# CONFIG_SND_SOC_SOF_ALDERLAKE_SUPPORT:
-#
-# This adds support for Sound Open Firmware for Intel(R) platforms
-# using the Alderlake processors.
-# Say Y if you have such a device.
-# If unsure select "N".
-#
-# Symbol: SND_SOC_SOF_ALDERLAKE_SUPPORT [=n]
-# Type : bool
-# Defined at sound/soc/sof/intel/Kconfig:274
-# Prompt: SOF support for Alderlake
-# Depends on: SOUND [=m] && !UML && SND [=m] && SND_SOC [=m] && SND_SOC_SOF_TOPLEVEL [=y] && SND_SOC_SOF_INTEL_TOPLEVEL [=y] && SND_SOC_SOF_INTEL_PCI [=m]
-# Location:
-# -> Device Drivers
-# -> Sound card support (SOUND [=m])
-# -> Advanced Linux Sound Architecture (SND [=m])
-# -> ALSA for SoC audio support (SND_SOC [=m])
-# -> Sound Open Firmware Support (SND_SOC_SOF_TOPLEVEL [=y])
-# -> SOF support for Intel audio DSPs (SND_SOC_SOF_INTEL_TOPLEVEL [=y])
-#
-#
-#
-# CONFIG_SND_SOC_SOF_ALDERLAKE_SUPPORT is not set
--
GitLab
3 years, 3 months
[OS-BUILD PATCH] [redhat] New configs in drivers/platform
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_AMD_PMC:
The driver provides support for AMD Power Management Controller
primarily responsible for S2Idle transactions that are driven from
a platform firmware running on SMU. This driver also provides a debug
mechanism to investigate the S2Idle transactions and failures.
Say Y or M here if you have a notebook powered by AMD RYZEN CPU/APU.
If you choose to compile this driver as a module the module will be
called amd-pmc.
Symbol: AMD_PMC [=n]
Type : tristate
Defined at drivers/platform/x86/Kconfig:194
Prompt: AMD SoC PMC driver
Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y] && ACPI [=y] && PCI [=y]
Location:
-> Device Drivers
-> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])
---
CONFIG_DELL_WMI_SYSMAN:
This driver allows changing BIOS settings on many Dell machines from
2018 and newer without the use of any additional software.
To compile this driver as a module, choose M here: the module will
be called dell-wmi-sysman.
Symbol: DELL_WMI_SYSMAN [=n]
Type : tristate
Defined at drivers/platform/x86/Kconfig:458
Prompt: Dell WMI-based Systems management driver
Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y] && ACPI_WMI [=m] && DMI [=y]
Location:
-> Device Drivers
-> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])
Selects: NLS [=y]
---
CONFIG_INTEL_PMT_CLASS:
The Intel Platform Monitoring Technology (PMT) class driver provides
the basic sysfs interface and file hierarchy uses by PMT devices.
For more information, see:
<file:Documentation/ABI/testing/sysfs-class-intel_pmt>
To compile this driver as a module, choose M here: the module
will be called intel_pmt_class.
Symbol: INTEL_PMT_CLASS [=n]
Type : tristate
Defined at drivers/platform/x86/Kconfig:1371
Prompt: Intel Platform Monitoring Technology (PMT) Class driver
Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y]
Location:
-> Device Drivers
-> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])
Selected by [n]:
- INTEL_PMT_TELEMETRY [=n] && X86 [=y] && X86_PLATFORM_DEVICES [=y]
- INTEL_PMT_CRASHLOG [=n] && X86 [=y] && X86_PLATFORM_DEVICES [=y]
---
CONFIG_INTEL_PMT_CRASHLOG:
The Intel Platform Monitoring Technology (PMT) crashlog driver provides
access to hardware crashlog capabilities on devices that support the
feature.
To compile this driver as a module, choose M here: the module
will be called intel_pmt_crashlog.
Symbol: INTEL_PMT_CRASHLOG [=n]
Type : tristate
Defined at drivers/platform/x86/Kconfig:1394
Prompt: Intel Platform Monitoring Technology (PMT) Crashlog driver
Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y]
Location:
-> Device Drivers
-> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])
Selects: INTEL_PMT_CLASS [=n]
---
CONFIG_INTEL_PMT_TELEMETRY:
The Intel Platform Monitory Technology (PMT) Telemetry driver provides
access to hardware telemetry metrics on devices that support the
feature.
To compile this driver as a module, choose M here: the module
will be called intel_pmt_telemetry.
Symbol: INTEL_PMT_TELEMETRY [=n]
Type : tristate
Defined at drivers/platform/x86/Kconfig:1383
Prompt: Intel Platform Monitoring Technology (PMT) Telemetry driver
Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y]
Location:
-> Device Drivers
-> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])
Selects: INTEL_PMT_CLASS [=n]
---
CONFIG_MLXBF_PMC:
Say y here to enable PMC support. The PMC driver provides access
to performance monitoring counters within various blocks in the
Mellanox BlueField SoC via a sysfs interface.
Symbol: MLXBF_PMC [=n]
Type : tristate
Defined at drivers/platform/mellanox/Kconfig:59
Prompt: Mellanox BlueField Performance Monitoring Counters driver
Depends on: MELLANOX_PLATFORM [=y] && ARM64 [=y] && HWMON [=y] && ACPI [=y]
Location:
-> Device Drivers
-> Platform support for Mellanox hardware (MELLANOX_PLATFORM [=y])
---
CONFIG_SURFACE_GPE:
This driver marks the GPEs related to the ACPI lid device found on
Microsoft Surface devices as wakeup sources and prepares them
accordingly. It is required on those devices to allow wake-ups from
suspend by opening the lid.
Symbol: SURFACE_GPE [=n]
Type : tristate
Defined at drivers/platform/surface/Kconfig:43
Prompt: Surface GPE/Lid Support Driver
Depends on: SURFACE_PLATFORMS [=y] && ACPI [=y] && DMI [=y]
Location:
-> Device Drivers
-> Microsoft Surface Platform-Specific Device Drivers (SURFACE_PLATFORMS [=y])
---
CONFIG_SURFACE_PLATFORMS:
Say Y here to get to see options for platform-specific device drivers
for Microsoft Surface devices. This option alone does not add any
kernel code.
If you say N, all options in this submenu will be skipped and disabled.
Symbol: SURFACE_PLATFORMS [=y]
Type : bool
Defined at drivers/platform/surface/Kconfig:6
Prompt: Microsoft Surface Platform-Specific Device Drivers
Location:
-> Device Drivers
---
Cc: David Arcari <darcari(a)redhat.com>
Cc: Mark Langsdorf <mlangsdo(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
redhat/configs/common/generic/CONFIG_AMD_PMC | 1 +
.../common/generic/CONFIG_DELL_WMI_SYSMAN | 1 +
.../common/generic/CONFIG_INTEL_PMT_CLASS | 1 +
.../common/generic/CONFIG_INTEL_PMT_CRASHLOG | 1 +
.../common/generic/CONFIG_INTEL_PMT_TELEMETRY | 1 +
.../configs/common/generic/CONFIG_MLXBF_PMC | 1 +
.../configs/common/generic/CONFIG_SURFACE_GPE | 1 +
.../common/generic/CONFIG_SURFACE_PLATFORMS | 1 +
.../pending-common/generic/CONFIG_AMD_PMC | 24 -----------------
.../generic/CONFIG_DELL_WMI_SYSMAN | 21 ---------------
.../generic/CONFIG_INTEL_PMT_CLASS | 26 -------------------
.../generic/CONFIG_INTEL_PMT_CRASHLOG | 22 ----------------
.../generic/CONFIG_INTEL_PMT_TELEMETRY | 22 ----------------
.../pending-common/generic/CONFIG_MLXBF_PMC | 18 -------------
.../pending-common/generic/CONFIG_SURFACE_GPE | 19 --------------
.../generic/CONFIG_SURFACE_PLATFORMS | 18 -------------
16 files changed, 8 insertions(+), 170 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_AMD_PMC
create mode 100644 redhat/configs/common/generic/CONFIG_DELL_WMI_SYSMAN
create mode 100644 redhat/configs/common/generic/CONFIG_INTEL_PMT_CLASS
create mode 100644 redhat/configs/common/generic/CONFIG_INTEL_PMT_CRASHLOG
create mode 100644 redhat/configs/common/generic/CONFIG_INTEL_PMT_TELEMETRY
create mode 100644 redhat/configs/common/generic/CONFIG_MLXBF_PMC
create mode 100644 redhat/configs/common/generic/CONFIG_SURFACE_GPE
create mode 100644 redhat/configs/common/generic/CONFIG_SURFACE_PLATFORMS
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_AMD_PMC
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_DELL_WMI_SYSMAN
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_INTEL_PMT_CLASS
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_INTEL_PMT_CRASHLOG
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_INTEL_PMT_TELEMETRY
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_MLXBF_PMC
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_SURFACE_GPE
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_SURFACE_PLATFORMS
diff --git a/redhat/configs/common/generic/CONFIG_AMD_PMC b/redhat/configs/common/generic/CONFIG_AMD_PMC
new file mode 100644
index 000000000000..1ad2137c611f
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_AMD_PMC
@@ -0,0 +1 @@
+# CONFIG_AMD_PMC is not set
diff --git a/redhat/configs/common/generic/CONFIG_DELL_WMI_SYSMAN b/redhat/configs/common/generic/CONFIG_DELL_WMI_SYSMAN
new file mode 100644
index 000000000000..78afec9296de
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_DELL_WMI_SYSMAN
@@ -0,0 +1 @@
+# CONFIG_DELL_WMI_SYSMAN is not set
diff --git a/redhat/configs/common/generic/CONFIG_INTEL_PMT_CLASS b/redhat/configs/common/generic/CONFIG_INTEL_PMT_CLASS
new file mode 100644
index 000000000000..01c64e9357f7
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_INTEL_PMT_CLASS
@@ -0,0 +1 @@
+# CONFIG_INTEL_PMT_CLASS is not set
diff --git a/redhat/configs/common/generic/CONFIG_INTEL_PMT_CRASHLOG b/redhat/configs/common/generic/CONFIG_INTEL_PMT_CRASHLOG
new file mode 100644
index 000000000000..ab5099de078d
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_INTEL_PMT_CRASHLOG
@@ -0,0 +1 @@
+# CONFIG_INTEL_PMT_CRASHLOG is not set
diff --git a/redhat/configs/common/generic/CONFIG_INTEL_PMT_TELEMETRY b/redhat/configs/common/generic/CONFIG_INTEL_PMT_TELEMETRY
new file mode 100644
index 000000000000..161cc85d1659
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_INTEL_PMT_TELEMETRY
@@ -0,0 +1 @@
+# CONFIG_INTEL_PMT_TELEMETRY is not set
diff --git a/redhat/configs/common/generic/CONFIG_MLXBF_PMC b/redhat/configs/common/generic/CONFIG_MLXBF_PMC
new file mode 100644
index 000000000000..9867f83d0a38
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_MLXBF_PMC
@@ -0,0 +1 @@
+# CONFIG_MLXBF_PMC is not set
diff --git a/redhat/configs/common/generic/CONFIG_SURFACE_GPE b/redhat/configs/common/generic/CONFIG_SURFACE_GPE
new file mode 100644
index 000000000000..160153290de5
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_SURFACE_GPE
@@ -0,0 +1 @@
+# CONFIG_SURFACE_GPE is not set
diff --git a/redhat/configs/common/generic/CONFIG_SURFACE_PLATFORMS b/redhat/configs/common/generic/CONFIG_SURFACE_PLATFORMS
new file mode 100644
index 000000000000..4cc37929c7e5
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_SURFACE_PLATFORMS
@@ -0,0 +1 @@
+CONFIG_SURFACE_PLATFORMS=y
diff --git a/redhat/configs/pending-common/generic/CONFIG_AMD_PMC b/redhat/configs/pending-common/generic/CONFIG_AMD_PMC
deleted file mode 100644
index 5cb8adeceee1..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_AMD_PMC
+++ /dev/null
@@ -1,24 +0,0 @@
-# CONFIG_AMD_PMC:
-#
-# The driver provides support for AMD Power Management Controller
-# primarily responsible for S2Idle transactions that are driven from
-# a platform firmware running on SMU. This driver also provides a debug
-# mechanism to investigate the S2Idle transactions and failures.
-#
-# Say Y or M here if you have a notebook powered by AMD RYZEN CPU/APU.
-#
-# If you choose to compile this driver as a module the module will be
-# called amd-pmc.
-#
-# Symbol: AMD_PMC [=n]
-# Type : tristate
-# Defined at drivers/platform/x86/Kconfig:194
-# Prompt: AMD SoC PMC driver
-# Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y] && ACPI [=y] && PCI [=y]
-# Location:
-# -> Device Drivers
-# -> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])
-#
-#
-#
-# CONFIG_AMD_PMC is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_DELL_WMI_SYSMAN b/redhat/configs/pending-common/generic/CONFIG_DELL_WMI_SYSMAN
deleted file mode 100644
index acb862441036..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_DELL_WMI_SYSMAN
+++ /dev/null
@@ -1,21 +0,0 @@
-# CONFIG_DELL_WMI_SYSMAN:
-#
-# This driver allows changing BIOS settings on many Dell machines from
-# 2018 and newer without the use of any additional software.
-#
-# To compile this driver as a module, choose M here: the module will
-# be called dell-wmi-sysman.
-#
-# Symbol: DELL_WMI_SYSMAN [=n]
-# Type : tristate
-# Defined at drivers/platform/x86/Kconfig:458
-# Prompt: Dell WMI-based Systems management driver
-# Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y] && ACPI_WMI [=m] && DMI [=y]
-# Location:
-# -> Device Drivers
-# -> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])
-# Selects: NLS [=y]
-#
-#
-#
-# CONFIG_DELL_WMI_SYSMAN is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_INTEL_PMT_CLASS b/redhat/configs/pending-common/generic/CONFIG_INTEL_PMT_CLASS
deleted file mode 100644
index a28076d3bfea..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_INTEL_PMT_CLASS
+++ /dev/null
@@ -1,26 +0,0 @@
-# CONFIG_INTEL_PMT_CLASS:
-#
-# The Intel Platform Monitoring Technology (PMT) class driver provides
-# the basic sysfs interface and file hierarchy uses by PMT devices.
-#
-# For more information, see:
-# <file:Documentation/ABI/testing/sysfs-class-intel_pmt>
-#
-# To compile this driver as a module, choose M here: the module
-# will be called intel_pmt_class.
-#
-# Symbol: INTEL_PMT_CLASS [=n]
-# Type : tristate
-# Defined at drivers/platform/x86/Kconfig:1371
-# Prompt: Intel Platform Monitoring Technology (PMT) Class driver
-# Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y]
-# Location:
-# -> Device Drivers
-# -> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])
-# Selected by [n]:
-# - INTEL_PMT_TELEMETRY [=n] && X86 [=y] && X86_PLATFORM_DEVICES [=y]
-# - INTEL_PMT_CRASHLOG [=n] && X86 [=y] && X86_PLATFORM_DEVICES [=y]
-#
-#
-#
-# CONFIG_INTEL_PMT_CLASS is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_INTEL_PMT_CRASHLOG b/redhat/configs/pending-common/generic/CONFIG_INTEL_PMT_CRASHLOG
deleted file mode 100644
index 5c68a9c8d25e..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_INTEL_PMT_CRASHLOG
+++ /dev/null
@@ -1,22 +0,0 @@
-# CONFIG_INTEL_PMT_CRASHLOG:
-#
-# The Intel Platform Monitoring Technology (PMT) crashlog driver provides
-# access to hardware crashlog capabilities on devices that support the
-# feature.
-#
-# To compile this driver as a module, choose M here: the module
-# will be called intel_pmt_crashlog.
-#
-# Symbol: INTEL_PMT_CRASHLOG [=n]
-# Type : tristate
-# Defined at drivers/platform/x86/Kconfig:1394
-# Prompt: Intel Platform Monitoring Technology (PMT) Crashlog driver
-# Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y]
-# Location:
-# -> Device Drivers
-# -> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])
-# Selects: INTEL_PMT_CLASS [=n]
-#
-#
-#
-# CONFIG_INTEL_PMT_CRASHLOG is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_INTEL_PMT_TELEMETRY b/redhat/configs/pending-common/generic/CONFIG_INTEL_PMT_TELEMETRY
deleted file mode 100644
index a215b2914774..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_INTEL_PMT_TELEMETRY
+++ /dev/null
@@ -1,22 +0,0 @@
-# CONFIG_INTEL_PMT_TELEMETRY:
-#
-# The Intel Platform Monitory Technology (PMT) Telemetry driver provides
-# access to hardware telemetry metrics on devices that support the
-# feature.
-#
-# To compile this driver as a module, choose M here: the module
-# will be called intel_pmt_telemetry.
-#
-# Symbol: INTEL_PMT_TELEMETRY [=n]
-# Type : tristate
-# Defined at drivers/platform/x86/Kconfig:1383
-# Prompt: Intel Platform Monitoring Technology (PMT) Telemetry driver
-# Depends on: X86 [=y] && X86_PLATFORM_DEVICES [=y]
-# Location:
-# -> Device Drivers
-# -> X86 Platform Specific Device Drivers (X86_PLATFORM_DEVICES [=y])
-# Selects: INTEL_PMT_CLASS [=n]
-#
-#
-#
-# CONFIG_INTEL_PMT_TELEMETRY is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_MLXBF_PMC b/redhat/configs/pending-common/generic/CONFIG_MLXBF_PMC
deleted file mode 100644
index 26e293f5fec0..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_MLXBF_PMC
+++ /dev/null
@@ -1,18 +0,0 @@
-# CONFIG_MLXBF_PMC:
-#
-# Say y here to enable PMC support. The PMC driver provides access
-# to performance monitoring counters within various blocks in the
-# Mellanox BlueField SoC via a sysfs interface.
-#
-# Symbol: MLXBF_PMC [=n]
-# Type : tristate
-# Defined at drivers/platform/mellanox/Kconfig:59
-# Prompt: Mellanox BlueField Performance Monitoring Counters driver
-# Depends on: MELLANOX_PLATFORM [=y] && ARM64 [=y] && HWMON [=y] && ACPI [=y]
-# Location:
-# -> Device Drivers
-# -> Platform support for Mellanox hardware (MELLANOX_PLATFORM [=y])
-#
-#
-#
-# CONFIG_MLXBF_PMC is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_SURFACE_GPE b/redhat/configs/pending-common/generic/CONFIG_SURFACE_GPE
deleted file mode 100644
index a4c070efd2c2..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_SURFACE_GPE
+++ /dev/null
@@ -1,19 +0,0 @@
-# CONFIG_SURFACE_GPE:
-#
-# This driver marks the GPEs related to the ACPI lid device found on
-# Microsoft Surface devices as wakeup sources and prepares them
-# accordingly. It is required on those devices to allow wake-ups from
-# suspend by opening the lid.
-#
-# Symbol: SURFACE_GPE [=n]
-# Type : tristate
-# Defined at drivers/platform/surface/Kconfig:43
-# Prompt: Surface GPE/Lid Support Driver
-# Depends on: SURFACE_PLATFORMS [=y] && ACPI [=y] && DMI [=y]
-# Location:
-# -> Device Drivers
-# -> Microsoft Surface Platform-Specific Device Drivers (SURFACE_PLATFORMS [=y])
-#
-#
-#
-# CONFIG_SURFACE_GPE is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_SURFACE_PLATFORMS b/redhat/configs/pending-common/generic/CONFIG_SURFACE_PLATFORMS
deleted file mode 100644
index d2823d1aac40..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_SURFACE_PLATFORMS
+++ /dev/null
@@ -1,18 +0,0 @@
-# CONFIG_SURFACE_PLATFORMS:
-#
-# Say Y here to get to see options for platform-specific device drivers
-# for Microsoft Surface devices. This option alone does not add any
-# kernel code.
-#
-# If you say N, all options in this submenu will be skipped and disabled.
-#
-# Symbol: SURFACE_PLATFORMS [=y]
-# Type : bool
-# Defined at drivers/platform/surface/Kconfig:6
-# Prompt: Microsoft Surface Platform-Specific Device Drivers
-# Location:
-# -> Device Drivers
-#
-#
-#
-CONFIG_SURFACE_PLATFORMS=y
--
GitLab
3 years, 3 months
❌ FAIL: Test report for kernel 5.10.5-200.fc33 (fedora-33)
by CKI Project
Hello,
We ran automated tests on the following kernel build:
Kernel package: kernel-5.10.5-200.fc33
Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=59079987
The results of these automated tests are provided below.
Overall result: FAILED (see details below)
Tests: FAILED
One or more kernel tests failed:
ppc64le:
❌ Boot test
All kernel binaries, config files, and logs are available for download here:
https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?pre...
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.
For the full detail on our testing procedures, please scroll to the bottom of
this message.
,-. ,-.
( C ) ( K ) Continuous
`-',-.`-' Kernel
( I ) Integration
`-'
______________________________________________________________________________
Hardware testing
----------------
We booted each kernel and ran the following tests:
aarch64:
Host 1:
✅ Boot test
✅ ACPI table test
✅ LTP
✅ Loopdev Sanity
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
🚧 ✅ CIFS Connectathon
🚧 ✅ Ethernet drivers sanity
Host 2:
✅ Boot test
✅ stress: stress-ng
🚧 ✅ xfstests - ext4
🚧 ✅ xfstests - xfs
🚧 ✅ xfstests - btrfs
🚧 ✅ Storage blktests
🚧 ✅ Storage block - filesystem fio test
🚧 ✅ Storage block - queue scheduler test
🚧 ✅ Storage nvme - tcp
🚧 ✅ Storage: swraid mdadm raid_module test
ppc64le:
Host 1:
❌ Boot test
🚧 ⚡⚡⚡ xfstests - ext4
🚧 ⚡⚡⚡ xfstests - xfs
🚧 ⚡⚡⚡ xfstests - btrfs
🚧 ⚡⚡⚡ Storage blktests
🚧 ⚡⚡⚡ Storage block - filesystem fio test
🚧 ⚡⚡⚡ Storage block - queue scheduler test
🚧 ⚡⚡⚡ Storage nvme - tcp
🚧 ⚡⚡⚡ Storage: swraid mdadm raid_module test
Host 2:
✅ Boot test
✅ LTP
✅ Loopdev Sanity
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
🚧 ✅ CIFS Connectathon
🚧 ✅ Ethernet drivers sanity
s390x:
Host 1:
✅ Boot test
✅ stress: stress-ng
🚧 ✅ Storage blktests
🚧 ❌ Storage nvme - tcp
🚧 ✅ Storage: swraid mdadm raid_module test
Host 2:
✅ Boot test
✅ LTP
✅ Loopdev Sanity
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
🚧 ✅ CIFS Connectathon
🚧 ✅ Ethernet drivers sanity
x86_64:
Host 1:
✅ Boot test
✅ stress: stress-ng
🚧 ✅ xfstests - ext4
🚧 ✅ xfstests - xfs
🚧 ✅ xfstests - btrfs
🚧 ✅ xfstests - nfsv4.2
🚧 ✅ xfstests - cifsv3.11
🚧 ✅ Storage blktests
🚧 ✅ Storage block - filesystem fio test
🚧 ✅ Storage block - queue scheduler test
🚧 ✅ Storage nvme - tcp
🚧 ✅ Storage: swraid mdadm raid_module test
Host 2:
✅ Boot test
✅ ACPI table test
✅ LTP
✅ Loopdev Sanity
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
🚧 ✅ CIFS Connectathon
🚧 ✅ Ethernet drivers sanity
Test sources: https://gitlab.com/cki-project/kernel-tests
💚 Pull requests are welcome for new tests or improvements to existing tests!
Aborted tests
-------------
Tests that didn't complete running successfully are marked with ⚡⚡⚡.
If this was caused by an infrastructure issue, we try to mark that
explicitly in the report.
Waived tests
------------
If the test run included waived tests, they are marked with 🚧. Such tests are
executed but their results are not taken into account. Tests are waived when
their results are not reliable enough, e.g. when they're just introduced or are
being fixed.
Testing timeout
---------------
We aim to provide a report within reasonable timeframe. Tests that haven't
finished running yet are marked with ⏱.
3 years, 3 months
[OS-BUILD PATCH] [redhat] New configs in net/bridge
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_BRIDGE_CFM:
If you say Y here, then the Ethernet bridge will be able to run CFM
protocol according to 802.1Q section 12.14
Say N to exclude this support and reduce the binary size.
If unsure, say N.
Symbol: BRIDGE_CFM [=n]
Type : bool
Defined at net/bridge/Kconfig:77
Prompt: CFM protocol
Depends on: NET [=y] && BRIDGE [=m]
Location:
-> Networking support (NET [=y])
-> Networking options
-> 802.1d Ethernet Bridging (BRIDGE [=m])
---
Cc: Ivan Vecera <ivecera(a)redhat.com>
Cc: Jiri Benc <jbenc(a)redhat.com>
Cc: Marcelo Leitner <mleitner(a)redhat.com>
Cc: Davide Caratti <dcaratti(a)redhat.com>
Cc: Eric Garver <egarver(a)redhat.com>
Cc: Flavio Leitner <fbl(a)redhat.com>
Cc: Florian Westphal <fwestpha(a)redhat.com>
Cc: Guillaume Nault <gnault(a)redhat.com>
Cc: Hangbin Liu <haliu(a)redhat.com>
Cc: Jarod Wilson <jarod(a)redhat.com>
Cc: Lorenzo Bianconi <lorenzo.bianconi(a)redhat.com>
Cc: Paolo Abeni <pabeni(a)redhat.com>
Cc: Phil Sutter <psutter(a)redhat.com>
Cc: Sabrina Dubroca <sdubroca(a)redhat.com>
Cc: Stefano Brivio <sbrivio(a)redhat.com>
Cc: Xin Long <lxin(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../configs/common/generic/CONFIG_BRIDGE_CFM | 1 +
.../pending-common/generic/CONFIG_BRIDGE_CFM | 22 -------------------
2 files changed, 1 insertion(+), 22 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_BRIDGE_CFM
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_BRIDGE_CFM
diff --git a/redhat/configs/common/generic/CONFIG_BRIDGE_CFM b/redhat/configs/common/generic/CONFIG_BRIDGE_CFM
new file mode 100644
index 000000000000..d3175e47af57
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_BRIDGE_CFM
@@ -0,0 +1 @@
+# CONFIG_BRIDGE_CFM is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_BRIDGE_CFM b/redhat/configs/pending-common/generic/CONFIG_BRIDGE_CFM
deleted file mode 100644
index b4e8cb358dec..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_BRIDGE_CFM
+++ /dev/null
@@ -1,22 +0,0 @@
-# CONFIG_BRIDGE_CFM:
-#
-# If you say Y here, then the Ethernet bridge will be able to run CFM
-# protocol according to 802.1Q section 12.14
-#
-# Say N to exclude this support and reduce the binary size.
-#
-# If unsure, say N.
-#
-# Symbol: BRIDGE_CFM [=n]
-# Type : bool
-# Defined at net/bridge/Kconfig:77
-# Prompt: CFM protocol
-# Depends on: NET [=y] && BRIDGE [=m]
-# Location:
-# -> Networking support (NET [=y])
-# -> Networking options
-# -> 802.1d Ethernet Bridging (BRIDGE [=m])
-#
-#
-#
-# CONFIG_BRIDGE_CFM is not set
--
GitLab
3 years, 3 months