kernel January 2021

kernel@lists.fedoraproject.org

22 participants
163 discussions

[OS-BUILD PATCH 0/14] 5.11 acpi cleanup
by GitLab Bridge on behalf of pbrobinson 12 Jan '21

12 Jan '21

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 16

✅ PASS: Test report for kernel 5.10.6-200.fc33 (fedora-33)
by CKI Project 11 Jan '21

11 Jan '21

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?prefi… 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 ⏱.

1 0

[OS-BUILD PATCH] Enable the vkms module in Fedora
by GitLab Bridge on behalf of jeremycline 11 Jan '21

11 Jan '21

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

1 0

[OS-BUILD PATCH] [redhat] New configs in drivers/hwmon
by GitLab Bridge on behalf of redhat-patchlab 11 Jan '21

11 Jan '21

2 1

[OS-BUILD PATCH] [redhat] New configs in arch/x86
by GitLab Bridge on behalf of redhat-patchlab 11 Jan '21

11 Jan '21

5 11

[OS-BUILD PATCH 0/6] RHMAINTAINERS: update 20210107
by GitLab Bridge on behalf of prarit 08 Jan '21

08 Jan '21

From: prarit on gitlab.com Update RHMAINTAINERS with new entries and cleanups. Signed-off-by: Prarit Bhargava <prarit(a)redhat.com>

2 7

[OS-BUILD PATCH] [redhat] New configs in sound/soc
by GitLab Bridge on behalf of redhat-patchlab 08 Jan '21

08 Jan '21

3 5

[OS-BUILD PATCH] [redhat] New configs in drivers/platform
by GitLab Bridge on behalf of redhat-patchlab 07 Jan '21

07 Jan '21

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

4 11

❌ FAIL: Test report for kernel 5.10.5-200.fc33 (fedora-33)
by CKI Project 07 Jan '21

07 Jan '21

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?prefi… 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 ⏱.

1 0

[OS-BUILD PATCH] [redhat] New configs in net/bridge
by GitLab Bridge on behalf of redhat-patchlab 06 Jan '21

06 Jan '21

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

kernel January 2021