[OS-BUILD PATCH] [redhat] New configs in drivers/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_MCP251XFD:
Driver for the Microchip MCP251XFD SPI FD-CAN controller
family.
Symbol: CAN_MCP251XFD [=n]
Type : tristate
Defined at drivers/net/can/spi/mcp251xfd/Kconfig:3
Prompt: Microchip MCP251xFD SPI CAN controllers
Depends on: NET [=y] && CAN [=m] && CAN_DEV [=m] && SPI [=y]
Location:
-> Networking support (NET [=y])
-> CAN bus subsystem support (CAN [=m])
-> CAN Device Drivers
-> Platform CAN drivers with Netlink support (CAN_DEV [=m])
-> CAN SPI interfaces
Selects: REGMAP [=y]
---
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_CAN_MCP251XFD | 1 +
.../generic/CONFIG_CAN_MCP251XFD | 21 -------------------
2 files changed, 1 insertion(+), 21 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_CAN_MCP251XFD
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_CAN_MCP251XFD
diff --git a/redhat/configs/common/generic/CONFIG_CAN_MCP251XFD b/redhat/configs/common/generic/CONFIG_CAN_MCP251XFD
new file mode 100644
index 000000000000..ba4b9f992ff9
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_CAN_MCP251XFD
@@ -0,0 +1 @@
+# CONFIG_CAN_MCP251XFD is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_CAN_MCP251XFD b/redhat/configs/pending-common/generic/CONFIG_CAN_MCP251XFD
deleted file mode 100644
index a6fef51cc94b..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_CAN_MCP251XFD
+++ /dev/null
@@ -1,21 +0,0 @@
-# CONFIG_CAN_MCP251XFD:
-#
-# Driver for the Microchip MCP251XFD SPI FD-CAN controller
-# family.
-#
-# Symbol: CAN_MCP251XFD [=n]
-# Type : tristate
-# Defined at drivers/net/can/spi/mcp251xfd/Kconfig:3
-# Prompt: Microchip MCP251xFD SPI CAN controllers
-# Depends on: NET [=y] && CAN [=m] && CAN_DEV [=m] && SPI [=y]
-# Location:
-# -> Networking support (NET [=y])
-# -> CAN bus subsystem support (CAN [=m])
-# -> CAN Device Drivers
-# -> Platform CAN drivers with Netlink support (CAN_DEV [=m])
-# -> CAN SPI interfaces
-# Selects: REGMAP [=y]
-#
-#
-#
-# CONFIG_CAN_MCP251XFD is not set
--
GitLab
2 years, 11 months
[OS-BUILD PATCH] [redhat] New configs in arch/s390
by GitLab Bridge on behalf of redhat-patchlab
From: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
Hi,
As part of the ongoing rebase effort, the following configuration
options need to be reviewed.
As a reminder, the ARK configuration flow involves moving unreviewed
configuration options from the pending directory to the ark directory.
In the diff below, options are removed from the pending directory and
added to the ark hierarchy. The final options that need to be ACKed
are the files that are being added to the ark hierarchy.
If the value for a file that is added should be changed, please reply
with a better option.
CONFIG_DEBUG_USER_ASCE:
Check on exit to user space that address space control
elements are setup correctly.
If unsure, say N.
Symbol: DEBUG_USER_ASCE [=n]
Type : bool
Defined at arch/s390/Kconfig.debug:9
Prompt: Debug User ASCE
Location:
-> Kernel hacking
-> s390 Debugging
---
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_DEBUG_USER_ASCE | 1 +
.../generic/CONFIG_DEBUG_USER_ASCE | 18 ------------------
2 files changed, 1 insertion(+), 18 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_DEBUG_USER_ASCE
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_DEBUG_USER_ASCE
diff --git a/redhat/configs/common/generic/CONFIG_DEBUG_USER_ASCE b/redhat/configs/common/generic/CONFIG_DEBUG_USER_ASCE
new file mode 100644
index 000000000000..8a8327065991
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_DEBUG_USER_ASCE
@@ -0,0 +1 @@
+# CONFIG_DEBUG_USER_ASCE is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_DEBUG_USER_ASCE b/redhat/configs/pending-common/generic/CONFIG_DEBUG_USER_ASCE
deleted file mode 100644
index aeaa452caae0..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_DEBUG_USER_ASCE
+++ /dev/null
@@ -1,18 +0,0 @@
-# CONFIG_DEBUG_USER_ASCE:
-#
-# Check on exit to user space that address space control
-# elements are setup correctly.
-#
-# If unsure, say N.
-#
-# Symbol: DEBUG_USER_ASCE [=n]
-# Type : bool
-# Defined at arch/s390/Kconfig.debug:9
-# Prompt: Debug User ASCE
-# Location:
-# -> Kernel hacking
-# -> s390 Debugging
-#
-#
-#
-# CONFIG_DEBUG_USER_ASCE is not set
--
GitLab
2 years, 11 months
[OS-BUILD PATCH] [redhat] New configs in fs/fuse
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_FUSE_DAX:
This allows bypassing guest page cache and allows mapping host page
cache directly in guest address space.
If you want to allow mounting a Virtio Filesystem with the "dax"
option, answer Y.
Symbol: FUSE_DAX [=y]
Type : bool
Defined at fs/fuse/Kconfig:42
Prompt: Virtio Filesystem Direct Host Memory Access support
Depends on: VIRTIO_FS [=m] && FS_DAX [=y] && DAX_DRIVER [=y]
Location:
-> File systems
-> FUSE (Filesystem in Userspace) support (FUSE_FS [=m])
-> Virtio Filesystem (VIRTIO_FS [=m])
Selects: INTERVAL_TREE [=y]
---
Cc: Miklos Szeredi <mszeredi(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
redhat/configs/common/generic/CONFIG_FUSE_DAX | 1 +
.../pending-common/generic/CONFIG_FUSE_DAX | 22 -------------------
2 files changed, 1 insertion(+), 22 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_FUSE_DAX
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_FUSE_DAX
diff --git a/redhat/configs/common/generic/CONFIG_FUSE_DAX b/redhat/configs/common/generic/CONFIG_FUSE_DAX
new file mode 100644
index 000000000000..cc453d1c5bc7
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_FUSE_DAX
@@ -0,0 +1 @@
+CONFIG_FUSE_DAX=y
diff --git a/redhat/configs/pending-common/generic/CONFIG_FUSE_DAX b/redhat/configs/pending-common/generic/CONFIG_FUSE_DAX
deleted file mode 100644
index 69992890efd9..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_FUSE_DAX
+++ /dev/null
@@ -1,22 +0,0 @@
-# CONFIG_FUSE_DAX:
-#
-# This allows bypassing guest page cache and allows mapping host page
-# cache directly in guest address space.
-#
-# If you want to allow mounting a Virtio Filesystem with the "dax"
-# option, answer Y.
-#
-# Symbol: FUSE_DAX [=y]
-# Type : bool
-# Defined at fs/fuse/Kconfig:42
-# Prompt: Virtio Filesystem Direct Host Memory Access support
-# Depends on: VIRTIO_FS [=m] && FS_DAX [=y] && DAX_DRIVER [=y]
-# Location:
-# -> File systems
-# -> FUSE (Filesystem in Userspace) support (FUSE_FS [=m])
-# -> Virtio Filesystem (VIRTIO_FS [=m])
-# Selects: INTERVAL_TREE [=y]
-#
-#
-#
-CONFIG_FUSE_DAX=y
--
GitLab
2 years, 11 months
[OS-BUILD PATCH] [redhat] New configs in drivers/ntb
by CKI Gitlab (via Email Bridge)
From: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
[redhat] New configs in drivers/ntb
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_NTB_EPF:
This driver supports EPF NTB on configurable endpoint.
If unsure, say N.
Symbol: NTB_EPF [=n]
Type : tristate
Defined at drivers/ntb/hw/epf/Kconfig:1
Prompt: Generic EPF Non-Transparent Bridge support
Depends on: NTB [=m] && m && MODULES [=y]
Location:
-> Device Drivers
-> Non-Transparent Bridge support (NTB [=m])
---
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
diff a/redhat/configs/common/generic/CONFIG_NTB_EPF b/redhat/configs/common/generic/CONFIG_NTB_EPF
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_NTB_EPF
@@ -0,0 +1 @@
+# CONFIG_NTB_EPF is not set
diff a/redhat/configs/pending-common/generic/CONFIG_NTB_EPF b/redhat/configs/pending-common/generic/CONFIG_NTB_EPF
--- a/redhat/configs/pending-common/generic/CONFIG_NTB_EPF
+++ /dev/null
@@ -1,17 +0,0 @@
-# CONFIG_NTB_EPF:
-#
-# This driver supports EPF NTB on configurable endpoint.
-# If unsure, say N.
-#
-# Symbol: NTB_EPF [=n]
-# Type : tristate
-# Defined at drivers/ntb/hw/epf/Kconfig:1
-# Prompt: Generic EPF Non-Transparent Bridge support
-# Depends on: NTB [=m] && m && MODULES [=y]
-# Location:
-# -> Device Drivers
-# -> Non-Transparent Bridge support (NTB [=m])
-#
-#
-#
-# CONFIG_NTB_EPF is not set
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/930
2 years, 11 months
[OS-BUILD PATCH] [redhat] New configs in drivers/cxl
by CKI Gitlab (via Email Bridge)
From: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
[redhat] New configs in drivers/cxl
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_CXL_BUS:
CXL is a bus that is electrically compatible with PCI Express, but
layers three protocols on that signalling (CXL.io, CXL.cache, and
CXL.mem). The CXL.cache protocol allows devices to hold cachelines
locally, the CXL.mem protocol allows devices to be fully coherent
memory targets, the CXL.io protocol is equivalent to PCI Express.
Say 'y' to enable support for the configuration and management of
devices supporting these protocols.
Symbol: CXL_BUS [=n]
Type : tristate
Defined at drivers/cxl/Kconfig:2
Prompt: CXL (Compute Express Link) Devices Support
Depends on: PCI [=y]
Location:
-> Device Drivers
-> PCI support (PCI [=y])
---
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
diff a/redhat/configs/common/generic/CONFIG_CXL_BUS b/redhat/configs/common/generic/CONFIG_CXL_BUS
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_CXL_BUS
@@ -0,0 +1 @@
+# CONFIG_CXL_BUS is not set
diff a/redhat/configs/pending-common/generic/CONFIG_CXL_BUS b/redhat/configs/pending-common/generic/CONFIG_CXL_BUS
--- a/redhat/configs/pending-common/generic/CONFIG_CXL_BUS
+++ /dev/null
@@ -1,22 +0,0 @@
-# CONFIG_CXL_BUS:
-#
-# CXL is a bus that is electrically compatible with PCI Express, but
-# layers three protocols on that signalling (CXL.io, CXL.cache, and
-# CXL.mem). The CXL.cache protocol allows devices to hold cachelines
-# locally, the CXL.mem protocol allows devices to be fully coherent
-# memory targets, the CXL.io protocol is equivalent to PCI Express.
-# Say 'y' to enable support for the configuration and management of
-# devices supporting these protocols.
-#
-# Symbol: CXL_BUS [=n]
-# Type : tristate
-# Defined at drivers/cxl/Kconfig:2
-# Prompt: CXL (Compute Express Link) Devices Support
-# Depends on: PCI [=y]
-# Location:
-# -> Device Drivers
-# -> PCI support (PCI [=y])
-#
-#
-#
-# CONFIG_CXL_BUS is not set
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/927
2 years, 11 months
[OS-BUILD PATCH] [redhat] New configs in drivers/thunderbolt
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_USB4_DEBUGFS_WRITE:
Enables writing to device configuration registers through
debugfs interface.
Only enable this if you know what you are doing! Never enable
this for production systems or distro kernels.
Symbol: USB4_DEBUGFS_WRITE [=n]
Type : bool
Defined at drivers/thunderbolt/Kconfig:21
Prompt: Enable write by debugfs to configuration spaces (DANGEROUS)
Depends on: USB4 [=y]
Location:
-> Device Drivers
-> Unified support for USB4 and Thunderbolt (USB4 [=y])
---
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_USB4_DEBUGFS_WRITE | 1 +
.../generic/CONFIG_USB4_DEBUGFS_WRITE | 20 -------------------
2 files changed, 1 insertion(+), 20 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_USB4_DEBUGFS_WRITE
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_USB4_DEBUGFS_WRITE
diff --git a/redhat/configs/common/generic/CONFIG_USB4_DEBUGFS_WRITE b/redhat/configs/common/generic/CONFIG_USB4_DEBUGFS_WRITE
new file mode 100644
index 000000000000..966dff9102ad
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_USB4_DEBUGFS_WRITE
@@ -0,0 +1 @@
+# CONFIG_USB4_DEBUGFS_WRITE is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_USB4_DEBUGFS_WRITE b/redhat/configs/pending-common/generic/CONFIG_USB4_DEBUGFS_WRITE
deleted file mode 100644
index 4aa0125ab425..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_USB4_DEBUGFS_WRITE
+++ /dev/null
@@ -1,20 +0,0 @@
-# CONFIG_USB4_DEBUGFS_WRITE:
-#
-# Enables writing to device configuration registers through
-# debugfs interface.
-#
-# Only enable this if you know what you are doing! Never enable
-# this for production systems or distro kernels.
-#
-# Symbol: USB4_DEBUGFS_WRITE [=n]
-# Type : bool
-# Defined at drivers/thunderbolt/Kconfig:21
-# Prompt: Enable write by debugfs to configuration spaces (DANGEROUS)
-# Depends on: USB4 [=y]
-# Location:
-# -> Device Drivers
-# -> Unified support for USB4 and Thunderbolt (USB4 [=y])
-#
-#
-#
-# CONFIG_USB4_DEBUGFS_WRITE is not set
--
GitLab
2 years, 11 months
[OS-BUILD PATCH] drm/i915/tgl/psr: Disable PSR on Tigerlake for now
by Lyude Paul (via Email Bridge)
From: Lyude Paul <lyude(a)redhat.com>
drm/i915/tgl/psr: Disable PSR on Tigerlake for now
Currently PSR2 appears to be broken on TGL which causes some pretty nasty
refresh issues. Intel doesn't have a fix for this quite yet, and this
definitely affects a couple of OEM machines shipping with Fedora.
We don't have a better workaround for the time being, so just disable PSR2
outright for Tigerlake by default until this gets fixed.
Signed-off-by: Lyude Paul <lyude(a)redhat.com>
Cc: Jared Dominguez <jaredz(a)redhat.com>
Cc: Mark Pearson <markpearson(a)lenovo.com>
Bugzilla: https://gitlab.freedesktop.org/drm/intel/-/issues/3134
diff a/drivers/gpu/drm/i915/display/intel_psr.c b/drivers/gpu/drm/i915/display/intel_psr.c
--- a/drivers/gpu/drm/i915/display/intel_psr.c
+++ b/drivers/gpu/drm/i915/display/intel_psr.c
@@ -1817,9 +1817,14 @@ void intel_psr_init(struct drm_i915_private *dev_priv)
*/
dev_priv->hsw_psr_mmio_adjust = _SRD_CTL_EDP - _HSW_EDP_PSR_BASE;
- if (dev_priv->params.enable_psr == -1)
- if (INTEL_GEN(dev_priv) < 9 || !dev_priv->vbt.psr.enable)
+ if (dev_priv->params.enable_psr == -1) {
+ if (INTEL_GEN(dev_priv) < 9 || !dev_priv->vbt.psr.enable) {
dev_priv->params.enable_psr = 0;
+ } else if (INTEL_GEN(dev_priv) == 12) {
+ /* See https://gitlab.freedesktop.org/drm/intel/-/issues/3134 */
+ dev_priv->params.enable_psr = 0;
+ }
+ }
/* Set link_standby x link_off defaults */
if (IS_HASWELL(dev_priv) || IS_BROADWELL(dev_priv))
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/981
2 years, 11 months
[OS-BUILD PATCH] redhat/Makefile.common: Fix 'fatal: Not a valid
object name
master' error
by GitLab Bridge on behalf of prarit
From: Prarit Bhargava <prarit(a)redhat.com>
Hey everyone,
I spent 5-10 mins looking at the 'fatal: Not a valid object name master' error
this morning. It comes from the redhat/Makefile.common:45
MERGE_BASE:=$(shell git merge-base HEAD master)
There is no master branch so 'git merge-base HEAD master' returns an error
with message 'fatal: Not a valid object name master'.
If I add a Makefile target to dump the MERGE_BASE, TAG, and SNAPSHOT
variables I get
MERGE_BASE= TAG=v5.8-rc7-1028-g305981a20220 SNAPSHOT=1
I thought about changing the MERGE_BASE value to
MERGE_BASE:=$(shell git merge-base HEAD master >& /dev/null && git merge-base HEAD master || git merge-base HEAD upstream/master)
but that seems really clunky. Anyone have a better idea? Maybe it should only
be
MERGE_BASE:$(git merge-base HEAD upstream/master) ?
In any case, after changing the MERGE_BASE line in Makefile.common, and
dumping the values the 'fatal' error no longer occurs and MERGE_BASE
is set correctly:
MERGE_BASE=d3590ebf6f91350192737dd1d1b219c05277f067 TAG=v5.8-rc7-39-gd3590ebf6f91 SNAPSHOT=1
P.
---8<----
Executing some redhat/Makefile targets results in a
'fatal: Not a valid object name master'
error. This occurs because MERGE_BASE is calculated against the master
branch which may not exist.
Check to see if master branch exists and if it doesn't use upstream/master
instead.
Signed-off-by: Prarit Bhargava <prarit(a)redhat.com>
---
redhat/Makefile.common | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/redhat/Makefile.common b/redhat/Makefile.common
index 6d048415ba6d..e67f2c9dec50 100644
--- a/redhat/Makefile.common
+++ b/redhat/Makefile.common
@@ -41,8 +41,7 @@ else
VERSION_ON_UPSTREAM:=0
endif
ifeq ($(VERSION_ON_UPSTREAM),1)
- # master is expected to track mainline.
- MERGE_BASE:=$(shell git merge-base HEAD master)
+ MERGE_BASE:=$(shell git merge-base HEAD master >& /dev/null && git merge-base HEAD master || git merge-base HEAD upstream/master)
TAG:=$(shell git describe $(MERGE_BASE))
# a snapshot off of a tagged git is of the form [tag]-[cnt]-g[hash]
SNAPSHOT:=$(shell echo $(TAG) | grep -c '\-g')
--
GitLab
2 years, 11 months
[OS-BUILD PATCH] iommu/vt-d: enable INTEL_IDXD_SVM for both fedora
and rhel
by Jerry Snitselaar (via Email Bridge)
From: Jerry Snitselaar <jsnitsel(a)redhat.com>
iommu/vt-d: enable INTEL_IDXD_SVM for both fedora and rhel
It is already enabled for Fedora, so move to common/generic/x86.
Signed-off-by: Jerry Snitselaar <jsnitsel(a)redhat.com>
diff a/redhat/configs/fedora/generic/x86/CONFIG_INTEL_IDXD_SVM b/redhat/configs/common/generic/x86/CONFIG_INTEL_IDXD_SVM
--- a/redhat/configs/fedora/generic/x86/CONFIG_INTEL_IDXD_SVM
+++ b/redhat/configs/common/generic/x86/CONFIG_INTEL_IDXD_SVM
diff a/redhat/configs/pending-common/generic/CONFIG_INTEL_IDXD_SVM b/redhat/configs/pending-common/generic/CONFIG_INTEL_IDXD_SVM
--- a/redhat/configs/pending-common/generic/CONFIG_INTEL_IDXD_SVM
+++ /dev/null
@@ -1 +0,0 @@
-# CONFIG_INTEL_IDXD_SVM is not set
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/898
2 years, 11 months