[OS-BUILD PATCH] New configs in drivers/misc
by GitLab Bridge on behalf of jeremycline
From: Jeremy Cline <jcline(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_UACCE:
UACCE provides interface for the user process to access the hardware
without interaction with the kernel space in data path.
The user-space interface is described in
include/uapi/misc/uacce/uacce.h
See Documentation/misc-devices/uacce.rst for more details.
If you don't know what to do here, say N.
Symbol: UACCE [=n]
Type : tristate
Defined at drivers/misc/uacce/Kconfig:1
Prompt: Accelerator Framework for User Land
Depends on: IOMMU_API [=y]
Location:
-> Device Drivers
-> Misc devices
Cc: John Linville <linville(a)redhat.com>
---
redhat/configs/common/generic/CONFIG_UACCE | 1 +
.../pending-common/generic/CONFIG_UACCE | 24 -------------------
2 files changed, 1 insertion(+), 24 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_UACCE
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_UACCE
diff --git a/redhat/configs/common/generic/CONFIG_UACCE b/redhat/configs/common/generic/CONFIG_UACCE
new file mode 100644
index 000000000000..74eddb03cc56
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_UACCE
@@ -0,0 +1 @@
+# CONFIG_UACCE is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_UACCE b/redhat/configs/pending-common/generic/CONFIG_UACCE
deleted file mode 100644
index c94f26e05a56..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_UACCE
+++ /dev/null
@@ -1,24 +0,0 @@
-# CONFIG_UACCE:
-#
-# UACCE provides interface for the user process to access the hardware
-# without interaction with the kernel space in data path.
-#
-# The user-space interface is described in
-# include/uapi/misc/uacce/uacce.h
-#
-# See Documentation/misc-devices/uacce.rst for more details.
-#
-# If you don't know what to do here, say N.
-#
-# Symbol: UACCE [=n]
-# Type : tristate
-# Defined at drivers/misc/uacce/Kconfig:1
-# Prompt: Accelerator Framework for User Land
-# Depends on: IOMMU_API [=y]
-# Location:
-# -> Device Drivers
-# -> Misc devices
-#
-#
-#
-# CONFIG_UACCE is not set
--
GitLab
3 years, 6 months
[OS-BUILD PATCH] [redhat] New configs in drivers/net/wireless
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_MT7663U:
This adds support for MT7663U 802.11ax 2x2:2 wireless devices.
To compile this driver as a module, choose M here.
Symbol: MT7663U [=n]
Type : tristate
Defined at drivers/net/wireless/mediatek/mt76/mt7615/Kconfig:31
Prompt: MediaTek MT7663U (USB) support
Depends on: NETDEVICES [=y] && WLAN [=y] && WLAN_VENDOR_MEDIATEK [=y] && MAC80211 [=m] && USB [=y]
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> Wireless LAN (WLAN [=y])
-> MediaTek devices (WLAN_VENDOR_MEDIATEK [=y])
Selects: MT76_USB [=m] && MT7615_COMMON [=n]
---
CONFIG_MT7915E:
This adds support for MT7915-based wireless PCIe devices,
which support concurrent dual-band operation at both 5GHz
and 2.4GHz IEEE 802.11ax 4x4:4SS 1024-QAM, 160MHz channels,
OFDMA, spatial reuse and dual carrier modulation.
To compile this driver as a module, choose M here.
Symbol: MT7915E [=n]
Type : tristate
Defined at drivers/net/wireless/mediatek/mt76/mt7915/Kconfig:2
Prompt: MediaTek MT7915E (PCIe) support
Depends on: NETDEVICES [=y] && WLAN [=y] && WLAN_VENDOR_MEDIATEK [=y] && MAC80211 [=m] && PCI [=y]
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> Wireless LAN (WLAN [=y])
-> MediaTek devices (WLAN_VENDOR_MEDIATEK [=y])
Selects: MT76_CORE [=m]
---
CONFIG_RTW88_8723DE:
Select this option will enable support for 8723DE chipset
802.11n PCIe wireless network adapter
Symbol: RTW88_8723DE [=n]
Type : tristate
Defined at drivers/net/wireless/realtek/rtw88/Kconfig:50
Prompt: Realtek 8723DE PCI wireless network adapter
Depends on: NETDEVICES [=y] && WLAN [=y] && WLAN_VENDOR_REALTEK [=y] && RTW88 [=m] && PCI [=y]
Location:
-> Device Drivers
-> Network device support (NETDEVICES [=y])
-> Wireless LAN (WLAN [=y])
-> Realtek devices (WLAN_VENDOR_REALTEK [=y])
-> Realtek 802.11ac wireless chips support (RTW88 [=m])
Selects: RTW88_CORE [=m] && RTW88_PCI [=m] && RTW88_8723D [=n]
---
Signed-off-by: Justin M. Forbes <jforbes(a)fedoraproject.org>
---
redhat/configs/common/generic/CONFIG_MT7663U | 1 +
redhat/configs/common/generic/CONFIG_MT7915E | 1 +
.../common/generic/CONFIG_RTW88_8723DE | 1 +
.../pending-common/generic/CONFIG_MT7663U | 21 ----------------
.../pending-common/generic/CONFIG_MT7915E | 24 -------------------
.../generic/CONFIG_RTW88_8723DE | 22 -----------------
6 files changed, 3 insertions(+), 67 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_MT7663U
create mode 100644 redhat/configs/common/generic/CONFIG_MT7915E
create mode 100644 redhat/configs/common/generic/CONFIG_RTW88_8723DE
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_MT7663U
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_MT7915E
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_RTW88_8723DE
diff --git a/redhat/configs/common/generic/CONFIG_MT7663U b/redhat/configs/common/generic/CONFIG_MT7663U
new file mode 100644
index 000000000000..c4efff0c4a21
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_MT7663U
@@ -0,0 +1 @@
+# CONFIG_MT7663U is not set
diff --git a/redhat/configs/common/generic/CONFIG_MT7915E b/redhat/configs/common/generic/CONFIG_MT7915E
new file mode 100644
index 000000000000..3ad870e9f43b
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_MT7915E
@@ -0,0 +1 @@
+# CONFIG_MT7915E is not set
diff --git a/redhat/configs/common/generic/CONFIG_RTW88_8723DE b/redhat/configs/common/generic/CONFIG_RTW88_8723DE
new file mode 100644
index 000000000000..78ccc3dc8d89
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_RTW88_8723DE
@@ -0,0 +1 @@
+# CONFIG_RTW88_8723DE is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_MT7663U b/redhat/configs/pending-common/generic/CONFIG_MT7663U
deleted file mode 100644
index 476cbde00f23..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_MT7663U
+++ /dev/null
@@ -1,21 +0,0 @@
-# CONFIG_MT7663U:
-#
-# This adds support for MT7663U 802.11ax 2x2:2 wireless devices.
-#
-# To compile this driver as a module, choose M here.
-#
-# Symbol: MT7663U [=n]
-# Type : tristate
-# Defined at drivers/net/wireless/mediatek/mt76/mt7615/Kconfig:31
-# Prompt: MediaTek MT7663U (USB) support
-# Depends on: NETDEVICES [=y] && WLAN [=y] && WLAN_VENDOR_MEDIATEK [=y] && MAC80211 [=m] && USB [=y]
-# Location:
-# -> Device Drivers
-# -> Network device support (NETDEVICES [=y])
-# -> Wireless LAN (WLAN [=y])
-# -> MediaTek devices (WLAN_VENDOR_MEDIATEK [=y])
-# Selects: MT76_USB [=m] && MT7615_COMMON [=n]
-#
-#
-#
-# CONFIG_MT7663U is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_MT7915E b/redhat/configs/pending-common/generic/CONFIG_MT7915E
deleted file mode 100644
index 3caf2fc5ee12..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_MT7915E
+++ /dev/null
@@ -1,24 +0,0 @@
-# CONFIG_MT7915E:
-#
-# This adds support for MT7915-based wireless PCIe devices,
-# which support concurrent dual-band operation at both 5GHz
-# and 2.4GHz IEEE 802.11ax 4x4:4SS 1024-QAM, 160MHz channels,
-# OFDMA, spatial reuse and dual carrier modulation.
-#
-# To compile this driver as a module, choose M here.
-#
-# Symbol: MT7915E [=n]
-# Type : tristate
-# Defined at drivers/net/wireless/mediatek/mt76/mt7915/Kconfig:2
-# Prompt: MediaTek MT7915E (PCIe) support
-# Depends on: NETDEVICES [=y] && WLAN [=y] && WLAN_VENDOR_MEDIATEK [=y] && MAC80211 [=m] && PCI [=y]
-# Location:
-# -> Device Drivers
-# -> Network device support (NETDEVICES [=y])
-# -> Wireless LAN (WLAN [=y])
-# -> MediaTek devices (WLAN_VENDOR_MEDIATEK [=y])
-# Selects: MT76_CORE [=m]
-#
-#
-#
-# CONFIG_MT7915E is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_RTW88_8723DE b/redhat/configs/pending-common/generic/CONFIG_RTW88_8723DE
deleted file mode 100644
index 40cda55d25d7..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_RTW88_8723DE
+++ /dev/null
@@ -1,22 +0,0 @@
-# CONFIG_RTW88_8723DE:
-#
-# Select this option will enable support for 8723DE chipset
-#
-# 802.11n PCIe wireless network adapter
-#
-# Symbol: RTW88_8723DE [=n]
-# Type : tristate
-# Defined at drivers/net/wireless/realtek/rtw88/Kconfig:50
-# Prompt: Realtek 8723DE PCI wireless network adapter
-# Depends on: NETDEVICES [=y] && WLAN [=y] && WLAN_VENDOR_REALTEK [=y] && RTW88 [=m] && PCI [=y]
-# Location:
-# -> Device Drivers
-# -> Network device support (NETDEVICES [=y])
-# -> Wireless LAN (WLAN [=y])
-# -> Realtek devices (WLAN_VENDOR_REALTEK [=y])
-# -> Realtek 802.11ac wireless chips support (RTW88 [=m])
-# Selects: RTW88_CORE [=m] && RTW88_PCI [=m] && RTW88_8723D [=n]
-#
-#
-#
-# CONFIG_RTW88_8723DE is not set
--
2.26.2
3 years, 6 months
[OS-BUILD PATCH] [redhat] New configs in drivers/phy
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_PHY_QCOM_IPQ806X_USB:
This option enables support for the Synopsis PHYs present inside the
Qualcomm USB3.0 DWC3 controller on ipq806x SoC. This driver supports
both HS and SS PHY controllers.
Symbol: PHY_QCOM_IPQ806X_USB [=n]
Type : tristate
Defined at drivers/phy/qualcomm/Kconfig:108
Prompt: Qualcomm IPQ806x DWC3 USB PHY driver
Depends on: HAS_IOMEM [=y] && OF [=y] && (ARCH_QCOM [=y] || COMPILE_TEST [=n])
Location:
-> Device Drivers
-> PHY Subsystem
Selects: GENERIC_PHY [=y]
---
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../generic/CONFIG_PHY_QCOM_IPQ806X_USB | 1 +
.../generic/CONFIG_PHY_QCOM_IPQ806X_USB | 19 -------------------
2 files changed, 1 insertion(+), 19 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_PHY_QCOM_IPQ806X_USB
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_PHY_QCOM_IPQ806X_USB
diff --git a/redhat/configs/common/generic/CONFIG_PHY_QCOM_IPQ806X_USB b/redhat/configs/common/generic/CONFIG_PHY_QCOM_IPQ806X_USB
new file mode 100644
index 000000000000..de880c0fb3a6
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_PHY_QCOM_IPQ806X_USB
@@ -0,0 +1 @@
+# CONFIG_PHY_QCOM_IPQ806X_USB is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_PHY_QCOM_IPQ806X_USB b/redhat/configs/pending-common/generic/CONFIG_PHY_QCOM_IPQ806X_USB
deleted file mode 100644
index b71da31e30e5..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_PHY_QCOM_IPQ806X_USB
+++ /dev/null
@@ -1,19 +0,0 @@
-# CONFIG_PHY_QCOM_IPQ806X_USB:
-#
-# This option enables support for the Synopsis PHYs present inside the
-# Qualcomm USB3.0 DWC3 controller on ipq806x SoC. This driver supports
-# both HS and SS PHY controllers.
-#
-# Symbol: PHY_QCOM_IPQ806X_USB [=n]
-# Type : tristate
-# Defined at drivers/phy/qualcomm/Kconfig:108
-# Prompt: Qualcomm IPQ806x DWC3 USB PHY driver
-# Depends on: HAS_IOMEM [=y] && OF [=y] && (ARCH_QCOM [=y] || COMPILE_TEST [=n])
-# Location:
-# -> Device Drivers
-# -> PHY Subsystem
-# Selects: GENERIC_PHY [=y]
-#
-#
-#
-# CONFIG_PHY_QCOM_IPQ806X_USB is not set
--
GitLab
3 years, 6 months
[OS-BUILD PATCH] [redhat] New configs in drivers/tty
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_SERIAL_LANTIQ:
Support for UART on Lantiq and Intel SoCs.
To compile this driver as a module, select M here. The
module will be called lantiq.
Symbol: SERIAL_LANTIQ [=n]
Type : tristate
Defined at drivers/tty/serial/Kconfig:1036
Prompt: Lantiq serial driver
Depends on: TTY [=y] && HAS_IOMEM [=y] && (LANTIQ || X86 [=y] || COMPILE_TEST [=n])
Location:
-> Device Drivers
-> Character devices
-> Enable TTY (TTY [=y])
-> Serial drivers
Selects: SERIAL_CORE [=y]
---
Signed-off-by: Fedora Kernel Team <kernel-team(a)fedoraproject.org>
---
.../common/generic/CONFIG_SERIAL_LANTIQ | 1 +
.../generic/CONFIG_SERIAL_LANTIQ | 21 -------------------
2 files changed, 1 insertion(+), 21 deletions(-)
create mode 100644 redhat/configs/common/generic/CONFIG_SERIAL_LANTIQ
delete mode 100644 redhat/configs/pending-common/generic/CONFIG_SERIAL_LANTIQ
diff --git a/redhat/configs/common/generic/CONFIG_SERIAL_LANTIQ b/redhat/configs/common/generic/CONFIG_SERIAL_LANTIQ
new file mode 100644
index 000000000000..7bd602b2fd91
--- /dev/null
+++ b/redhat/configs/common/generic/CONFIG_SERIAL_LANTIQ
@@ -0,0 +1 @@
+# CONFIG_SERIAL_LANTIQ is not set
diff --git a/redhat/configs/pending-common/generic/CONFIG_SERIAL_LANTIQ b/redhat/configs/pending-common/generic/CONFIG_SERIAL_LANTIQ
deleted file mode 100644
index 5fc2caf1f9ee..000000000000
--- a/redhat/configs/pending-common/generic/CONFIG_SERIAL_LANTIQ
+++ /dev/null
@@ -1,21 +0,0 @@
-# CONFIG_SERIAL_LANTIQ:
-#
-# Support for UART on Lantiq and Intel SoCs.
-# To compile this driver as a module, select M here. The
-# module will be called lantiq.
-#
-# Symbol: SERIAL_LANTIQ [=n]
-# Type : tristate
-# Defined at drivers/tty/serial/Kconfig:1036
-# Prompt: Lantiq serial driver
-# Depends on: TTY [=y] && HAS_IOMEM [=y] && (LANTIQ || X86 [=y] || COMPILE_TEST [=n])
-# Location:
-# -> Device Drivers
-# -> Character devices
-# -> Enable TTY (TTY [=y])
-# -> Serial drivers
-# Selects: SERIAL_CORE [=y]
-#
-#
-#
-# CONFIG_SERIAL_LANTIQ is not set
--
2.26.2
3 years, 6 months
[OS-BUILD PATCH] Combine Red Hat patches into single patch
by GitLab Bridge on behalf of dzickusrh
From: Don Zickus <dzickus(a)redhat.com>
This in spirit reverts 0409b218390b564c44dd0181c5d0fe177d4c6bc3
and converts the broken out Red Hat patches back into a single diff.
The original idea was to make it easy for the Fedora community to see
what changes Red Hat was making on top of upstream's tarball. The
concept was good, the reality with a source git tree had a flaw.
While 'git merging' with upstream, various conflicts were resolved
through git or the merge. However, when broken out into individual
patches and placed on top of a tarball, this becomes a rebase.
The conflicts could not be resolved with later patches as the initial
patch was a problem. The only solution was to periodically rebase
the source git tree which dampens the spirit of the idea of source-git.
This patch takes another apporach to solve the original problem:
- create a diff from upstream as a single patch
- create a Patchlist.changelog file to list the individual patches
and their shas1 as seen in the source git tree.
This is what was there original and hence the partial revert (though
that patch went through many changes since then).
It isn't perfect, but we are still evolving. This should resolve the
CKI build failures they continuously run into.
Signed-off-by: Don Zickus <dzickus(a)redhat.com>
---
redhat/genspec.sh | 47 ++++++++++++++-----------------------
redhat/kernel.spec.template | 5 ++--
2 files changed, 20 insertions(+), 32 deletions(-)
diff --git a/redhat/genspec.sh b/redhat/genspec.sh
index a2bfa07a5ef6..966fe85f132f 100755
--- a/redhat/genspec.sh
+++ b/redhat/genspec.sh
@@ -28,9 +28,6 @@ clogf="$SOURCES/changelog"
HIDE_REDHAT=1;
# hide entries for unsupported arches
HIDE_UNSUPPORTED_ARCH=1;
-# Set up for broken out patches
-plistf="$SOURCES/Patchlist"
-pnum=2
# override LC_TIME to avoid date conflicts when building the srpm
LC_TIME=
STAMP=$(echo $MARKER | cut -f 1 -d '-' | sed -e "s/v//");
@@ -252,37 +249,29 @@ test -n "$SPECFILE" &&
s/%%DEBUG_BUILDS_ENABLED%%/$DEBUG_BUILDS_ENABLED/
s/%%TARBALL_VERSION%%/$TARFILE_RELEASE/" $SPECFILE
-touch $plistf
+echo "MARKER is $MARKER"
+
+EXCLUDE_FILES=":(exclude,top).get_maintainer.conf \
+ :(exclude,top).gitattributes \
+ :(exclude,top).gitignore \
+ :(exclude,top).gitlab-ci.yml \
+ :(exclude,top)makefile \
+ :(exclude,top)Makefile.rhelver \
+ :(exclude,top)redhat \
+ :(exclude,top)configs"
+
if [ "$SINGLE_TARBALL" = 0 ]; then
- truncate -s 0 $plistf
- COMMITS=$(git log --reverse --pretty=format:"%h" --no-merges "$MARKER".. \
- ":(exclude,top).get_maintainer.conf" \
- ":(exclude,top).gitattributes" \
- ":(exclude,top).gitignore" \
- ":(exclude,top).gitlab-ci.yml" \
- ":(exclude,top)makefile" \
- ":(exclude,top)Makefile.rhelver" \
- ":(exclude,top)redhat")
- for c in $COMMITS; do
- patch=$(git format-patch --zero-commit -1 "$c")
- echo "$patch" >> $plistf
- mv $patch $SOURCES/
- sed -i "s/%%PATCHLIST%%/Patch$pnum: $patch\n%%PATCHLIST%%/" $SPECFILE
- sed -i "s/%%APPLYPATCH%%/ApplyOptionalPatch $patch\n%%APPLYPATCH%%/" $SPECFILE
- ((pnum++))
- done
+ git diff -p --no-renames --stat $MARKER.. $EXCLUDE_FILES \
+ > $SOURCES/patch-${RPMVERSION}-redhat.patch
+else
+ # Need an empty file for dist-git compatibility
+ touch $SOURCES/patch-${RPMVERSION}-redhat.patch
fi
# generate Patchlist.changelog file that holds the shas and commits not
# included upstream.
-git log --no-merges --pretty=oneline --no-decorate master.. \
- ":(exclude,top).gitlab-ci.yml" \
- ":(exclude,top)makefile" \
- ":(exclude,top)Makefile.rhelver" \
- ":(exclude,top)redhat" > $plistf.changelog
-
-sed -i "s/%%PATCHLIST%%//" $SPECFILE
-sed -i "s/%%APPLYPATCH%%//" $SPECFILE
+git log --no-merges --pretty=oneline --no-decorate master.. $EXCLUDE_FILES \
+ > $SOURCES/Patchlist.changelog
for opt in $BUILDOPTS; do
add_opt=
diff --git a/redhat/kernel.spec.template b/redhat/kernel.spec.template
index bc12211a7d6b..7cbfb9c139eb 100644
--- a/redhat/kernel.spec.template
+++ b/redhat/kernel.spec.template
@@ -707,7 +707,6 @@ Source2001: cpupower.config
# source tree, but in the mean time we carry this to support the legacy workflow
Source3000: merge.pl
Source3001: kernel-local
-Source3002: Patchlist
Source3003: Patchlist.changelog
Source4000: README.rst
@@ -716,7 +715,7 @@ Source4000: README.rst
%if !%{nopatches}
-%%PATCHLIST%%
+Patch1: patch-%{rpmversion}-redhat.patch
%endif
# empty final patch to facilitate testing of kernel patches
@@ -1219,7 +1218,7 @@ cp -a %{SOURCE1} .
%if !%{nopatches}
-%%APPLYPATCH%%
+ApplyOptionalPatch patch-%{rpmversion}-redhat.patch
%endif
ApplyOptionalPatch linux-kernel-test.patch
--
GitLab
3 years, 6 months
❌ FAIL: Test report for kernel 5.9.0-0.rc8.29.cki.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: 2d2419754dac - [redhat] kernel-5.9.0-0.rc8.28
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:
ppc64le: FAILED (see build-ppc64le.log.xz attachment)
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
3 years, 6 months
❌ FAIL: Test report for kernel 5.9.0-0.rc8.28.cki.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: b327ac0982ee - [redhat] kernel-5.9.0-0.rc8.27
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:
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=kabidw_base --without=debug
3 years, 6 months
❌ FAIL: Test report for kernel 5.9.0-0.rc7.27.cki.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: e7e671aa06d3 - [redhat] kernel-5.9.0-0.rc7.20201005git22fbc037cd32.26
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:
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=kabidw_base --without=debug
3 years, 6 months
❌ FAIL: Test report for kernel 5.9.0-0.rc7.26.cki.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: ad33dcdc7128 - [redhat] kernel-5.9.0-0.rc7.20201004gitd3d45f8220d6.25
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:
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=kabidw_base --without=debug
3 years, 6 months
❌ FAIL: Test report for kernel 5.9.0-0.rc7.25.cki.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: a991f4f70984 - [redhat] kernel-5.9.0-0.rc7.20201003git472e5b056f00.24
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:
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=kabidw_base --without=debug
3 years, 6 months