Re: [OS-BUILD PATCH] [redhat] New configs in net/xfrm
by Marcelo Ricardo Leitner
On Mon, Oct 19, 2020 at 11:58:59PM +0200, Sabrina Dubroca wrote:
> 2020-10-19, 13:35:11 -0300, Marcelo Ricardo Leitner wrote:
> > On Fri, Oct 16, 2020 at 03:29:58PM -0000, GitLab Bridge on behalf of jeremycline wrote:
> > > --- /dev/null
> > > +++ b/redhat/configs/common/generic/CONFIG_XFRM_USER_COMPAT
> > > @@ -0,0 +1 @@
> > > +# CONFIG_XFRM_USER_COMPAT is not set
> >
> > Sabrina, thoughts?
>
> That's for 32-bit userspace programs configuring IPsec on 64-bit
> kernels. I think it's ok to leave it off for now.
Cool. Can you then please ack this change? :-)
Marcelo
1 hour, 44 minutes
❌ FAIL: Test report for kernel 5.9.0-42.test.fc33 (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: 889afeef8da3 - [redhat] kernel-5.10.0-0.rc0.20201015gitb5fc7a89e58b.41
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://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?pre...
We attempted to compile the kernel for multiple architectures, but the compile
failed on one or more architectures:
s390x: FAILED (see build-s390x.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=kabidw_base --without=debug
2 hours, 10 minutes
[OS-BUILD PATCH] arm64/defconfig: Enable CONFIG_KEXEC_FILE
by GitLab Bridge on behalf of bhsharma
From: Bhupesh Sharma <bhsharma(a)redhat.com>
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1821565
Upstream Status: 2a379716f3d76aebc5574155de247b547a0214cc
kexec_file_load() syscall interface is now supported for
arm64 architecture as well via upstream commits:
3751e728cef2 ("arm64: kexec_file: add crash dump support") and
3ddd9992a590 ("arm64: enable KEXEC_FILE config")].
This patch enables config KEXEC_FILE by default in the fedora
arm64 defconfig, so that user-space tools like kexec-tools
can use the same as the default interface for kexec/kdump
on arm64 fedora systems.
Cc: kernel-team(a)fedoraproject.org
Signed-off-by: Bhupesh Sharma <bhsharma(a)redhat.com>
---
redhat/configs/fedora/generic/arm/aarch64/CONFIG_KEXEC_FILE | 1 +
1 file changed, 1 insertion(+)
create mode 100644 redhat/configs/fedora/generic/arm/aarch64/CONFIG_KEXEC_FILE
diff --git a/redhat/configs/fedora/generic/arm/aarch64/CONFIG_KEXEC_FILE b/redhat/configs/fedora/generic/arm/aarch64/CONFIG_KEXEC_FILE
new file mode 100644
index 000000000000..25862bf98de8
--- /dev/null
+++ b/redhat/configs/fedora/generic/arm/aarch64/CONFIG_KEXEC_FILE
@@ -0,0 +1 @@
+CONFIG_KEXEC_FILE=y
--
GitLab
2 hours, 51 minutes
[OS-BUILD PATCH] [redhat] New configs in drivers/acpi
by GitLab Bridge on behalf of jeremycline
From: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_DPTF_PCH_FIVR:
This driver adds support for Dynamic Platform and Thermal Framework
(DPTF) PCH FIVR Participant device support. This driver allows to
switch PCH FIVR (Fully Integrated Voltage Regulator) frequency.
This participant is responsible for exposing:
freq_mhz_low_clock
freq_mhz_high_clock
To compile this driver as a module, choose M here:
the module will be called dptf_pch_fivr.
Symbol: DPTF_PCH_FIVR [=n]
Type : tristate
Defined at drivers/acpi/dptf/Kconfig:18
Prompt: DPTF PCH FIVR Participant
Depends on: ACPI [=y] && X86 [=y]
Location:
-> Power management and ACPI options
-> ACPI (Advanced Configuration and Power Interface) Support (ACPI [=y])
---
Cc: Al Stone <ahs3(a)redhat.com>
Cc: Lenny Szubowicz <lszubowi(a)redhat.com>
Cc: Prarit Bhargava <prarit(a)redhat.com>
Cc: David Arcari <darcari(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_DPTF_PCH_FIVR | 1 +
.../generic/CONFIG_DPTF_PCH_FIVR | 24 -------------------
2 files changed, 1 insertion(+), 24 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_DPTF_PCH_FIVR
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_DPTF_PCH_FIVR
diff --git a/redhat/configs/common/generic/CONFIG_DPTF_PCH_FIVR b/redhat/configs/common/generic/CONFIG_DPTF_PCH_FIVR
new file mode 100644
index 000000000000..e201b9b14135
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_DPTF_PCH_FIVR
@@ -0,0 +1 @@
+# CONFIG_DPTF_PCH_FIVR is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_DPTF_PCH_FIVR b/redhat/configs/pending-common/generic/CONFIG_DPTF_PCH_FIVR
deleted file mode 100644
index 511d5616fbc6..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_DPTF_PCH_FIVR
+++ /dev/null
@@ -1,24 +0,0 @@
-# CONFIG_DPTF_PCH_FIVR:
-#
-# This driver adds support for Dynamic Platform and Thermal Framework
-# (DPTF) PCH FIVR Participant device support. This driver allows to
-# switch PCH FIVR (Fully Integrated Voltage Regulator) frequency.
-# This participant is responsible for exposing:
-# freq_mhz_low_clock
-# freq_mhz_high_clock
-#
-# To compile this driver as a module, choose M here:
-# the module will be called dptf_pch_fivr.
-#
-# Symbol: DPTF_PCH_FIVR [=n]
-# Type : tristate
-# Defined at drivers/acpi/dptf/Kconfig:18
-# Prompt: DPTF PCH FIVR Participant
-# Depends on: ACPI [=y] && X86 [=y]
-# Location:
-# -> Power management and ACPI options
-# -> ACPI (Advanced Configuration and Power Interface) Support (ACPI [=y])
-#
-#
-#
-# CONFIG_DPTF_PCH_FIVR is not set
--
GitLab
5 hours, 39 minutes
[OS-BUILD PATCH] [redhat] New configs in net/can
by GitLab Bridge on behalf of jeremycline
From: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_CAN_ISOTP:
CAN Transport Protocols offer support for segmented Point-to-Point
communication between CAN nodes via two defined CAN Identifiers.
As CAN frames can only transport a small amount of data bytes
(max. 8 bytes for 'classic' CAN and max. 64 bytes for CAN FD) this
segmentation is needed to transport longer PDUs as needed e.g. for
vehicle diagnosis (UDS, ISO 14229) or IP-over-CAN traffic.
This protocol driver implements data transfers according to
ISO 15765-2:2016 for 'classic' CAN and CAN FD frame types.
If you want to perform automotive vehicle diagnostic services (UDS),
say 'y'.
Symbol: CAN_ISOTP [=n]
Type : tristate
Defined at net/can/Kconfig:58
Prompt: ISO 15765-2:2016 CAN transport protocol
Depends on: NET [=y] && CAN [=m]
Location:
-> Networking support (NET [=y])
-> CAN bus subsystem support (CAN [=m])
---
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: Ivan Vecera <ivecera(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_CAN_ISOTP | 1 +
.../pending-common/generic/CONFIG_CAN_ISOTP | 25 -------------------
2 files changed, 1 insertion(+), 25 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_CAN_ISOTP
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_CAN_ISOTP
diff --git a/redhat/configs/common/generic/CONFIG_CAN_ISOTP b/redhat/configs/common/generic/CONFIG_CAN_ISOTP
new file mode 100644
index 000000000000..2ebf8768a868
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_CAN_ISOTP
@@ -0,0 +1 @@
+# CONFIG_CAN_ISOTP is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_CAN_ISOTP b/redhat/configs/pending-common/generic/CONFIG_CAN_ISOTP
deleted file mode 100644
index 58dd572e7fc7..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_CAN_ISOTP
+++ /dev/null
@@ -1,25 +0,0 @@
-# CONFIG_CAN_ISOTP:
-#
-# CAN Transport Protocols offer support for segmented Point-to-Point
-# communication between CAN nodes via two defined CAN Identifiers.
-# As CAN frames can only transport a small amount of data bytes
-# (max. 8 bytes for 'classic' CAN and max. 64 bytes for CAN FD) this
-# segmentation is needed to transport longer PDUs as needed e.g. for
-# vehicle diagnosis (UDS, ISO 14229) or IP-over-CAN traffic.
-# This protocol driver implements data transfers according to
-# ISO 15765-2:2016 for 'classic' CAN and CAN FD frame types.
-# If you want to perform automotive vehicle diagnostic services (UDS),
-# say 'y'.
-#
-# Symbol: CAN_ISOTP [=n]
-# Type : tristate
-# Defined at net/can/Kconfig:58
-# Prompt: ISO 15765-2:2016 CAN transport protocol
-# Depends on: NET [=y] && CAN [=m]
-# Location:
-# -> Networking support (NET [=y])
-# -> CAN bus subsystem support (CAN [=m])
-#
-#
-#
-# CONFIG_CAN_ISOTP is not set
--
GitLab
6 hours, 6 minutes
[OS-BUILD PATCH] [redhat] New configs in drivers/video
by GitLab Bridge on behalf of jeremycline
From: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_BACKLIGHT_KTD253:
Say y to enabled the backlight driver for the Kinetic KTD253
which is a 1-wire GPIO-controlled backlight found in some mobile
phones.
Symbol: BACKLIGHT_KTD253 [=n]
Type : tristate
Defined at drivers/video/backlight/Kconfig:185
Prompt: Backlight Driver for Kinetic KTD253
Depends on: HAS_IOMEM [=y] && BACKLIGHT_CLASS_DEVICE [=y] && (GPIOLIB [=y] || COMPILE_TEST [=n])
Location:
-> Device Drivers
-> Graphics support
-> Backlight & LCD device support
-> Lowlevel Backlight controls (BACKLIGHT_CLASS_DEVICE [=y])
---
Cc: David Airlie <airlied(a)redhat.com>
Cc: Adam Jackson <ajax(a)redhat.com>
Cc: Lyude Paul <lyude(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_BACKLIGHT_KTD253 | 1 +
.../generic/CONFIG_BACKLIGHT_KTD253 | 20 -------------------
2 files changed, 1 insertion(+), 20 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_BACKLIGHT_KTD253
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_BACKLIGHT_KTD253
diff --git a/redhat/configs/common/generic/CONFIG_BACKLIGHT_KTD253 b/redhat/configs/common/generic/CONFIG_BACKLIGHT_KTD253
new file mode 100644
index 000000000000..5f66e1f9d617
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_BACKLIGHT_KTD253
@@ -0,0 +1 @@
+# CONFIG_BACKLIGHT_KTD253 is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_BACKLIGHT_KTD253 b/redhat/configs/pending-common/generic/CONFIG_BACKLIGHT_KTD253
deleted file mode 100644
index b91ab9814972..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_BACKLIGHT_KTD253
+++ /dev/null
@@ -1,20 +0,0 @@
-# CONFIG_BACKLIGHT_KTD253:
-#
-# Say y to enabled the backlight driver for the Kinetic KTD253
-# which is a 1-wire GPIO-controlled backlight found in some mobile
-# phones.
-#
-# Symbol: BACKLIGHT_KTD253 [=n]
-# Type : tristate
-# Defined at drivers/video/backlight/Kconfig:185
-# Prompt: Backlight Driver for Kinetic KTD253
-# Depends on: HAS_IOMEM [=y] && BACKLIGHT_CLASS_DEVICE [=y] && (GPIOLIB [=y] || COMPILE_TEST [=n])
-# Location:
-# -> Device Drivers
-# -> Graphics support
-# -> Backlight & LCD device support
-# -> Lowlevel Backlight controls (BACKLIGHT_CLASS_DEVICE [=y])
-#
-#
-#
-# CONFIG_BACKLIGHT_KTD253 is not set
--
GitLab
6 hours, 21 minutes
[OS-BUILD PATCH] [redhat] New configs in drivers/gpu
by GitLab Bridge on behalf of jeremycline
From: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_DRM_AMD_DC_SI:
Choose this option to enable new AMD DC support for SI asics
by default. This includes Tahiti, Pitcairn, Cape Verde, Oland.
Hainan is not supported by AMD DC and it has no physical DCE6.
Symbol: DRM_AMD_DC_SI [=n]
Type : bool
Defined at drivers/gpu/drm/amd/display/Kconfig:34
Prompt: AMD DC support for Southern Islands ASICs
Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_AMDGPU [=m]
Location:
-> Device Drivers
-> Graphics support
-> AMD GPU (DRM_AMDGPU [=m])
-> Display Engine Configuration
---
CONFIG_DRM_CDNS_MHDP8546:
Support Cadence DPI to DP bridge. This is an internal
bridge and is meant to be directly embedded in a SoC.
It takes a DPI stream as input and outputs it encoded
in DP format.
Symbol: DRM_CDNS_MHDP8546 [=n]
Type : tristate
Defined at drivers/gpu/drm/bridge/cadence/Kconfig:2
Prompt: Cadence DPI/DP bridge
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] && DRM_PANEL_BRIDGE [=y]
---
CONFIG_DRM_LONTIUM_LT9611:
Driver for Lontium LT9611 DSI to HDMI bridge
chip driver that converts dual DSI and I2S to
HDMI signals
Please say Y if you have such hardware.
Symbol: DRM_LONTIUM_LT9611 [=n]
Type : tristate
Defined at drivers/gpu/drm/bridge/Kconfig:51
Prompt: Lontium LT9611 DSI/HDMI bridge
Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_BRIDGE [=y] && OF [=y]
Location:
-> Device Drivers
-> Graphics support
-> Display Interface Bridges
Selects: SND_SOC_HDMI_CODEC [=n] && DRM_PANEL_BRIDGE [=y] && DRM_KMS_HELPER [=m] && REGMAP_I2C [=m]
---
CONFIG_DRM_TOSHIBA_TC358762:
Toshiba TC358762 DSI/DPI bridge driver.
Symbol: DRM_TOSHIBA_TC358762 [=n]
Type : tristate
Defined at drivers/gpu/drm/bridge/Kconfig:169
Prompt: TC358762 DSI/DPI bridge
Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_BRIDGE [=y] && OF [=y]
Location:
-> Device Drivers
-> Graphics support
-> Display Interface Bridges
Selects: DRM_MIPI_DSI [=n] && DRM_PANEL_BRIDGE [=y]
---
CONFIG_DRM_TOSHIBA_TC358775:
Toshiba TC358775 DSI/LVDS bridge chip driver.
Symbol: DRM_TOSHIBA_TC358775 [=n]
Type : tristate
Defined at drivers/gpu/drm/bridge/Kconfig:205
Prompt: Toshiba TC358775 DSI/LVDS bridge
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] && REGMAP_I2C [=m] && DRM_PANEL [=y] && DRM_MIPI_DSI [=n]
---
Cc: David Airlie <airlied(a)redhat.com>
Cc: Adam Jackson <ajax(a)redhat.com>
Cc: Lyude Paul <lyude(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_DRM_AMD_DC_SI | 1 +
.../common/generic/CONFIG_DRM_CDNS_MHDP8546 | 1 +
.../common/generic/CONFIG_DRM_LONTIUM_LT9611 | 1 +
.../generic/CONFIG_DRM_TOSHIBA_TC358762 | 1 +
.../generic/CONFIG_DRM_TOSHIBA_TC358775 | 1 +
.../generic/CONFIG_DRM_AMD_DC_SI | 20 ------------------
.../generic/CONFIG_DRM_CDNS_MHDP8546 | 21 -------------------
.../generic/CONFIG_DRM_LONTIUM_LT9611 | 21 -------------------
.../generic/CONFIG_DRM_TOSHIBA_TC358762 | 18 ----------------
.../generic/CONFIG_DRM_TOSHIBA_TC358775 | 18 ----------------
10 files changed, 5 insertions(+), 98 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_DRM_AMD_DC_SI
create mode 100644 redhat/configs/common/generic/CONFIG_DRM_CDNS_MHDP8546
create mode 100644 redhat/configs/common/generic/CONFIG_DRM_LONTIUM_LT9611
create mode 100644 redhat/configs/common/generic/CONFIG_DRM_TOSHIBA_TC358762
create mode 100644 redhat/configs/common/generic/CONFIG_DRM_TOSHIBA_TC358775
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_DRM_AMD_DC_SI
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_DRM_CDNS_MHDP8546
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_DRM_LONTIUM_LT9611
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_DRM_TOSHIBA_TC358762
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_DRM_TOSHIBA_TC358775
diff --git a/redhat/configs/common/generic/CONFIG_DRM_AMD_DC_SI b/redhat/configs/common/generic/CONFIG_DRM_AMD_DC_SI
new file mode 100644
index 000000000000..8714da73cbd2
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_DRM_AMD_DC_SI
@@ -0,0 +1 @@
+# CONFIG_DRM_AMD_DC_SI is not set
diff --git a/redhat/configs/common/generic/CONFIG_DRM_CDNS_MHDP8546 b/redhat/configs/common/generic/CONFIG_DRM_CDNS_MHDP8546
new file mode 100644
index 000000000000..2f08c639144c
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_DRM_CDNS_MHDP8546
@@ -0,0 +1 @@
+# CONFIG_DRM_CDNS_MHDP8546 is not set
diff --git a/redhat/configs/common/generic/CONFIG_DRM_LONTIUM_LT9611 b/redhat/configs/common/generic/CONFIG_DRM_LONTIUM_LT9611
new file mode 100644
index 000000000000..0ee3b259ff15
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_DRM_LONTIUM_LT9611
@@ -0,0 +1 @@
+# CONFIG_DRM_LONTIUM_LT9611 is not set
diff --git a/redhat/configs/common/generic/CONFIG_DRM_TOSHIBA_TC358762 b/redhat/configs/common/generic/CONFIG_DRM_TOSHIBA_TC358762
new file mode 100644
index 000000000000..a99c1adf0ba5
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_DRM_TOSHIBA_TC358762
@@ -0,0 +1 @@
+# CONFIG_DRM_TOSHIBA_TC358762 is not set
diff --git a/redhat/configs/common/generic/CONFIG_DRM_TOSHIBA_TC358775 b/redhat/configs/common/generic/CONFIG_DRM_TOSHIBA_TC358775
new file mode 100644
index 000000000000..5090a0707875
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_DRM_TOSHIBA_TC358775
@@ -0,0 +1 @@
+# CONFIG_DRM_TOSHIBA_TC358775 is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_DRM_AMD_DC_SI b/redhat/configs/pending-common/generic/CONFIG_DRM_AMD_DC_SI
deleted file mode 100644
index c5a73ee203d5..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_DRM_AMD_DC_SI
+++ /dev/null
@@ -1,20 +0,0 @@
-# CONFIG_DRM_AMD_DC_SI:
-#
-# Choose this option to enable new AMD DC support for SI asics
-# by default. This includes Tahiti, Pitcairn, Cape Verde, Oland.
-# Hainan is not supported by AMD DC and it has no physical DCE6.
-#
-# Symbol: DRM_AMD_DC_SI [=n]
-# Type : bool
-# Defined at drivers/gpu/drm/amd/display/Kconfig:34
-# Prompt: AMD DC support for Southern Islands ASICs
-# Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_AMDGPU [=m]
-# Location:
-# -> Device Drivers
-# -> Graphics support
-# -> AMD GPU (DRM_AMDGPU [=m])
-# -> Display Engine Configuration
-#
-#
-#
-# CONFIG_DRM_AMD_DC_SI is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_DRM_CDNS_MHDP8546 b/redhat/configs/pending-common/generic/CONFIG_DRM_CDNS_MHDP8546
deleted file mode 100644
index 02038e90fdb0..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_DRM_CDNS_MHDP8546
+++ /dev/null
@@ -1,21 +0,0 @@
-# CONFIG_DRM_CDNS_MHDP8546:
-#
-# Support Cadence DPI to DP bridge. This is an internal
-# bridge and is meant to be directly embedded in a SoC.
-# It takes a DPI stream as input and outputs it encoded
-# in DP format.
-#
-# Symbol: DRM_CDNS_MHDP8546 [=n]
-# Type : tristate
-# Defined at drivers/gpu/drm/bridge/cadence/Kconfig:2
-# Prompt: Cadence DPI/DP bridge
-# 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] && DRM_PANEL_BRIDGE [=y]
-#
-#
-#
-# CONFIG_DRM_CDNS_MHDP8546 is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_DRM_LONTIUM_LT9611 b/redhat/configs/pending-common/generic/CONFIG_DRM_LONTIUM_LT9611
deleted file mode 100644
index 4aebfd6a11dd..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_DRM_LONTIUM_LT9611
+++ /dev/null
@@ -1,21 +0,0 @@
-# CONFIG_DRM_LONTIUM_LT9611:
-#
-# Driver for Lontium LT9611 DSI to HDMI bridge
-# chip driver that converts dual DSI and I2S to
-# HDMI signals
-# Please say Y if you have such hardware.
-#
-# Symbol: DRM_LONTIUM_LT9611 [=n]
-# Type : tristate
-# Defined at drivers/gpu/drm/bridge/Kconfig:51
-# Prompt: Lontium LT9611 DSI/HDMI bridge
-# Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_BRIDGE [=y] && OF [=y]
-# Location:
-# -> Device Drivers
-# -> Graphics support
-# -> Display Interface Bridges
-# Selects: SND_SOC_HDMI_CODEC [=n] && DRM_PANEL_BRIDGE [=y] && DRM_KMS_HELPER [=m] && REGMAP_I2C [=m]
-#
-#
-#
-# CONFIG_DRM_LONTIUM_LT9611 is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_DRM_TOSHIBA_TC358762 b/redhat/configs/pending-common/generic/CONFIG_DRM_TOSHIBA_TC358762
deleted file mode 100644
index 0dc67e830c11..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_DRM_TOSHIBA_TC358762
+++ /dev/null
@@ -1,18 +0,0 @@
-# CONFIG_DRM_TOSHIBA_TC358762:
-#
-# Toshiba TC358762 DSI/DPI bridge driver.
-#
-# Symbol: DRM_TOSHIBA_TC358762 [=n]
-# Type : tristate
-# Defined at drivers/gpu/drm/bridge/Kconfig:169
-# Prompt: TC358762 DSI/DPI bridge
-# Depends on: HAS_IOMEM [=y] && DRM [=m] && DRM_BRIDGE [=y] && OF [=y]
-# Location:
-# -> Device Drivers
-# -> Graphics support
-# -> Display Interface Bridges
-# Selects: DRM_MIPI_DSI [=n] && DRM_PANEL_BRIDGE [=y]
-#
-#
-#
-# CONFIG_DRM_TOSHIBA_TC358762 is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_DRM_TOSHIBA_TC358775 b/redhat/configs/pending-common/generic/CONFIG_DRM_TOSHIBA_TC358775
deleted file mode 100644
index fad70468b09d..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_DRM_TOSHIBA_TC358775
+++ /dev/null
@@ -1,18 +0,0 @@
-# CONFIG_DRM_TOSHIBA_TC358775:
-#
-# Toshiba TC358775 DSI/LVDS bridge chip driver.
-#
-# Symbol: DRM_TOSHIBA_TC358775 [=n]
-# Type : tristate
-# Defined at drivers/gpu/drm/bridge/Kconfig:205
-# Prompt: Toshiba TC358775 DSI/LVDS bridge
-# 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] && REGMAP_I2C [=m] && DRM_PANEL [=y] && DRM_MIPI_DSI [=n]
-#
-#
-#
-# CONFIG_DRM_TOSHIBA_TC358775 is not set
--
GitLab
6 hours, 21 minutes
[OS-BUILD PATCH] [redhat] New configs in net/xfrm
by GitLab Bridge on behalf of jeremycline
From: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_XFRM_USER_COMPAT:
Transformation(XFRM) user configuration interface like IPsec
used by compatible Linux applications.
If unsure, say N.
Symbol: XFRM_USER_COMPAT [=n]
Type : tristate
Defined at net/xfrm/Kconfig:31
Prompt: Compatible ABI support
Depends on: NET [=y] && INET [=y] && XFRM_USER [=y] && COMPAT_FOR_U64_ALIGNMENT [=y] && HAVE_EFFICIENT_UNALIGNED_ACCESS [=y]
Location:
-> Networking support (NET [=y])
-> Networking options
-> Transformation user configuration interface (XFRM_USER [=y])
Selects: WANT_COMPAT_NETLINK_MESSAGES [=n]
---
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: Ivan Vecera <ivecera(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>
---
.../common/generic/CONFIG_XFRM_USER_COMPAT | 1 +
.../generic/CONFIG_XFRM_USER_COMPAT | 21 -------------------
2 files changed, 1 insertion(+), 21 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_XFRM_USER_COMPAT
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_XFRM_USER_COMPAT
diff --git a/redhat/configs/common/generic/CONFIG_XFRM_USER_COMPAT b/redhat/configs/common/generic/CONFIG_XFRM_USER_COMPAT
new file mode 100644
index 000000000000..798d10e8e93e
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_XFRM_USER_COMPAT
@@ -0,0 +1 @@
+# CONFIG_XFRM_USER_COMPAT is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_XFRM_USER_COMPAT b/redhat/configs/pending-common/generic/CONFIG_XFRM_USER_COMPAT
deleted file mode 100644
index 7941fd360e9b..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_XFRM_USER_COMPAT
+++ /dev/null
@@ -1,21 +0,0 @@
-# CONFIG_XFRM_USER_COMPAT:
-#
-# Transformation(XFRM) user configuration interface like IPsec
-# used by compatible Linux applications.
-#
-# If unsure, say N.
-#
-# Symbol: XFRM_USER_COMPAT [=n]
-# Type : tristate
-# Defined at net/xfrm/Kconfig:31
-# Prompt: Compatible ABI support
-# Depends on: NET [=y] && INET [=y] && XFRM_USER [=y] && COMPAT_FOR_U64_ALIGNMENT [=y] && HAVE_EFFICIENT_UNALIGNED_ACCESS [=y]
-# Location:
-# -> Networking support (NET [=y])
-# -> Networking options
-# -> Transformation user configuration interface (XFRM_USER [=y])
-# Selects: WANT_COMPAT_NETLINK_MESSAGES [=n]
-#
-#
-#
-# CONFIG_XFRM_USER_COMPAT is not set
--
GitLab
7 hours, 26 minutes
[OS-BUILD PATCH] [redhat] New configs in drivers/pinctrl
by GitLab Bridge on behalf of jeremycline
From: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_PINCTRL_MSM8226:
This is the pinctrl, pinmux, pinconf and gpiolib driver for the
Qualcomm Technologies Inc TLMM block found on the Qualcomm
Technologies Inc MSM8226 platform.
Symbol: PINCTRL_MSM8226 [=n]
Type : tristate
Defined at drivers/pinctrl/qcom/Kconfig:65
Prompt: Qualcomm 8226 pin controller driver
Depends on: PINCTRL [=y] && (ARCH_QCOM [=y] || COMPILE_TEST [=n]) && GPIOLIB [=y] && OF [=y]
Location:
-> Device Drivers
-> Pin controllers (PINCTRL [=y])
Selects: PINCTRL_MSM [=y]
---
Cc: David Arcari <darcari(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_PINCTRL_MSM8226 | 1 +
.../generic/CONFIG_PINCTRL_MSM8226 | 19 -------------------
2 files changed, 1 insertion(+), 19 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_PINCTRL_MSM8226
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_PINCTRL_MSM8226
diff --git a/redhat/configs/common/generic/CONFIG_PINCTRL_MSM8226 b/redhat/configs/common/generic/CONFIG_PINCTRL_MSM8226
new file mode 100644
index 000000000000..3bc6adb7fe6e
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_PINCTRL_MSM8226
@@ -0,0 +1 @@
+# CONFIG_PINCTRL_MSM8226 is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_PINCTRL_MSM8226 b/redhat/configs/pending-common/generic/CONFIG_PINCTRL_MSM8226
deleted file mode 100644
index e89e5bdc2f79..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_PINCTRL_MSM8226
+++ /dev/null
@@ -1,19 +0,0 @@
-# CONFIG_PINCTRL_MSM8226:
-#
-# This is the pinctrl, pinmux, pinconf and gpiolib driver for the
-# Qualcomm Technologies Inc TLMM block found on the Qualcomm
-# Technologies Inc MSM8226 platform.
-#
-# Symbol: PINCTRL_MSM8226 [=n]
-# Type : tristate
-# Defined at drivers/pinctrl/qcom/Kconfig:65
-# Prompt: Qualcomm 8226 pin controller driver
-# Depends on: PINCTRL [=y] && (ARCH_QCOM [=y] || COMPILE_TEST [=n]) && GPIOLIB [=y] && OF [=y]
-# Location:
-# -> Device Drivers
-# -> Pin controllers (PINCTRL [=y])
-# Selects: PINCTRL_MSM [=y]
-#
-#
-#
-# CONFIG_PINCTRL_MSM8226 is not set
--
GitLab
8 hours, 17 minutes
[OS-BUILD PATCH] [redhat] New configs in drivers/mfd
by GitLab Bridge on behalf of jeremycline
From: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_MFD_INTEL_M10_BMC:
Support for the Intel MAX 10 board management controller using the
SPI interface.
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_INTEL_M10_BMC [=n]
Type : tristate
Defined at drivers/mfd/Kconfig:2156
Prompt: Intel MAX 10 Board Management Controller
Depends on: HAS_IOMEM [=y] && SPI_MASTER [=y]
Location:
-> Device Drivers
-> Multifunction device drivers
Selects: REGMAP_SPI_AVMM [=n] && MFD_CORE [=y]
---
CONFIG_MFD_SL28CPLD:
Say yes here to enable support for the Kontron sl28cpld board
management controller.
It can be found on the following boards:
* SMARC-sAL28
Symbol: MFD_SL28CPLD [=n]
Type : tristate
Defined at drivers/mfd/Kconfig:1189
Prompt: Kontron sl28cpld Board Management Controller
Depends on: HAS_IOMEM [=y] && I2C [=y]
Location:
-> Device Drivers
-> Multifunction device drivers
Selects: MFD_SIMPLE_MFD_I2C [=n]
---
Cc: Torez Smith <torez(a)redhat.com>
Cc: David Arcari <darcari(a)redhat.com>
Cc: Tony Camuso <tcamuso(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_MFD_INTEL_M10_BMC | 1 +
.../common/generic/CONFIG_MFD_SL28CPLD | 1 +
.../generic/CONFIG_MFD_INTEL_M10_BMC | 22 -------------------
.../generic/CONFIG_MFD_SL28CPLD | 21 ------------------
4 files changed, 2 insertions(+), 43 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_MFD_INTEL_M10_BMC
create mode 100644 redhat/configs/common/generic/CONFIG_MFD_SL28CPLD
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_MFD_INTEL_M10_BMC
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_MFD_SL28CPLD
diff --git a/redhat/configs/common/generic/CONFIG_MFD_INTEL_M10_BMC b/redhat/configs/common/generic/CONFIG_MFD_INTEL_M10_BMC
new file mode 100644
index 000000000000..6b75715a431e
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_MFD_INTEL_M10_BMC
@@ -0,0 +1 @@
+# CONFIG_MFD_INTEL_M10_BMC is not set
diff --git a/redhat/configs/common/generic/CONFIG_MFD_SL28CPLD b/redhat/configs/common/generic/CONFIG_MFD_SL28CPLD
new file mode 100644
index 000000000000..b65f30c09c02
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_MFD_SL28CPLD
@@ -0,0 +1 @@
+# CONFIG_MFD_SL28CPLD is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_MFD_INTEL_M10_BMC b/redhat/configs/pending-common/generic/CONFIG_MFD_INTEL_M10_BMC
deleted file mode 100644
index f38da74c6fc7..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_MFD_INTEL_M10_BMC
+++ /dev/null
@@ -1,22 +0,0 @@
-# CONFIG_MFD_INTEL_M10_BMC:
-#
-# Support for the Intel MAX 10 board management controller using the
-# SPI interface.
-#
-# 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_INTEL_M10_BMC [=n]
-# Type : tristate
-# Defined at drivers/mfd/Kconfig:2156
-# Prompt: Intel MAX 10 Board Management Controller
-# Depends on: HAS_IOMEM [=y] && SPI_MASTER [=y]
-# Location:
-# -> Device Drivers
-# -> Multifunction device drivers
-# Selects: REGMAP_SPI_AVMM [=n] && MFD_CORE [=y]
-#
-#
-#
-# CONFIG_MFD_INTEL_M10_BMC is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_MFD_SL28CPLD b/redhat/configs/pending-common/generic/CONFIG_MFD_SL28CPLD
deleted file mode 100644
index 78b3a4d3da71..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_MFD_SL28CPLD
+++ /dev/null
@@ -1,21 +0,0 @@
-# CONFIG_MFD_SL28CPLD:
-#
-# Say yes here to enable support for the Kontron sl28cpld board
-# management controller.
-#
-# It can be found on the following boards:
-# * SMARC-sAL28
-#
-# Symbol: MFD_SL28CPLD [=n]
-# Type : tristate
-# Defined at drivers/mfd/Kconfig:1189
-# Prompt: Kontron sl28cpld Board Management Controller
-# Depends on: HAS_IOMEM [=y] && I2C [=y]
-# Location:
-# -> Device Drivers
-# -> Multifunction device drivers
-# Selects: MFD_SIMPLE_MFD_I2C [=n]
-#
-#
-#
-# CONFIG_MFD_SL28CPLD is not set
--
GitLab
8 hours, 17 minutes
