✅ PASS: Test report for kernel 5.6.16-300.fc32 (fedora-32)
by CKI Project
Hello jforbes,
We ran automated tests on the following kernel build:
Kernel package: kernel-5.6.16-300.fc32
Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=45421398
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://cki-artifacts.s3.us-east-2.amazonaws.com/index.html?prefix=datawa...
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
✅ LTP
✅ Loopdev Sanity
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
✅ Ethernet drivers sanity
🚧 ✅ CIFS Connectathon
Host 2:
✅ Boot test
✅ xfstests - ext4
✅ xfstests - xfs
🚧 ✅ Storage blktests
ppc64le:
Host 1:
✅ Boot test
✅ LTP
✅ Loopdev Sanity
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
✅ Ethernet drivers sanity
🚧 ✅ CIFS Connectathon
Host 2:
✅ Boot test
🚧 ✅ kdump - sysrq-c
Host 3:
✅ Boot test
✅ xfstests - ext4
✅ xfstests - xfs
🚧 ✅ Storage blktests
s390x:
Host 1:
✅ Boot test
🚧 ✅ kdump - sysrq-c
Host 2:
✅ Boot test
✅ stress: stress-ng
🚧 ✅ Storage blktests
Host 3:
✅ Boot test
✅ LTP
✅ Loopdev Sanity
✅ Memory function: memfd_create
✅ Ethernet drivers sanity
🚧 ✅ CIFS Connectathon
x86_64:
Host 1:
✅ Boot test
🚧 ✅ kdump - sysrq-c
Host 2:
✅ Boot test
✅ LTP
✅ Loopdev Sanity
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
✅ Ethernet drivers sanity
🚧 ✅ CIFS Connectathon
Host 3:
✅ Boot test
✅ xfstests - ext4
✅ xfstests - xfs
✅ stress: stress-ng
🚧 ✅ Storage blktests
Test sources: https://github.com/CKI-project/tests-beaker
💚 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, 10 months
[OS-BUILD PATCH] [redhat] New configs in net/bridge
by GitLab Bridge on behalf of jmflinuxtx
From: "Justin M. Forbes" <jforbes(a)fedoraproject.org>
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_BRIDGE_MRP:
If you say Y here, then the Ethernet bridge will be able to run MRP
protocol to detect loops
Say N to exclude this support and reduce the binary size.
If unsure, say N.
Symbol: BRIDGE_MRP [=n]
Type : bool
Defined at net/bridge/Kconfig:65
Prompt: MRP protocol
Depends on: NET [=y] && BRIDGE [=m]
Location:
-> Networking support (NET [=y])
-> Networking options
-> 802.1d Ethernet Bridging (BRIDGE [=m])
---
Signed-off-by: Justin M. Forbes <jforbes(a)fedoraproject.org>
---
.../configs/common/generic/CONFIG_BRIDGE_MRP | 1 +
.../pending-common/generic/CONFIG_BRIDGE_MRP | 22 -------------------
2 files changed, 1 insertion(+), 22 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_BRIDGE_MRP
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_BRIDGE_MRP
diff --git a/redhat/configs/common/generic/CONFIG_BRIDGE_MRP b/redhat/configs/common/generic/CONFIG_BRIDGE_MRP
new file mode 100644
index 000000000000..38f0a923d22d
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_BRIDGE_MRP
@@ -0,0 +1 @@
+# CONFIG_BRIDGE_MRP is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_BRIDGE_MRP b/redhat/configs/pending-common/generic/CONFIG_BRIDGE_MRP
deleted file mode 100644
index e85844c2b228..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_BRIDGE_MRP
+++ /dev/null
@@ -1,22 +0,0 @@
-# CONFIG_BRIDGE_MRP:
-#
-# If you say Y here, then the Ethernet bridge will be able to run MRP
-# protocol to detect loops
-#
-# Say N to exclude this support and reduce the binary size.
-#
-# If unsure, say N.
-#
-# Symbol: BRIDGE_MRP [=n]
-# Type : bool
-# Defined at net/bridge/Kconfig:65
-# Prompt: MRP protocol
-# Depends on: NET [=y] && BRIDGE [=m]
-# Location:
-# -> Networking support (NET [=y])
-# -> Networking options
-# -> 802.1d Ethernet Bridging (BRIDGE [=m])
-#
-#
-#
-# CONFIG_BRIDGE_MRP is not set
--
2.26.2
3 years, 10 months
[OS-BUILD PATCH] [redhat] New configs in lib/Kconfig.debug
by GitLab Bridge on behalf of jeremycline
From: "CKI@GitLab" <cki-project(a)redhat.com>
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_TEST_HMM:
This is a pseudo device driver solely for testing HMM.
Say M here if you want to build the HMM test module.
Doing so will allow you to run tools/testing/selftest/vm/hmm-tests.
If unsure, say N.
Symbol: TEST_HMM [=n]
Type : tristate
Defined at lib/Kconfig.debug:2221
Prompt: Test HMM (Heterogeneous Memory Management)
Depends on: RUNTIME_TESTING_MENU [=y] && TRANSPARENT_HUGEPAGE [=y] && DEVICE_PRIVATE [=y]
Location:
-> Kernel hacking
-> Kernel Testing and Coverage
-> Runtime Testing (RUNTIME_TESTING_MENU [=y])
Selects: HMM_MIRROR [=n] && MMU_NOTIFIER [=y]
---
Signed-off-by: CKI@GitLab <cki-project(a)redhat.com>
---
redhat/configs/common/generic/CONFIG_TEST_HMM | 1 +
.../pending-common/generic/CONFIG_TEST_HMM | 22 -------------------
2 files changed, 1 insertion(+), 22 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_TEST_HMM
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_TEST_HMM
diff --git a/redhat/configs/common/generic/CONFIG_TEST_HMM b/redhat/configs/common/generic/CONFIG_TEST_HMM
new file mode 100644
index 000000000000..5210be0d7788
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_TEST_HMM
@@ -0,0 +1 @@
+# CONFIG_TEST_HMM is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_TEST_HMM b/redhat/configs/pending-common/generic/CONFIG_TEST_HMM
deleted file mode 100644
index 4956e0059745..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_TEST_HMM
+++ /dev/null
@@ -1,22 +0,0 @@
-# CONFIG_TEST_HMM:
-#
-# This is a pseudo device driver solely for testing HMM.
-# Say M here if you want to build the HMM test module.
-# Doing so will allow you to run tools/testing/selftest/vm/hmm-tests.
-#
-# If unsure, say N.
-#
-# Symbol: TEST_HMM [=n]
-# Type : tristate
-# Defined at lib/Kconfig.debug:2221
-# Prompt: Test HMM (Heterogeneous Memory Management)
-# Depends on: RUNTIME_TESTING_MENU [=y] && TRANSPARENT_HUGEPAGE [=y] && DEVICE_PRIVATE [=y]
-# Location:
-# -> Kernel hacking
-# -> Kernel Testing and Coverage
-# -> Runtime Testing (RUNTIME_TESTING_MENU [=y])
-# Selects: HMM_MIRROR [=n] && MMU_NOTIFIER [=y]
-#
-#
-#
-# CONFIG_TEST_HMM is not set
--
2.26.2
3 years, 10 months
[OS-BUILD PATCH] [redhat] New configs in kernel/power
by GitLab Bridge on behalf of jeremycline
From: "CKI@GitLab" <cki-project(a)redhat.com>
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_HIBERNATION_SNAPSHOT_DEV:
Device used by the uswsusp tools.
Say N if no snapshotting from userspace is needed, this also
reduces the attack surface of the kernel.
If in doubt, say Y.
Symbol: HIBERNATION_SNAPSHOT_DEV [=y]
Type : bool
Defined at kernel/power/Kconfig:83
Prompt: Userspace snapshot device
Depends on: HIBERNATION [=y]
Location:
-> Power management and ACPI options
-> Hibernation (aka 'suspend to disk') (HIBERNATION [=y])
---
Signed-off-by: CKI@GitLab <cki-project(a)redhat.com>
---
.../generic/CONFIG_HIBERNATION_SNAPSHOT_DEV | 1 +
.../generic/CONFIG_HIBERNATION_SNAPSHOT_DEV | 21 -------------------
2 files changed, 1 insertion(+), 21 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_HIBERNATION_SNAPSHOT_DEV
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_HIBERNATION_SNAPSHOT_DEV
diff --git a/redhat/configs/common/generic/CONFIG_HIBERNATION_SNAPSHOT_DEV b/redhat/configs/common/generic/CONFIG_HIBERNATION_SNAPSHOT_DEV
new file mode 100644
index 000000000000..c4627aa7e564
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_HIBERNATION_SNAPSHOT_DEV
@@ -0,0 +1 @@
+CONFIG_HIBERNATION_SNAPSHOT_DEV=y
diff --git a/redhat/configs/pending-common/generic/CONFIG_HIBERNATION_SNAPSHOT_DEV b/redhat/configs/pending-common/generic/CONFIG_HIBERNATION_SNAPSHOT_DEV
deleted file mode 100644
index b1643ff501e5..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_HIBERNATION_SNAPSHOT_DEV
+++ /dev/null
@@ -1,21 +0,0 @@
-# CONFIG_HIBERNATION_SNAPSHOT_DEV:
-#
-# Device used by the uswsusp tools.
-#
-# Say N if no snapshotting from userspace is needed, this also
-# reduces the attack surface of the kernel.
-#
-# If in doubt, say Y.
-#
-# Symbol: HIBERNATION_SNAPSHOT_DEV [=y]
-# Type : bool
-# Defined at kernel/power/Kconfig:83
-# Prompt: Userspace snapshot device
-# Depends on: HIBERNATION [=y]
-# Location:
-# -> Power management and ACPI options
-# -> Hibernation (aka 'suspend to disk') (HIBERNATION [=y])
-#
-#
-#
-CONFIG_HIBERNATION_SNAPSHOT_DEV=y
--
2.26.2
3 years, 10 months
[OS-BUILD PATCH] [redhat] New configs in drivers/mfd
by GitLab Bridge on behalf of jeremycline
From: "CKI@GitLab" <cki-project(a)redhat.com>
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_MFD_GATEWORKS_GSC:
Enable support for the Gateworks System Controller (GSC) found
on Gateworks Single Board Computers supporting system functions
such as push-button monitor, multiple ADC's for voltage and
temperature monitoring, fan controller and watchdog monitor.
This driver provides common support for accessing the device.
Additional drivers must be enabled in order to use the
functionality of the device.
Symbol: MFD_GATEWORKS_GSC [=n]
Type : tristate
Defined at drivers/mfd/Kconfig:410
Prompt: Gateworks System Controller
Depends on: HAS_IOMEM [=y] && I2C [=y] && OF [=y]
Location:
-> Device Drivers
-> Multifunction device drivers
Selects: MFD_CORE [=m] && REGMAP_I2C [=m] && REGMAP_IRQ [=n]
---
Signed-off-by: CKI@GitLab <cki-project(a)redhat.com>
---
.../common/generic/CONFIG_MFD_GATEWORKS_GSC | 1 +
.../generic/CONFIG_MFD_GATEWORKS_GSC | 23 -------------------
2 files changed, 1 insertion(+), 23 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_MFD_GATEWORKS_GSC
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_MFD_GATEWORKS_GSC
diff --git a/redhat/configs/common/generic/CONFIG_MFD_GATEWORKS_GSC b/redhat/configs/common/generic/CONFIG_MFD_GATEWORKS_GSC
new file mode 100644
index 000000000000..19ea1a015197
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_MFD_GATEWORKS_GSC
@@ -0,0 +1 @@
+# CONFIG_MFD_GATEWORKS_GSC is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_MFD_GATEWORKS_GSC b/redhat/configs/pending-common/generic/CONFIG_MFD_GATEWORKS_GSC
deleted file mode 100644
index bf368088fee8..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_MFD_GATEWORKS_GSC
+++ /dev/null
@@ -1,23 +0,0 @@
-# CONFIG_MFD_GATEWORKS_GSC:
-#
-# Enable support for the Gateworks System Controller (GSC) found
-# on Gateworks Single Board Computers supporting system functions
-# such as push-button monitor, multiple ADC's for voltage and
-# temperature monitoring, fan controller and watchdog monitor.
-# This driver provides common support for accessing the device.
-# Additional drivers must be enabled in order to use the
-# functionality of the device.
-#
-# Symbol: MFD_GATEWORKS_GSC [=n]
-# Type : tristate
-# Defined at drivers/mfd/Kconfig:410
-# Prompt: Gateworks System Controller
-# Depends on: HAS_IOMEM [=y] && I2C [=y] && OF [=y]
-# Location:
-# -> Device Drivers
-# -> Multifunction device drivers
-# Selects: MFD_CORE [=m] && REGMAP_I2C [=m] && REGMAP_IRQ [=n]
-#
-#
-#
-# CONFIG_MFD_GATEWORKS_GSC is not set
--
2.26.2
3 years, 10 months
[OS-BUILD PATCH] [redhat] New configs in drivers/char
by GitLab Bridge on behalf of jeremycline
From: "CKI@GitLab" <cki-project(a)redhat.com>
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_HW_RANDOM_CCTRNG:
Say 'Y' to enable the True Random Number Generator driver for the
Arm TrustZone CryptoCell family of processors.
Currently the CryptoCell 713 and 703 are supported.
The driver is supported only in SoC where Trusted Execution
Environment is not used.
Choose 'M' to compile this driver as a module. The module
will be called cctrng.
If unsure, say 'N'.
Symbol: HW_RANDOM_CCTRNG [=n]
Type : tristate
Defined at drivers/char/hw_random/Kconfig:477
Prompt: Arm CryptoCell True Random Number Generator support
Depends on: HW_RANDOM [=y] && HAS_IOMEM [=y] && OF [=y]
Location:
-> Device Drivers
-> Character devices
-> Hardware Random Number Generator Core support (HW_RANDOM [=y])
---
Signed-off-by: CKI@GitLab <cki-project(a)redhat.com>
---
.../common/generic/CONFIG_HW_RANDOM_CCTRNG | 1 +
.../generic/CONFIG_HW_RANDOM_CCTRNG | 24 -------------------
2 files changed, 1 insertion(+), 24 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_HW_RANDOM_CCTRNG
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_HW_RANDOM_CCTRNG
diff --git a/redhat/configs/common/generic/CONFIG_HW_RANDOM_CCTRNG b/redhat/configs/common/generic/CONFIG_HW_RANDOM_CCTRNG
new file mode 100644
index 000000000000..97f5363c7233
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_HW_RANDOM_CCTRNG
@@ -0,0 +1 @@
+# CONFIG_HW_RANDOM_CCTRNG is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_HW_RANDOM_CCTRNG b/redhat/configs/pending-common/generic/CONFIG_HW_RANDOM_CCTRNG
deleted file mode 100644
index e21ef59f0f46..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_HW_RANDOM_CCTRNG
+++ /dev/null
@@ -1,24 +0,0 @@
-# CONFIG_HW_RANDOM_CCTRNG:
-#
-# Say 'Y' to enable the True Random Number Generator driver for the
-# Arm TrustZone CryptoCell family of processors.
-# Currently the CryptoCell 713 and 703 are supported.
-# The driver is supported only in SoC where Trusted Execution
-# Environment is not used.
-# Choose 'M' to compile this driver as a module. The module
-# will be called cctrng.
-# If unsure, say 'N'.
-#
-# Symbol: HW_RANDOM_CCTRNG [=n]
-# Type : tristate
-# Defined at drivers/char/hw_random/Kconfig:477
-# Prompt: Arm CryptoCell True Random Number Generator support
-# Depends on: HW_RANDOM [=y] && HAS_IOMEM [=y] && OF [=y]
-# Location:
-# -> Device Drivers
-# -> Character devices
-# -> Hardware Random Number Generator Core support (HW_RANDOM [=y])
-#
-#
-#
-# CONFIG_HW_RANDOM_CCTRNG is not set
--
2.26.2
3 years, 10 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: 92ecc67cdc42 - [redhat] kernel-5.8.0-0.rc0.20200604git9fb4c5250f10.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, 10 months
[OS-BUILD PATCH] [redhat] New configs in block/Kconfig
by GitLab Bridge on behalf of jeremycline
From: "CKI@GitLab" <cki-project(a)redhat.com>
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_BLK_INLINE_ENCRYPTION:
Build the blk-crypto subsystem. Enabling this lets the
block layer handle encryption, so users can take
advantage of inline encryption hardware if present.
Symbol: BLK_INLINE_ENCRYPTION [=n]
Type : bool
Defined at block/Kconfig:189
Prompt: Enable inline encryption support in block layer
Depends on: BLOCK [=y]
Location:
-> Enable the block layer (BLOCK [=y])
---
Cc: Ming Lei <minlei(a)redhat.com>
Cc: Jeff Moyer <jmoyer(a)redhat.com>
Cc: Vivek Goyal <vgoyal(a)redhat.com>
Signed-off-by: CKI@GitLab <cki-project(a)redhat.com>
---
.../common/generic/CONFIG_BLK_INLINE_ENCRYPTION | 1 +
.../generic/CONFIG_BLK_INLINE_ENCRYPTION | 17 -----------------
2 files changed, 1 insertion(+), 17 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_BLK_INLINE_ENCRYPTION
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_BLK_INLINE_ENCRYPTION
diff --git a/redhat/configs/common/generic/CONFIG_BLK_INLINE_ENCRYPTION b/redhat/configs/common/generic/CONFIG_BLK_INLINE_ENCRYPTION
new file mode 100644
index 000000000000..3f642705f0e4
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_BLK_INLINE_ENCRYPTION
@@ -0,0 +1 @@
+# CONFIG_BLK_INLINE_ENCRYPTION is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_BLK_INLINE_ENCRYPTION b/redhat/configs/pending-common/generic/CONFIG_BLK_INLINE_ENCRYPTION
deleted file mode 100644
index 69f5c2552f83..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_BLK_INLINE_ENCRYPTION
+++ /dev/null
@@ -1,17 +0,0 @@
-# CONFIG_BLK_INLINE_ENCRYPTION:
-#
-# Build the blk-crypto subsystem. Enabling this lets the
-# block layer handle encryption, so users can take
-# advantage of inline encryption hardware if present.
-#
-# Symbol: BLK_INLINE_ENCRYPTION [=n]
-# Type : bool
-# Defined at block/Kconfig:189
-# Prompt: Enable inline encryption support in block layer
-# Depends on: BLOCK [=y]
-# Location:
-# -> Enable the block layer (BLOCK [=y])
-#
-#
-#
-# CONFIG_BLK_INLINE_ENCRYPTION is not set
--
2.26.2
3 years, 10 months
[OS-BUILD PATCH] [redhat] New configs in drivers/gpu
by GitLab Bridge on behalf of jeremycline
From: "CKI@GitLab" <cki-project(a)redhat.com>
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_DRM_CHRONTEL_CH7033:
Enable support for the Chrontel CH7033 VGA/DVI/HDMI Encoder, as
found in the Dell Wyse 3020 thin client.
If in doubt, say "N".
Symbol: DRM_CHRONTEL_CH7033 [=n]
Type : tristate
Defined at drivers/gpu/drm/bridge/Kconfig:30
Prompt: Chrontel CH7033 Video Encoder
Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_BRIDGE [=y] && OF [=y]
Location:
-> Device Drivers
-> Graphics support
-> Display Interface Bridges
Selects: DRM_KMS_HELPER [=m]
---
CONFIG_DRM_NWL_MIPI_DSI:
This enables the Northwest Logic MIPI DSI Host controller as
for example found on NXP's i.MX8 Processors.
Symbol: DRM_NWL_MIPI_DSI [=n]
Type : tristate
Defined at drivers/gpu/drm/bridge/Kconfig:71
Prompt: Northwest Logic MIPI DSI Host controller
Depends on: DRM_BRIDGE [=y] && DRM [=m] && COMMON_CLK [=y] && OF [=y] && HAS_IOMEM [=y]
Location:
-> Device Drivers
-> Graphics support
-> Display Interface Bridges
Selects: DRM_KMS_HELPER [=m] && DRM_MIPI_DSI [=n] && DRM_PANEL_BRIDGE [=y] && GENERIC_PHY_MIPI_DPHY [=n] && MFD_SYSCON [=y] && MULTIPLEXER [=n] && REGMAP_MMIO [=y]
---
Cc: David Airlie <airlied(a)redhat.com>
Cc: Adam Jackson <ajax(a)redhat.com>
Signed-off-by: CKI@GitLab <cki-project(a)redhat.com>
---
.../common/generic/CONFIG_DRM_CHRONTEL_CH7033 | 1 +
.../common/generic/CONFIG_DRM_NWL_MIPI_DSI | 1 +
.../generic/CONFIG_DRM_CHRONTEL_CH7033 | 21 -------------------
.../generic/CONFIG_DRM_NWL_MIPI_DSI | 19 -----------------
4 files changed, 2 insertions(+), 40 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_DRM_CHRONTEL_CH7033
create mode 100644 redhat/configs/common/generic/CONFIG_DRM_NWL_MIPI_DSI
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_DRM_CHRONTEL_CH7033
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_DRM_NWL_MIPI_DSI
diff --git a/redhat/configs/common/generic/CONFIG_DRM_CHRONTEL_CH7033 b/redhat/configs/common/generic/CONFIG_DRM_CHRONTEL_CH7033
new file mode 100644
index 000000000000..5cfc88342d4f
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_DRM_CHRONTEL_CH7033
@@ -0,0 +1 @@
+# CONFIG_DRM_CHRONTEL_CH7033 is not set
diff --git a/redhat/configs/common/generic/CONFIG_DRM_NWL_MIPI_DSI b/redhat/configs/common/generic/CONFIG_DRM_NWL_MIPI_DSI
new file mode 100644
index 000000000000..6f4e4e857904
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_DRM_NWL_MIPI_DSI
@@ -0,0 +1 @@
+# CONFIG_DRM_NWL_MIPI_DSI is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_DRM_CHRONTEL_CH7033 b/redhat/configs/pending-common/generic/CONFIG_DRM_CHRONTEL_CH7033
deleted file mode 100644
index 67f8d39636b8..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_DRM_CHRONTEL_CH7033
+++ /dev/null
@@ -1,21 +0,0 @@
-# CONFIG_DRM_CHRONTEL_CH7033:
-#
-# Enable support for the Chrontel CH7033 VGA/DVI/HDMI Encoder, as
-# found in the Dell Wyse 3020 thin client.
-#
-# If in doubt, say "N".
-#
-# Symbol: DRM_CHRONTEL_CH7033 [=n]
-# Type : tristate
-# Defined at drivers/gpu/drm/bridge/Kconfig:30
-# Prompt: Chrontel CH7033 Video Encoder
-# Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_BRIDGE [=y] && OF [=y]
-# Location:
-# -> Device Drivers
-# -> Graphics support
-# -> Display Interface Bridges
-# Selects: DRM_KMS_HELPER [=m]
-#
-#
-#
-# CONFIG_DRM_CHRONTEL_CH7033 is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_DRM_NWL_MIPI_DSI b/redhat/configs/pending-common/generic/CONFIG_DRM_NWL_MIPI_DSI
deleted file mode 100644
index 1bbd7514e83e..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_DRM_NWL_MIPI_DSI
+++ /dev/null
@@ -1,19 +0,0 @@
-# CONFIG_DRM_NWL_MIPI_DSI:
-#
-# This enables the Northwest Logic MIPI DSI Host controller as
-# for example found on NXP's i.MX8 Processors.
-#
-# Symbol: DRM_NWL_MIPI_DSI [=n]
-# Type : tristate
-# Defined at drivers/gpu/drm/bridge/Kconfig:71
-# Prompt: Northwest Logic MIPI DSI Host controller
-# Depends on: DRM_BRIDGE [=y] && DRM [=m] && COMMON_CLK [=y] && OF [=y] && HAS_IOMEM [=y]
-# Location:
-# -> Device Drivers
-# -> Graphics support
-# -> Display Interface Bridges
-# Selects: DRM_KMS_HELPER [=m] && DRM_MIPI_DSI [=n] && DRM_PANEL_BRIDGE [=y] && GENERIC_PHY_MIPI_DPHY [=n] && MFD_SYSCON [=y] && MULTIPLEXER [=n] && REGMAP_MMIO [=y]
-#
-#
-#
-# CONFIG_DRM_NWL_MIPI_DSI is not set
--
2.26.2
3 years, 10 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: 5beac744b0fc - [redhat] kernel-5.8.0-0.rc0.20200603gitd6f9469a03d8.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:
aarch64: FAILED (see build-aarch64.log.xz attachment)
ppc64le: FAILED (see build-ppc64le.log.xz attachment)
s390x: FAILED (see build-s390x.log.xz attachment)
x86_64: FAILED (see build-x86_64.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 compiled the kernel for 4 architectures:
aarch64:
rpmbuild arguments: rpmbuild --target aarch64 --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools
ppc64le:
rpmbuild arguments: rpmbuild --target ppc64le --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools
s390x:
rpmbuild arguments: rpmbuild --target s390x --with=cross --with=kabidw_base --without=bpftool --without=selftests --without=debug --without=ipaclones --without=perf --without=tools
x86_64:
rpmbuild arguments: rpmbuild --target x86_64 --with=bpftool --with=selftests --with=kabidw_base --without=debug --without=ipaclones --without=perf --without=tools
3 years, 10 months