[OS-BUILD PATCH] [redhat] New configs in net/bluetooth
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_BT_MSFTEXT:
This options enables support for the Microsoft defined HCI
vendor extensions.
Symbol: BT_MSFTEXT [=n]
Type : bool
Defined at net/bluetooth/Kconfig:96
Prompt: Enable Microsoft extensions
Depends on: NET [=y] && BT [=m]
Location:
-> Networking support (NET [=y])
-> Bluetooth subsystem support (BT [=m])
---
Signed-off-by: Justin M. Forbes <jforbes(a)fedoraproject.org>
---
redhat/configs/common/generic/CONFIG_BT_MSFTEXT | 1 +
.../pending-common/generic/CONFIG_BT_MSFTEXT | 17 -----------------
2 files changed, 1 insertion(+), 17 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_BT_MSFTEXT
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_BT_MSFTEXT
diff --git a/redhat/configs/common/generic/CONFIG_BT_MSFTEXT b/redhat/configs/common/generic/CONFIG_BT_MSFTEXT
new file mode 100644
index 000000000000..7fae871b2426
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_BT_MSFTEXT
@@ -0,0 +1 @@
+# CONFIG_BT_MSFTEXT is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_BT_MSFTEXT b/redhat/configs/pending-common/generic/CONFIG_BT_MSFTEXT
deleted file mode 100644
index b93c24c93f7f..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_BT_MSFTEXT
+++ /dev/null
@@ -1,17 +0,0 @@
-# CONFIG_BT_MSFTEXT:
-#
-# This options enables support for the Microsoft defined HCI
-# vendor extensions.
-#
-# Symbol: BT_MSFTEXT [=n]
-# Type : bool
-# Defined at net/bluetooth/Kconfig:96
-# Prompt: Enable Microsoft extensions
-# Depends on: NET [=y] && BT [=m]
-# Location:
-# -> Networking support (NET [=y])
-# -> Bluetooth subsystem support (BT [=m])
-#
-#
-#
-# CONFIG_BT_MSFTEXT is not set
--
2.26.2
3 years, 1 month
[OS-BUILD PATCH] [redhat] New configs in
drivers/net/ethernet/mellanox
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_MLX5_CLS_ACT:
mlx5 ConnectX offloads support for TC classifier action (NET_CLS_ACT),
works in both native NIC mode and Switchdev SRIOV mode.
Actions get attached to a Hardware offloaded classifiers and are
invoked after a successful classification. Actions are used to
overwrite the classification result, instantly drop or redirect and/or
reformat packets in wire speeds without involving the host cpu.
If set to N, TC offloads in both NIC and switchdev modes will be disabled.
If unsure, set to Y
Symbol: MLX5_CLS_ACT [=y]
Type : bool
Defined at drivers/net/ethernet/mellanox/mlx5/core/Kconfig:81
Prompt: MLX5 TC classifier action support
Depends on: NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_MELLANOX [=y] && MLX5_ESWITCH [=y] && NET_CLS_ACT [=y]
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> Ethernet driver support (ETHERNET [=y])
-> Mellanox devices (NET_VENDOR_MELLANOX [=y])
-> Mellanox 5th generation network adapters (ConnectX series) Ethernet support (MLX5_CORE_EN [=y])
-> Mellanox Technologies MLX5 SRIOV E-Switch support (MLX5_ESWITCH [=y])
---
Signed-off-by: Justin M. Forbes <jforbes(a)fedoraproject.org>
---
.../common/generic/CONFIG_MLX5_CLS_ACT | 1 +
.../generic/CONFIG_MLX5_CLS_ACT | 28 -------------------
2 files changed, 1 insertion(+), 28 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_MLX5_CLS_ACT
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_MLX5_CLS_ACT
diff --git a/redhat/configs/common/generic/CONFIG_MLX5_CLS_ACT b/redhat/configs/common/generic/CONFIG_MLX5_CLS_ACT
new file mode 100644
index 000000000000..2ff38eef7747
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_MLX5_CLS_ACT
@@ -0,0 +1 @@
+CONFIG_MLX5_CLS_ACT=y
diff --git a/redhat/configs/pending-common/generic/CONFIG_MLX5_CLS_ACT b/redhat/configs/pending-common/generic/CONFIG_MLX5_CLS_ACT
deleted file mode 100644
index 0dd0c3000053..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_MLX5_CLS_ACT
+++ /dev/null
@@ -1,28 +0,0 @@
-# CONFIG_MLX5_CLS_ACT:
-#
-# mlx5 ConnectX offloads support for TC classifier action (NET_CLS_ACT),
-# works in both native NIC mode and Switchdev SRIOV mode.
-# Actions get attached to a Hardware offloaded classifiers and are
-# invoked after a successful classification. Actions are used to
-# overwrite the classification result, instantly drop or redirect and/or
-# reformat packets in wire speeds without involving the host cpu.
-#
-# If set to N, TC offloads in both NIC and switchdev modes will be disabled.
-# If unsure, set to Y
-#
-# Symbol: MLX5_CLS_ACT [=y]
-# Type : bool
-# Defined at drivers/net/ethernet/mellanox/mlx5/core/Kconfig:81
-# Prompt: MLX5 TC classifier action support
-# Depends on: NETDEVICES [=y] && ETHERNET [=y] && NET_VENDOR_MELLANOX [=y] && MLX5_ESWITCH [=y] && NET_CLS_ACT [=y]
-# Location:
-# -> Device Drivers
-# -> Network device support (NETDEVICES [=y])
-# -> Ethernet driver support (ETHERNET [=y])
-# -> Mellanox devices (NET_VENDOR_MELLANOX [=y])
-# -> Mellanox 5th generation network adapters (ConnectX series) Ethernet support (MLX5_CORE_EN [=y])
-# -> Mellanox Technologies MLX5 SRIOV E-Switch support (MLX5_ESWITCH [=y])
-#
-#
-#
-CONFIG_MLX5_CLS_ACT=y
--
2.26.2
3 years, 1 month
[OS-BUILD PATCH] [redhat] New configs in init/Kconfig
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_WATCH_QUEUE:
This is a general notification queue for the kernel to pass events to
userspace by splicing them into pipes. It can be used in conjunction
with watches for key/keyring change notifications and device
notifications.
See Documentation/watch_queue.rst
Symbol: WATCH_QUEUE [=n]
Type : bool
Defined at init/Kconfig:370
Prompt: General notification queue
Location:
-> General setup
---
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../configs/common/generic/CONFIG_WATCH_QUEUE | 1 +
.../pending-common/generic/CONFIG_WATCH_QUEUE | 20 -------------------
2 files changed, 1 insertion(+), 20 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_WATCH_QUEUE
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_WATCH_QUEUE
diff --git a/redhat/configs/common/generic/CONFIG_WATCH_QUEUE b/redhat/configs/common/generic/CONFIG_WATCH_QUEUE
new file mode 100644
index 000000000000..4e2060b85ff3
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_WATCH_QUEUE
@@ -0,0 +1 @@
+# CONFIG_WATCH_QUEUE is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_WATCH_QUEUE b/redhat/configs/pending-common/generic/CONFIG_WATCH_QUEUE
deleted file mode 100644
index 11707e6429cb..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_WATCH_QUEUE
+++ /dev/null
@@ -1,20 +0,0 @@
-# CONFIG_WATCH_QUEUE:
-#
-#
-# This is a general notification queue for the kernel to pass events to
-# userspace by splicing them into pipes. It can be used in conjunction
-# with watches for key/keyring change notifications and device
-# notifications.
-#
-# See Documentation/watch_queue.rst
-#
-# Symbol: WATCH_QUEUE [=n]
-# Type : bool
-# Defined at init/Kconfig:370
-# Prompt: General notification queue
-# Location:
-# -> General setup
-#
-#
-#
-# CONFIG_WATCH_QUEUE is not set
--
GitLab
3 years, 1 month
[OS-BUILD PATCH] RHMAINTAINERS: Update DMA Mapping entry
by GitLab Bridge on behalf of prarit
From: Jerry Snitselaar <jsnitsel(a)redhat.com>
I'm taking over the primary role for DMA Mapping
so update the maintainers entry.
RH-Acked-by: Myron Stowe <mstowe(a)redhat.com
RH-Acked-by: Don Dutile <ddutile(a)redhat.com>
Cc: Prarit Bhargava <prarit(a)redhat.com>
Cc: Donald Dutile <ddutile(a)redhat.com>
Signed-off-by: Jerry Snitselaar <jsnitsel(a)redhat.com>
---
redhat/rhdocs/MAINTAINERS/RHMAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/redhat/rhdocs/MAINTAINERS/RHMAINTAINERS b/redhat/rhdocs/MAINTAINERS/RHMAINTAINERS
index dda356a9d5e9..df60e8537ff2 100644
--- a/redhat/rhdocs/MAINTAINERS/RHMAINTAINERS
+++ b/redhat/rhdocs/MAINTAINERS/RHMAINTAINERS
@@ -503,6 +503,7 @@ S: Maintained
F: drivers/scsi/hpsa*
DMA MAPPING SUPPORT
+M: Jerry Snitselaar <jsnitsel(a)redhat.com>
M: Donald Dutile <ddutile(a)redhat.com>
S: Maintained
F: kernel/dma/*
--
GitLab
3 years, 1 month
[OS-BUILD PATCH] redhat: Implement Makefile.dist
by GitLab Bridge on behalf of prarit
From: Prarit Bhargava <prarit(a)redhat.com>
One of the nice things about the RHEL and ARK trees is that commands like
'make dist-configs' and 'make dist-help' can be executed from the
top-level linux directory.
In the existing code, the makefile includes the top-level linux Makefile
if the targets are not dist-* or distg-*. Otherwise the commands are
executed with the redhat/Makefile* files. This is clunky and requires the
inclusion of the makefile in .gitignore which causes problems when
upstream modifies .gitignore.
A better approach is to include the code in a top-level Makefile.dist.
This change can then be moved upstream for inclusion with a oneline patch
to include Makefile.dist. Makefile.dist would not be included in the
gitignore file because we want to track changes for the file in our
own tree.
Move the makefile and Makefile.rhelver code into Makefile.dist, and
include Makefile.dist from the top-level Makefile.
Signed-off-by: Prarit Bhargava <prarit(a)redhat.com>
Cc: dzickus(a)redhat.com
Cc: jforbes(a)redhat.com
Cc: bcrocker(a)redhat.com
---
Makefile | 6 ++----
Makefile.rhelver => Makefile.dist | 19 ++++++++++++++++++-
makefile | 16 ----------------
redhat/Makefile | 4 ++--
redhat/Makefile.common | 2 +-
redhat/genspec.sh | 2 +-
redhat/kernel.spec.template | 2 +-
redhat/scripts/new_release.sh | 12 ++++++------
8 files changed, 31 insertions(+), 32 deletions(-)
rename Makefile.rhelver => Makefile.dist (77%)
delete mode 100644 makefile
diff --git a/Makefile b/Makefile
index f3d1dd649d9b..c9a0d4f20808 100644
--- a/Makefile
+++ b/Makefile
@@ -18,10 +18,6 @@ $(if $(filter __%, $(MAKECMDGOALS)), \
PHONY := __all
__all:
-# Set RHEL variables
-# Use this spot to avoid future merge conflicts
-include Makefile.rhelver
-
# We are using a recursive build, so we need to do a little thinking
# to get the ordering right.
#
@@ -273,6 +269,8 @@ no-sync-config-targets := $(no-dot-config-targets) install %install \
kernelrelease
single-targets := %.a %.i %.ko %.lds %.ll %.lst %.mod %.o %.s %.symtypes %/
+-include Makefile.dist
+
config-build :=
mixed-build :=
need-config := 1
diff --git a/Makefile.rhelver b/Makefile.dist
similarity index 77%
rename from Makefile.rhelver
rename to Makefile.dist
index 8fceabade7c8..0b4f2d28e7b8 100644
--- a/Makefile.rhelver
+++ b/Makefile.dist
@@ -12,7 +12,7 @@ RHEL_MINOR = 99
#
# Use this spot to avoid future merge conflicts.
# Do not trim this comment.
-RHEL_RELEASE = 0
+RHEL_RELEASE = 1
#
# Early y+1 numbering
@@ -43,3 +43,20 @@ ifneq ("$(ZSTREAM)", "yes")
RHEL_RELEASE:=$(RHEL_RELEASE).$(EARLY_YRELEASE)
endif
endif
+
+no-dot-config-targets += dist-% distg-%
+
+ifneq ($(filter dist-% distg-%,$(MAKECMDGOALS)),)
+_OUTPUT := "."
+# this section is needed in order to make O= to work
+ifeq ("$(origin O)", "command line")
+ _OUTPUT := "$(abspath $(O))"
+ _EXTRA_ARGS := O=$(_OUTPUT)
+endif
+endif
+
+dist-%::
+ $(MAKE) -C redhat $(@) $(_EXTRA_ARGS)
+
+distg-%::
+ $(MAKE) -C redhat $(@) $(_EXTRA_ARGS)
diff --git a/makefile b/makefile
deleted file mode 100644
index 819ac9a5cd60..000000000000
--- a/makefile
+++ /dev/null
@@ -1,16 +0,0 @@
-ifeq ($(filter dist-% distg-%,$(MAKECMDGOALS)),)
- include Makefile
-endif
-
-_OUTPUT := "."
-# this section is needed in order to make O= to work
-ifeq ("$(origin O)", "command line")
- _OUTPUT := "$(abspath $(O))"
- _EXTRA_ARGS := O=$(_OUTPUT)
-endif
-dist-%::
- $(MAKE) -C redhat $(@) $(_EXTRA_ARGS)
-
-distg-%::
- $(MAKE) -C redhat $(@) $(_EXTRA_ARGS)
-
diff --git a/redhat/Makefile b/redhat/Makefile
index 61dcc522fbc6..8c6a3a510768 100644
--- a/redhat/Makefile
+++ b/redhat/Makefile
@@ -256,7 +256,7 @@ sources-rh: $(TARBALL)
configs/process_configs.sh \
parallel_xz.sh \
generate_bls_conf.sh \
- ../Makefile.rhelver \
+ ../Makefile.dist \
README.rst \
$(SOURCES)/
@for KABIARCH in $(ARCH_LIST); do \
@@ -308,7 +308,7 @@ dist-release-finish: setup-source
@git add $(REDHAT)/$(CHANGELOG)
@echo $(MARKER) > $(REDHAT)/marker
@git add $(REDHAT)/marker
- @git commit -s ../Makefile.rhelver $(REDHAT)/marker $(REDHAT)/$(CHANGELOG) $(PACKAGE_NAME).spec.template -m "[redhat] $(PACKAGE_NAME)-$(STAMP_VERSION)-$(PREBUILD)$(BUILD)$(BUILDID)"
+ @git commit -s ../Makefile.dist $(REDHAT)/marker $(REDHAT)/$(CHANGELOG) $(PACKAGE_NAME).spec.template -m "[redhat] $(PACKAGE_NAME)-$(STAMP_VERSION)-$(PREBUILD)$(BUILD)$(BUILDID)"
@$(MAKE) dist-configs
@$(MAKE) dist-kabi
@$(MAKE) dist-kabi-dup
diff --git a/redhat/Makefile.common b/redhat/Makefile.common
index 6d048415ba6d..d4e68369fb05 100644
--- a/redhat/Makefile.common
+++ b/redhat/Makefile.common
@@ -1,6 +1,6 @@
TOPDIR:=$(shell git rev-parse --show-toplevel)
REDHAT:=$(TOPDIR)/redhat
-include $(TOPDIR)/Makefile.rhelver
+include $(TOPDIR)/Makefile.dist
RPMBUILD := $(shell if [ -x "/usr/bin/rpmbuild" ]; then echo rpmbuild; \
else echo rpm; fi)
diff --git a/redhat/genspec.sh b/redhat/genspec.sh
index b72dffe14729..1cd9095a69ea 100755
--- a/redhat/genspec.sh
+++ b/redhat/genspec.sh
@@ -253,7 +253,7 @@ if [ "$SINGLE_TARBALL" = 0 ]; then
":(exclude,top).gitignore" \
":(exclude,top).gitlab-ci.yml" \
":(exclude,top)makefile" \
- ":(exclude,top)Makefile.rhelver" \
+ ":(exclude,top)Makefile.dist" \
":(exclude,top)redhat")
for c in $COMMITS; do
patch=$(git format-patch --zero-commit -1 "$c")
diff --git a/redhat/kernel.spec.template b/redhat/kernel.spec.template
index d47c9cce8a0e..93fa8c2985b1 100644
--- a/redhat/kernel.spec.template
+++ b/redhat/kernel.spec.template
@@ -569,7 +569,7 @@ BuildRequires: asciidoc
# xzcat -qq ${TARBALL} | git get-tar-commit-id
Source0: linux-%%TARBALL_VERSION%%.tar.xz
-Source1: Makefile.rhelver
+Source1: Makefile.dist
# Name of the packaged file containing signing key
diff --git a/redhat/scripts/new_release.sh b/redhat/scripts/new_release.sh
index 1e4c7bb1dc86..f1025f458d04 100755
--- a/redhat/scripts/new_release.sh
+++ b/redhat/scripts/new_release.sh
@@ -13,7 +13,7 @@ if [ -s "$RHPATH/linux-kernel-test.patch" ]; then
exit 1;
fi
-RELEASE=$(sed -n -e 's/^RHEL_RELEASE\ =\ \(.*\)/\1/p' $RHPATH/../Makefile.rhelver)
+RELEASE=$(sed -n -e 's/^RHEL_RELEASE\ =\ \(.*\)/\1/p' $RHPATH/../Makefile.dist)
YVER=$(echo $RELEASE | cut -d "." -f 1)
YVER=${YVER:=$RELEASE}
@@ -26,15 +26,15 @@ if [ "$ZSTREAM_FLAG" == "no" ]; then
if [ "$YSTREAM_FLAG" == "yes" ]; then
NEW_RELEASE="$[RELEASE + 1]";
else
- EARLY_YBUILD=$(sed -n -e 's/^EARLY_YBUILD:=\(.*\)/\1/p' $RHPATH/../Makefile.rhelver);
- EARLY_YRELEASE=$(sed -n -e 's/^EARLY_YRELEASE:=\(.*\)/\1/p' $RHPATH/../Makefile.rhelver);
+ EARLY_YBUILD=$(sed -n -e 's/^EARLY_YBUILD:=\(.*\)/\1/p' $RHPATH/../Makefile.dist);
+ EARLY_YRELEASE=$(sed -n -e 's/^EARLY_YRELEASE:=\(.*\)/\1/p' $RHPATH/../Makefile.dist);
if [ "$EARLY_YBUILD" != "$RELEASE" ]; then
NEW_EARLY_YRELEASE=1;
else
NEW_EARLY_YRELEASE="$[EARLY_YRELEASE + 1]";
fi
- sed -i -e "s/^EARLY_YBUILD:=$EARLY_YBUILD/EARLY_YBUILD:=$RELEASE/" $RHPATH/../Makefile.rhelver;
- sed -i -e "s/^EARLY_YRELEASE:=$EARLY_YRELEASE/EARLY_YRELEASE:=$NEW_EARLY_YRELEASE/" $RHPATH/../Makefile.rhelver;
+ sed -i -e "s/^EARLY_YBUILD:=$EARLY_YBUILD/EARLY_YBUILD:=$RELEASE/" $RHPATH/../Makefile.dist;
+ sed -i -e "s/^EARLY_YRELEASE:=$EARLY_YRELEASE/EARLY_YRELEASE:=$NEW_EARLY_YRELEASE/" $RHPATH/../Makefile.dist;
NEW_RELEASE=$RELEASE;
fi
elif [ "$ZSTREAM_FLAG" == "yes" ]; then
@@ -46,5 +46,5 @@ else
exit 1;
fi
-sed -i -e "s/RHEL_RELEASE\ =.*/RHEL_RELEASE\ =\ $NEW_RELEASE/" $RHPATH/../Makefile.rhelver;
+sed -i -e "s/RHEL_RELEASE\ =.*/RHEL_RELEASE\ =\ $NEW_RELEASE/" $RHPATH/../Makefile.dist;
--
GitLab
3 years, 1 month
[OS-BUILD PATCHv2] [redhat] spec: Add %bcond_with toolchain_clang
option
by Tom Stellard (via Email Bridge)
From: Tom Stellard <tstellar(a)redhat.com>
[redhat] spec: Add %bcond_with toolchain_clang option
This option can be enabled by passing --with toolchain_clang to rpmbuild
or mock. Enabling this option will cause the kernel to be built with
clang instead of gcc.
Signed-off-by: Tom Stellard <tstellar(a)redhat.com>
diff a/redhat/kernel.spec.template b/redhat/kernel.spec.template
--- a/redhat/kernel.spec.template
+++ b/redhat/kernel.spec.template
@@ -6,6 +6,12 @@
# Disable LTO in userspace packages.
%global _lto_cflags %{nil}
+# Option to enable compiling with clang instead of gcc.
+%bcond_with toolchain_clang
+
+%if %{with toolchain_clang}
+%global toolchain clang
+%endif
# Cross compile on copr for arm
# See https://bugzilla.redhat.com/1879599
@@ -228,6 +234,10 @@ Summary: The Linux kernel
%define make_opts -s
%endif
+%if %{with toolchain_clang}
+%global make_opts %{make_opts} HOSTCC=clang CC=clang
+%endif
+
# turn off debug kernel and kabichk for gcov builds
%if %{with_gcov}
%define with_debug 0
@@ -432,6 +442,14 @@ Summary: The Linux kernel
%define with_configchecks 0
%endif
+# Setting the compiler to clang enables some different config options
+# than what is expected, so disable this check for now.
+# TODO: What's the best way to fix this? Do wee need a different set of
+# configs for clang?
+%if %{with toolchain_clang}
+%define with_configchecks 0
+%endif
+
# To temporarily exclude an architecture from being built, add it to
# %%nobuildarches. Do _NOT_ use the ExclusiveArch: line, because if we
# don't build kernel-headers then the new build system will no longer let
@@ -596,6 +614,10 @@ BuildRequires: xmlto
BuildRequires: asciidoc
%endif
+%if %{with toolchain_clang}
+BuildRequires: clang
+%endif
+
# Because this is the kernel, it's hard to get a single upstream URL
# to represent the base without needing to do a bunch of patching. This
# tarball is generated from a src-git tree. If you want to see the
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/894
3 years, 1 month
[OS-BUILD PATCH] [redhat] New configs in drivers/pci
by CKI Gitlab (via Email Bridge)
From: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
[redhat] New configs in drivers/pci
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_PCIE_MICROCHIP_HOST:
Say Y here if you want kernel to support the Microchip AXI PCIe
Host Bridge driver.
Symbol: PCIE_MICROCHIP_HOST [=n]
Type : bool
Defined at drivers/pci/controller/Kconfig:278
Prompt: Microchip AXI PCIe host bridge support
Depends on: PCI [=y] && PCI_MSI [=y] && OF [=y]
Location:
-> Device Drivers
-> PCI support (PCI [=y])
-> PCI controller drivers
Selects: PCI_MSI_IRQ_DOMAIN [=y] && GENERIC_MSI_IRQ_DOMAIN [=y] && PCI_HOST_COMMON [=n]
---
Cc: Myron Stowe <myron.stowe(a)redhat.com>
Cc: Prarit Bhargava <prarit(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
diff a/redhat/configs/common/generic/CONFIG_PCIE_MICROCHIP_HOST b/redhat/configs/common/generic/CONFIG_PCIE_MICROCHIP_HOST
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_PCIE_MICROCHIP_HOST
@@ -0,0 +1 @@
+# CONFIG_PCIE_MICROCHIP_HOST is not set
diff a/redhat/configs/pending-common/generic/CONFIG_PCIE_MICROCHIP_HOST b/redhat/configs/pending-common/generic/CONFIG_PCIE_MICROCHIP_HOST
--- a/redhat/configs/pending-common/generic/CONFIG_PCIE_MICROCHIP_HOST
+++ /dev/null
@@ -1,19 +0,0 @@
-# CONFIG_PCIE_MICROCHIP_HOST:
-#
-# Say Y here if you want kernel to support the Microchip AXI PCIe
-# Host Bridge driver.
-#
-# Symbol: PCIE_MICROCHIP_HOST [=n]
-# Type : bool
-# Defined at drivers/pci/controller/Kconfig:278
-# Prompt: Microchip AXI PCIe host bridge support
-# Depends on: PCI [=y] && PCI_MSI [=y] && OF [=y]
-# Location:
-# -> Device Drivers
-# -> PCI support (PCI [=y])
-# -> PCI controller drivers
-# Selects: PCI_MSI_IRQ_DOMAIN [=y] && GENERIC_MSI_IRQ_DOMAIN [=y] && PCI_HOST_COMMON [=n]
-#
-#
-#
-# CONFIG_PCIE_MICROCHIP_HOST is not set
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/932
3 years, 1 month
[OS-BUILD PATCHv2 0/0] [redhat] New configs in drivers/md
by CKI Gitlab (via Email Bridge)
From: CKI Gitlab on gitlab.com
Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/834
NOTE: Truncated patchset due to missing @redhat.com email
address on your GitLab profile at https://gitlab.com/-/profile.
Once that is fixed, close and reopen the merge request to
retrigger sending the emails.
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_DM_MULTIPATH_IOA:
This path selector selects the path based on the CPU the IO is
executed on and the CPU to path mapping setup at path addition time.
If unsure, say N.
Symbol: DM_MULTIPATH_IOA [=n]
Type : tristate
Defined at drivers/md/Kconfig:466
Prompt: I/O Path Selector based on CPU submission
Depends on: MD [=y] && DM_MULTIPATH [=m]
Location:
-> Device Drivers
-> Multiple devices driver support (RAID and LVM) (MD [=y])
-> Device mapper support (BLK_DEV_DM [=m])
-> Multipath target (DM_MULTIPATH [=m])
---
Cc: Nigel Croxon <ncroxon(a)redhat.com>
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
3 years, 1 month
❌ FAIL: Test report for kernel 5.11.8-200.fc33 (fedora-33)
by CKI Project
Hello,
We ran automated tests on the following kernel build:
Kernel package: kernel-5.11.8-200.fc33
Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=64307802
The results of these automated tests are provided below.
Overall result: FAILED (see details below)
Tests: FAILED
One or more kernel tests failed:
ppc64le:
❌ LTP
All kernel binaries, config files, and logs are available for download here:
https://arr-cki-prod-datawarehouse-public.s3.amazonaws.com/index.html?pre...
Please reply to this email if you have any questions about the tests that we
ran or if you have any suggestions on how to make future tests more effective.
For the full detail on our testing procedures, please scroll to the bottom of
this message.
,-. ,-.
( C ) ( K ) Continuous
`-',-.`-' Kernel
( I ) Integration
`-'
______________________________________________________________________________
Hardware testing
----------------
We booted each kernel and ran the following tests:
aarch64:
Host 1:
✅ Boot test
✅ Storage: swraid mdadm raid_module test
🚧 ✅ xfstests - ext4
🚧 ✅ xfstests - xfs
🚧 ✅ xfstests - btrfs
🚧 ✅ Storage blktests
🚧 ✅ Storage block - filesystem fio test
🚧 ✅ Storage block - queue scheduler test
🚧 ✅ Storage nvme - tcp
🚧 ✅ Storage: lvm device-mapper test
🚧 ❌ stress: stress-ng
Host 2:
✅ Boot test
✅ ACPI table test
✅ LTP
✅ CIFS Connectathon
✅ Loopdev Sanity
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
✅ Ethernet drivers sanity
ppc64le:
Host 1:
✅ Boot test
✅ Storage: swraid mdadm raid_module test
🚧 ✅ xfstests - ext4
🚧 ✅ xfstests - xfs
🚧 ✅ xfstests - btrfs
🚧 ✅ Storage blktests
🚧 ✅ Storage block - filesystem fio test
🚧 ✅ Storage block - queue scheduler test
🚧 ✅ Storage nvme - tcp
🚧 ✅ Storage: lvm device-mapper test
Host 2:
✅ Boot test
❌ LTP
✅ CIFS Connectathon
✅ Loopdev Sanity
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
✅ Ethernet drivers sanity
s390x:
Host 1:
✅ Boot test
✅ Storage: swraid mdadm raid_module test
🚧 ✅ Storage blktests
🚧 ✅ Storage nvme - tcp
🚧 ✅ stress: stress-ng
Host 2:
✅ Boot test
✅ LTP
✅ CIFS Connectathon
✅ Loopdev Sanity
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
✅ Ethernet drivers sanity
x86_64:
Host 1:
✅ Boot test
✅ Storage: swraid mdadm raid_module test
🚧 ✅ 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: lvm device-mapper test
🚧 ✅ stress: stress-ng
Host 2:
✅ Boot test
✅ ACPI table test
✅ LTP
✅ CIFS Connectathon
✅ Loopdev Sanity
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
✅ Ethernet drivers sanity
Test sources: https://gitlab.com/cki-project/kernel-tests
💚 Pull requests are welcome for new tests or improvements to existing tests!
Aborted tests
-------------
Tests that didn't complete running successfully are marked with ⚡⚡⚡.
If this was caused by an infrastructure issue, we try to mark that
explicitly in the report.
Waived tests
------------
If the test run included waived tests, they are marked with 🚧. Such tests are
executed but their results are not taken into account. Tests are waived when
their results are not reliable enough, e.g. when they're just introduced or are
being fixed.
Testing timeout
---------------
We aim to provide a report within reasonable timeframe. Tests that haven't
finished running yet are marked with ⏱.
3 years, 1 month