The kernel-ark os-build branch has been rebased.
by Justin Forbes
As we did with 5.15, we have done this again for os-build, we expect
to keep it up as a cadence with every upstream release. This means we
will do it again when 5.17 releases, and again with 5.18... It is
difficult to manage a regularly rebased tree, because any outstanding
MR is invalidated and has to also be rebased. But not doing somewhat
regular rebases can also be difficult in the spirit of the openness
that Fedora is based upon. While there are plenty of ways to see
which patches we carry compared to upstream, some of those patches are
fairly old, and would not apply cleanly at all to a modern tree after
several releases were merged in with them. As we have gotten into a
flow of things with merge requests, we can get to the point of very
few outstanding MRs towards the end of a release cycle, and that makes
it an opportune time to rebase the tree. This also means that the
patches we carry should be no more than 1 release out of date, making
them easier to apply to various other trees. I do realize that this
is a minor inconvenience every 2-3 months, but I believe the results
are worth it.
Thanks,
Justin
2 years, 3 months
[OS-BUILD PATCH] move CONFIG_STRICT_SIGALTSTACK_SIZE to the
appropriate
directory
by David Arcari (via Email Bridge)
From: David Arcari <darcari(a)redhat.com>
move CONFIG_STRICT_SIGALTSTACK_SIZE to the appropriate directory
STRICT_SIGALTSTACK_SIZE is only present in arch/x86
Signed-off-by: David Arcari <darcari(a)redhat.com>
diff --git a/redhat/configs/common/generic/CONFIG_STRICT_SIGALTSTACK_SIZE b/redhat/configs/common/generic/x86/x86_64/CONFIG_STRICT_SIGALTSTACK_SIZE
rename from redhat/configs/common/generic/CONFIG_STRICT_SIGALTSTACK_SIZE
rename to redhat/configs/common/generic/x86/x86_64/CONFIG_STRICT_SIGALTSTACK_SIZE
index blahblah..blahblah 100644
--- a/redhat/configs/common/generic/CONFIG_STRICT_SIGALTSTACK_SIZE
+++ b/redhat/configs/common/generic/x86/x86_64/CONFIG_STRICT_SIGALTSTACK_SIZE
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1507
2 years, 3 months
[OS-BUILD PATCHv2] redhat: switch the vsyscall config to
CONFIG_LEGACY_VSYSCALL_XONLY=y
by Herton R. Krzesinski (via Email Bridge)
From: Herton R. Krzesinski <herton(a)redhat.com>
redhat: switch the vsyscall config to CONFIG_LEGACY_VSYSCALL_XONLY=y
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1876977
As discussed upstream eg. at https://lore.kernel.org/linux-api/87h7bzjaer.fsf@oldenburg.str.redhat.com/T/
and pointed on the bug's description above, VSYSCALL_XONLY is more
secure while still maintaining useful backward compatibility.
We also plan to do this change on the RHEL side with a centos-stream-9
change, so the change here covers both Fedora and RHEL/CentOS.
v2: move the CONFIG_LEGACY_VSYSCALL* files to the x86 directory, as they
are x86 only settings, as reported/suggested by Waiman Long.
Signed-off-by: Herton R. Krzesinski <herton(a)redhat.com>
diff --git a/redhat/configs/common/generic/CONFIG_LEGACY_VSYSCALL_EMULATE b/redhat/configs/common/generic/CONFIG_LEGACY_VSYSCALL_EMULATE
deleted file mode 100644
index blahblah..blahblah 0
--- a/redhat/configs/common/generic/CONFIG_LEGACY_VSYSCALL_EMULATE
+++ /dev/null
@@ -1 +0,0 @@
-CONFIG_LEGACY_VSYSCALL_EMULATE=y
diff --git a/redhat/configs/common/generic/CONFIG_LEGACY_VSYSCALL_XONLY b/redhat/configs/common/generic/CONFIG_LEGACY_VSYSCALL_XONLY
deleted file mode 100644
index blahblah..blahblah 0
--- a/redhat/configs/common/generic/CONFIG_LEGACY_VSYSCALL_XONLY
+++ /dev/null
@@ -1 +0,0 @@
-# CONFIG_LEGACY_VSYSCALL_XONLY is not set
diff --git a/redhat/configs/common/generic/x86/CONFIG_LEGACY_VSYSCALL_EMULATE b/redhat/configs/common/generic/x86/CONFIG_LEGACY_VSYSCALL_EMULATE
new file mode 100644
index blahblah..blahblah 100644
--- /dev/null
+++ b/redhat/configs/common/generic/x86/CONFIG_LEGACY_VSYSCALL_EMULATE
@@ -0,0 +1 @@
+# CONFIG_LEGACY_VSYSCALL_EMULATE is not set
diff --git a/redhat/configs/common/generic/CONFIG_LEGACY_VSYSCALL_NONE b/redhat/configs/common/generic/x86/CONFIG_LEGACY_VSYSCALL_NONE
rename from redhat/configs/common/generic/CONFIG_LEGACY_VSYSCALL_NONE
rename to redhat/configs/common/generic/x86/CONFIG_LEGACY_VSYSCALL_NONE
index blahblah..blahblah 100644
--- a/redhat/configs/common/generic/CONFIG_LEGACY_VSYSCALL_NONE
+++ b/redhat/configs/common/generic/x86/CONFIG_LEGACY_VSYSCALL_NONE
diff --git a/redhat/configs/common/generic/x86/CONFIG_LEGACY_VSYSCALL_XONLY b/redhat/configs/common/generic/x86/CONFIG_LEGACY_VSYSCALL_XONLY
new file mode 100644
index blahblah..blahblah 100644
--- /dev/null
+++ b/redhat/configs/common/generic/x86/CONFIG_LEGACY_VSYSCALL_XONLY
@@ -0,0 +1 @@
+CONFIG_LEGACY_VSYSCALL_XONLY=y
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1531
2 years, 3 months
[OS-BUILD PATCHv2] Enable iSER on s390x
by Stefan Schulze Frielinghaus (via Email Bridge)
From: Stefan Schulze Frielinghaus <sfrielin(a)redhat.com>
Enable iSER on s390x
Brew: http://brewweb.engineering.redhat.com/brew/taskinfo?taskID=41520597
Tested: by IBM
Upstream Status: RHEL only
Signed-off-by: Stefan Schulze Frielinghaus <sfrielin(a)redhat.com>
diff --git a/redhat/configs/ark/generic/s390x/CONFIG_INFINIBAND_ISER b/redhat/configs/ark/generic/s390x/CONFIG_INFINIBAND_ISER
index blahblah..blahblah 100644
--- a/redhat/configs/ark/generic/s390x/CONFIG_INFINIBAND_ISER
+++ b/redhat/configs/ark/generic/s390x/CONFIG_INFINIBAND_ISER
@@ -1 +1 @@
-# CONFIG_INFINIBAND_ISER is not set
+CONFIG_INFINIBAND_ISER=m
diff --git a/redhat/configs/ark/generic/s390x/CONFIG_INFINIBAND_ISERT b/redhat/configs/ark/generic/s390x/CONFIG_INFINIBAND_ISERT
index blahblah..blahblah 100644
--- a/redhat/configs/ark/generic/s390x/CONFIG_INFINIBAND_ISERT
+++ b/redhat/configs/ark/generic/s390x/CONFIG_INFINIBAND_ISERT
@@ -1 +1 @@
-# CONFIG_INFINIBAND_ISERT is not set
+CONFIG_INFINIBAND_ISERT=m
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1536
2 years, 3 months
[OS-BUILD PATCH] Enable iSER on s390x
by Stefan Schulze Frielinghaus (via Email Bridge)
From: Stefan Schulze Frielinghaus <sfrielin(a)redhat.com>
Enable iSER on s390x
Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1965279
Brew: http://brewweb.engineering.redhat.com/brew/taskinfo?taskID=41520597
Tested: by IBM
Upstream Status: RHEL only
Signed-off-by: Stefan Schulze Frielinghaus <sfrielin(a)redhat.com>
diff --git a/redhat/configs/ark/generic/s390x/CONFIG_INFINIBAND_ISER b/redhat/configs/ark/generic/s390x/CONFIG_INFINIBAND_ISER
index blahblah..blahblah 100644
--- a/redhat/configs/ark/generic/s390x/CONFIG_INFINIBAND_ISER
+++ b/redhat/configs/ark/generic/s390x/CONFIG_INFINIBAND_ISER
@@ -1 +1 @@
-# CONFIG_INFINIBAND_ISER is not set
+CONFIG_INFINIBAND_ISER=m
diff --git a/redhat/configs/ark/generic/s390x/CONFIG_INFINIBAND_ISERT b/redhat/configs/ark/generic/s390x/CONFIG_INFINIBAND_ISERT
index blahblah..blahblah 100644
--- a/redhat/configs/ark/generic/s390x/CONFIG_INFINIBAND_ISERT
+++ b/redhat/configs/ark/generic/s390x/CONFIG_INFINIBAND_ISERT
@@ -1 +1 @@
-# CONFIG_INFINIBAND_ISERT is not set
+CONFIG_INFINIBAND_ISERT=m
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1536
2 years, 3 months
✅ PASS: Test report for kernel 5.15.13-100.fc34 (fedora-34)
by CKI Project
Hello,
We ran automated tests on the following kernel build:
Kernel package: kernel-5.15.13-100.fc34
Task URL: https://koji.fedoraproject.org/koji/taskinfo?taskID=80874708
The results of these automated tests are provided below.
Overall result: PASSED
Tests: OK
All kernel binaries, config files, and logs are available for download here:
https://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
✅ Reboot test
✅ ACPI table test
✅ LTP - cve
✅ LTP - sched
✅ LTP - syscalls
✅ LTP - can
✅ LTP - commands
✅ LTP - containers
✅ LTP - dio
✅ LTP - fs
✅ LTP - fsx
✅ LTP - math
✅ LTP - hugetlb
✅ LTP - mm
✅ LTP - nptl
✅ LTP - pty
✅ LTP - ipc
✅ LTP - tracing
✅ LTP: openposix test suite
✅ CIFS Connectathon
✅ Loopdev Sanity
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
✅ Ethernet drivers sanity
🚧 ✅ xarray-idr-radixtree-test
🚧 ✅ NFS Connectathon
Host 2:
✅ Boot test
✅ Reboot test
✅ xfstests - ext4
✅ xfstests - xfs
✅ Storage: swraid mdadm raid_module test
🚧 ✅ xfstests - btrfs
🚧 ✅ Storage blktests - blk
🚧 ✅ Storage blktests - nvme-tcp
🚧 ✅ Storage block - filesystem fio test
🚧 ✅ Storage block - queue scheduler test
🚧 ✅ Storage block - storage fio numa
🚧 ✅ storage: software RAID testing
🚧 ✅ stress: stress-ng - interrupt
🚧 ✅ stress: stress-ng - cpu
🚧 ✅ stress: stress-ng - cpu-cache
🚧 ✅ stress: stress-ng - memory
🚧 ✅ stress: stress-ng - os
Host 3:
✅ Boot test
✅ Reboot test
🚧 ❌ Storage blktests - nvmeof-mp
Host 4:
✅ Boot test
✅ Reboot test
🚧 ✅ Storage blktests - srp
Host 5:
⚡ Internal infrastructure issues prevented one or more tests (marked
with ⚡⚡⚡) from running on this architecture.
This is not the fault of the kernel that was tested.
⚡⚡⚡ Boot test
⚡⚡⚡ Reboot test
⚡⚡⚡ Ethernet drivers sanity - mlx5
Host 6:
✅ Boot test
✅ Reboot test
✅ Ethernet drivers sanity - mlx5
ppc64le:
Host 1:
✅ Boot test
✅ Reboot test
✅ LTP - cve
✅ LTP - sched
✅ LTP - syscalls
✅ LTP - can
✅ LTP - commands
✅ LTP - containers
✅ LTP - dio
✅ LTP - fs
✅ LTP - fsx
✅ LTP - math
✅ LTP - hugetlb
✅ LTP - mm
✅ LTP - nptl
✅ LTP - pty
✅ LTP - ipc
✅ LTP - tracing
✅ LTP: openposix test suite
✅ CIFS Connectathon
✅ Loopdev Sanity
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
✅ Ethernet drivers sanity
🚧 ✅ xarray-idr-radixtree-test
🚧 ✅ NFS Connectathon
Host 2:
✅ Boot test
✅ Reboot test
🚧 ❌ Storage blktests - nvmeof-mp
Host 3:
✅ Boot test
✅ Reboot test
✅ xfstests - ext4
✅ xfstests - xfs
✅ Storage: swraid mdadm raid_module test
🚧 ✅ xfstests - btrfs
🚧 ✅ Storage blktests - blk
🚧 ✅ Storage blktests - nvme-tcp
🚧 ✅ Storage block - filesystem fio test
🚧 ✅ Storage block - queue scheduler test
🚧 ❌ Storage block - storage fio numa
🚧 ✅ Storage: lvm device-mapper test - upstream
🚧 ✅ storage: software RAID testing
Host 4:
✅ Boot test
✅ Reboot test
🚧 ❌ Storage blktests - srp
s390x:
Host 1:
✅ Boot test
✅ Reboot test
✅ Storage: swraid mdadm raid_module test
🚧 ✅ Storage blktests - blk
🚧 ✅ Storage blktests - nvme-tcp
🚧 ✅ stress: stress-ng - interrupt
🚧 ✅ stress: stress-ng - cpu
🚧 ✅ stress: stress-ng - cpu-cache
🚧 ✅ stress: stress-ng - memory
🚧 ✅ stress: stress-ng - os
Host 2:
✅ Boot test
✅ Reboot test
✅ LTP - cve
✅ LTP - sched
✅ LTP - syscalls
✅ LTP - can
✅ LTP - commands
✅ LTP - containers
✅ LTP - dio
✅ LTP - fs
✅ LTP - fsx
✅ LTP - math
✅ LTP - hugetlb
✅ LTP - mm
✅ LTP - nptl
✅ LTP - pty
✅ LTP - ipc
✅ LTP - tracing
✅ LTP: openposix test suite
✅ CIFS Connectathon
✅ Loopdev Sanity
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
✅ Ethernet drivers sanity
🚧 ❌ xarray-idr-radixtree-test
🚧 ✅ NFS Connectathon
Host 3:
✅ Boot test
✅ Reboot test
🚧 ✅ Storage blktests - srp
Host 4:
✅ Boot test
✅ Reboot test
🚧 ❌ Storage blktests - nvmeof-mp
x86_64:
Host 1:
⚡ Internal infrastructure issues prevented one or more tests (marked
with ⚡⚡⚡) from running on this architecture.
This is not the fault of the kernel that was tested.
⚡⚡⚡ Boot test
⚡⚡⚡ Reboot test
⚡⚡⚡ xfstests - ext4
⚡⚡⚡ xfstests - xfs
⚡⚡⚡ xfstests - nfsv4.2
⚡⚡⚡ Storage: swraid mdadm raid_module test
🚧 ⚡⚡⚡ xfstests - btrfs
🚧 ⚡⚡⚡ xfstests - cifsv3.11
🚧 ⚡⚡⚡ Storage blktests - blk
🚧 ⚡⚡⚡ Storage blktests - nvme-tcp
🚧 ⚡⚡⚡ Storage block - filesystem fio test
🚧 ⚡⚡⚡ Storage block - queue scheduler test
🚧 ⚡⚡⚡ Storage block - storage fio numa
🚧 ⚡⚡⚡ Storage: lvm device-mapper test - upstream
🚧 ⚡⚡⚡ storage: software RAID testing
🚧 ⚡⚡⚡ stress: stress-ng - interrupt
🚧 ⚡⚡⚡ stress: stress-ng - cpu
🚧 ⚡⚡⚡ stress: stress-ng - cpu-cache
🚧 ⚡⚡⚡ stress: stress-ng - memory
🚧 ⚡⚡⚡ stress: stress-ng - os
Host 2:
✅ Boot test
✅ Reboot test
🚧 💥 Storage blktests - srp
Host 3:
⚡ Internal infrastructure issues prevented one or more tests (marked
with ⚡⚡⚡) from running on this architecture.
This is not the fault of the kernel that was tested.
⚡⚡⚡ Boot test
⚡⚡⚡ Reboot test
⚡⚡⚡ ACPI table test
⚡⚡⚡ LTP - cve
⚡⚡⚡ LTP - sched
⚡⚡⚡ LTP - syscalls
⚡⚡⚡ LTP - can
⚡⚡⚡ LTP - commands
⚡⚡⚡ LTP - containers
⚡⚡⚡ LTP - dio
⚡⚡⚡ LTP - fs
⚡⚡⚡ LTP - fsx
⚡⚡⚡ LTP - math
⚡⚡⚡ LTP - hugetlb
⚡⚡⚡ LTP - mm
⚡⚡⚡ LTP - nptl
⚡⚡⚡ LTP - pty
⚡⚡⚡ LTP - ipc
⚡⚡⚡ LTP - tracing
⚡⚡⚡ LTP: openposix test suite
⚡⚡⚡ CIFS Connectathon
⚡⚡⚡ Loopdev Sanity
⚡⚡⚡ Memory: fork_mem
⚡⚡⚡ Memory function: memfd_create
⚡⚡⚡ AMTU (Abstract Machine Test Utility)
⚡⚡⚡ Ethernet drivers sanity
🚧 ⚡⚡⚡ xarray-idr-radixtree-test
🚧 ⚡⚡⚡ NFS Connectathon
Host 4:
✅ Boot test
✅ Reboot test
🚧 ❌ Storage blktests - nvmeof-mp
Host 5:
✅ Boot test
✅ Reboot test
✅ xfstests - ext4
✅ xfstests - xfs
✅ xfstests - nfsv4.2
✅ Storage: swraid mdadm raid_module test
🚧 ✅ xfstests - btrfs
🚧 ✅ xfstests - cifsv3.11
🚧 ✅ Storage blktests - blk
🚧 ✅ Storage blktests - nvme-tcp
🚧 ✅ Storage block - filesystem fio test
🚧 ✅ Storage block - queue scheduler test
🚧 ❌ Storage block - storage fio numa
🚧 ✅ Storage: lvm device-mapper test - upstream
🚧 ✅ storage: software RAID testing
🚧 ✅ stress: stress-ng - interrupt
🚧 ✅ stress: stress-ng - cpu
🚧 ✅ stress: stress-ng - cpu-cache
🚧 ✅ stress: stress-ng - memory
🚧 ❌ stress: stress-ng - os
Host 6:
✅ Boot test
✅ Reboot test
✅ ACPI table test
✅ LTP - cve
✅ LTP - sched
✅ LTP - syscalls
✅ LTP - can
✅ LTP - commands
✅ LTP - containers
✅ LTP - dio
✅ LTP - fs
✅ LTP - fsx
✅ LTP - math
✅ LTP - hugetlb
✅ LTP - mm
✅ LTP - nptl
✅ LTP - pty
✅ LTP - ipc
✅ LTP - tracing
✅ LTP: openposix test suite
✅ CIFS Connectathon
✅ Loopdev Sanity
✅ Memory: fork_mem
✅ Memory function: memfd_create
✅ AMTU (Abstract Machine Test Utility)
✅ Ethernet drivers sanity
🚧 ❌ xarray-idr-radixtree-test
🚧 ✅ NFS Connectathon
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 ⏱.
2 years, 3 months
[OS-BUILD PATCHv2] Turn CONFIG_DEVMEM back off for aarch64
by Justin M. Forbes (via Email Bridge)
From: Justin M. Forbes <jforbes(a)fedoraproject.org>
Turn CONFIG_DEVMEM back off for aarch64
We have ended up with a config mismatch for the RHEL configs in a way
that was unclear and untracked. CONFIG_STRICT_DEVMEM is enabled in
configs/common/generic, but CONFIG_DEVMEM was disabled for aarch64 in
RHEL (though not in Fedora). This creates a mismatch situation where the
configs do not get generated in the way they are set. Our options are
to either turn off CONFIG_STRICT_DEVMEM as I have here, or turn on
CONFIG_DEVMEM for aarch64. I went with the former after discussion in
the MR.
Signed-off-by: Justin M. Forbes <jforbes(a)fedoraproject.org>
diff --git a/redhat/configs/ark/generic/arm/aarch64/CONFIG_STRICT_DEVMEM b/redhat/configs/ark/generic/arm/aarch64/CONFIG_STRICT_DEVMEM
new file mode 100644
index blahblah..blahblah 100644
--- /dev/null
+++ b/redhat/configs/ark/generic/arm/aarch64/CONFIG_STRICT_DEVMEM
@@ -0,0 +1 @@
+# CONFIG_STRICT_DEVMEM is not set
diff --git a/redhat/configs/pending-common/generic/arm/aarch64/CONFIG_DEVMEM b/redhat/configs/pending-common/generic/arm/aarch64/CONFIG_DEVMEM
deleted file mode 100644
index blahblah..blahblah 0
--- a/redhat/configs/pending-common/generic/arm/aarch64/CONFIG_DEVMEM
+++ /dev/null
@@ -1 +0,0 @@
-CONFIG_DEVMEM=y
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1408
2 years, 3 months
[OS-BUILD PATCH] Turn CONFIG_DEVMEM back on for aarch64
by Justin M. Forbes (via Email Bridge)
From: Justin M. Forbes <jforbes(a)fedoraproject.org>
Turn CONFIG_DEVMEM back on for aarch64
We have ended up with a config mismatch for the RHEL configs in a way
that was unclear and untracked. CONFIG_STRICT_DEVMEM is enabled in
configs/common/generic, but CONFIG_DEVMEM was disabled for aarc64 in
RHEL (though not in Fedora). This creates a mismatch situation where the
configs do not get generated in the way they are set. Our options are
to either turn on CONFIG_DEVMEM as I have here, or turn off
CONFIG_STRICT_DEVMEM for aarch64. I went with the former, but I am
happy to change this if needed, we just need the configs coherent.
Signed-off-by: Justin M. Forbes <jforbes(a)fedoraproject.org>
diff --git a/redhat/configs/ark/debug/arm/aarch64/CONFIG_DEVMEM b/redhat/configs/ark/debug/arm/aarch64/CONFIG_DEVMEM
deleted file mode 100644
index blahblah..blahblah 0
--- a/redhat/configs/ark/debug/arm/aarch64/CONFIG_DEVMEM
+++ /dev/null
@@ -1 +0,0 @@
-CONFIG_DEVMEM=y
diff --git a/redhat/configs/ark/generic/arm/aarch64/CONFIG_DEVMEM b/redhat/configs/ark/generic/arm/aarch64/CONFIG_DEVMEM
deleted file mode 100644
index blahblah..blahblah 0
--- a/redhat/configs/ark/generic/arm/aarch64/CONFIG_DEVMEM
+++ /dev/null
@@ -1 +0,0 @@
-# CONFIG_DEVMEM is not set
diff --git a/redhat/configs/pending-common/generic/arm/aarch64/CONFIG_DEVMEM b/redhat/configs/pending-common/generic/arm/aarch64/CONFIG_DEVMEM
deleted file mode 100644
index blahblah..blahblah 0
--- a/redhat/configs/pending-common/generic/arm/aarch64/CONFIG_DEVMEM
+++ /dev/null
@@ -1 +0,0 @@
-CONFIG_DEVMEM=y
--
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1408
2 years, 3 months