Re: [OS-BUILD PATCH] redhat: add documentation about the os-build rebase process
From: Don Zickus on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1387#note_680599158 There is a long run-on sentence here. Can we break it up? One suggestion (starting at 'Keeping the process..upstream merges only'): "" Rebasing from time to time, helps reduce the clutter of the extra changes on top of upstream and future merge conflicts. This periodic rebase addresses the needs of the Fedora community's desire to separate upstream from Fedora specific changes, helps keep it clear what patches changed in the final form upstream, and what a Fedora specific patch looks like currently as opposed to split across various conflict patches. While rebasing has a negative effect on developer contribution, we believe saving the rebase for the end of release cycle allows for minimal developer contribution disruption while gaining the above advantages. This process is open to feedback for improvements. "" The spirit of the above is to lay out our reasons for performing a developer impacting rebase. And then acknowledging that we understand this negatively impacts developers. Followed by our desire to continue to evolve this process. Feel free to re-word/write my suggestion. :-) Thoughts? ___ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: [OS-BUILD PATCH] redhat: add documentation about the os-build rebase process
From: Don Zickus on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1387#note_680602442 @jmflinuxtx - i want to document our reasons for doing the rebase. With that knowledge, I believe it helps others improve our process if they stumble upon a better way then what we do now. Can you review Herton's opening statement and/or my suggested improvements to see if they capture our reasons? ___ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[OS-BUILD PATCHv2] redhat: add documentation about the os-build rebase process
From: Herton R. Krzesinski redhat: add documentation about the os-build rebase process We have been rebasing os-build lately on each new major Linux upstream release. Add general instructions/guideline on how to do the rebase process on top of last upstream tag/commit. This also provides an explanation on why we are doing the rebase, provided by Don Zickus. Signed-off-by: Herton R. Krzesinski diff --git a/redhat/docs/maintaining.rst b/redhat/docs/maintaining.rst index blahblah..blahblah 100644 --- a/redhat/docs/maintaining.rst +++ b/redhat/docs/maintaining.rst @@ -128,6 +128,66 @@ above Fedora build. To kick off manually run +Rebasing + + +When a new major version of Linux is released upstream, we can rebase the +os-build branch. + +Rebasing from time to time, helps reduce the clutter of the extra changes +on top of upstream and future merge conflicts. This periodic rebase addresses +the needs of the Fedora community's desire to separate upstream from Fedora +specific changes, helps keep it clear what patches changed in the final form +upstream, and what a Fedora specific patch looks like currently as opposed to +split across various conflict patches. + +While rebasing has a negative effect on developer contribution, we believe +saving the rebase for the end of release cycle allows for minimal developer +contribution disruption while gaining the above advantages. + +This process is open to feedback for improvements. + +To do the os-build rebase, the following steps can be done: + +:: + + # Create a rebase branch from latest os-build branch and start the process + # For any conflicts that arise, check and fix them, following git instructions + git fetch origin + git checkout -b rebase origin/os-build + marker=$(cat redhat/marker) + git rebase $marker + + # After you finish the rebase, check the results against the current os-build + git diff origin/os-build.. + # If there are differences shown, you might have fixed conflicts wrongly or + # in a different way. To fix, you may want to add extra on top commits and + # rebase again interactively +&& git add + # create dummy commit + git commit + # You may need to create more than one commit, if changes are related to + # more than one previous commit. Then squash commits into the existing + # previous commits related to the change with: + git rebase -i $marker + + # Now cleanup any commits that we might have reverted, and release commits. + # When editor opens with the commit list in interactive mode, search for any + # commits starting with "Revert " in the subject and if they match a previous + # commit which is being reverted, you can remove both. For release commits, + # search commits with subject starting with "[redhat] kernel-" and delete/ + # remove them. + git rebase -i $marker + + # Check results again doing a diff against os-build branch. Because of cleanup + # in the previous step, some differences will appear now, and that's ok + # because of the removal of the release commits. The only differences that + # should appear are on Makefile.rhelver, redhat/kernel.changelog and + # redhat/marker + git diff origin/os-build.. + + # If differences shown are expected, we are ok and rebase is done. + :: TODO FILL ME IN -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1387 ___ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: [OS-BUILD PATCHv2] redhat: add documentation about the os-build rebase process
From: Herton R. Krzesinski on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1387#note_680671213 I updated the docs with your suggestion. I was struggling writing a good one yesterday. Please take a look. ___ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: [OS-BUILD PATCHv2] redhat: add documentation about the os-build rebase process
From: Don Zickus on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1387#note_680769864 @hertonrk-rh - thanks for the update. The process seems to be missing a last step. Probably obvious, but I was expecting a git checkout os-build git reset --hard rebase git push -f origin os-build or something similar as a 'finalize' the rebase process. Or perhaps you and Justin do not do that? ___ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: [OS-BUILD PATCHv2] redhat: add documentation about the os-build rebase process
From: Herton R. Krzesinski on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1387#note_680776133 Ok I'll add it. We do the force push yes. ___ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[OS-BUILD PATCHv3] redhat: add documentation about the os-build rebase process
From: Herton R. Krzesinski redhat: add documentation about the os-build rebase process We have been rebasing os-build lately on each new major Linux upstream release. Add general instructions/guideline on how to do the rebase process on top of last upstream tag/commit. This also provides an explanation on why we are doing the rebase, provided by Don Zickus. Added some of his suggestions as well on the rebase process instructions. Signed-off-by: Herton R. Krzesinski diff --git a/redhat/docs/maintaining.rst b/redhat/docs/maintaining.rst index blahblah..blahblah 100644 --- a/redhat/docs/maintaining.rst +++ b/redhat/docs/maintaining.rst @@ -128,6 +128,78 @@ above Fedora build. To kick off manually run +Rebasing + + +When a new major version of Linux is released upstream, we can rebase the +os-build branch. + +Rebasing from time to time, helps reduce the clutter of the extra changes +on top of upstream and future merge conflicts. This periodic rebase addresses +the needs of the Fedora community's desire to separate upstream from Fedora +specific changes, helps keep it clear what patches changed in the final form +upstream, and what a Fedora specific patch looks like currently as opposed to +split across various conflict patches. + +While rebasing has a negative effect on developer contribution, we believe +saving the rebase for the end of release cycle allows for minimal developer +contribution disruption while gaining the above advantages. + +This process is open to feedback for improvements. + +To do the os-build rebase, the following steps can be done: + +:: + + # Create a rebase branch from latest os-build branch and start the process + # For any conflicts that arise, check and fix them, following git instructions + git fetch origin + git checkout -b rebase origin/os-build + marker=$(cat redhat/marker) + git rebase $marker + + # After you finish the rebase, check the results against the current os-build + git diff origin/os-build.. + # If there are differences shown, you might have fixed conflicts wrongly or + # in a different way. To fix, you may want to add extra on top commits and + # rebase again interactively +&& git add + # create dummy commit + git commit + # You may need to create more than one commit, if changes are related to + # more than one previous commit. Then squash commits into the existing + # previous commits related to the change with: + git rebase -i $marker + + # Now cleanup any commits that we might have reverted, and release commits. + # When editor opens with the commit list in interactive mode, search for any + # commits starting with "Revert " in the subject and if they match a previous + # commit which is being reverted, you can remove both. For release commits, + # search commits with subject starting with "[redhat] kernel-" and delete/ + # remove them + git rebase -i $marker + + # Check results again doing a diff against os-build branch. Because of cleanup + # in the previous step, some differences will appear now, and that's ok + # because of the removal of the release commits. The only differences that + # should appear are on Makefile.rhelver, redhat/kernel.changelog and + # redhat/marker + git diff origin/os-build.. + + # If differences shown are expected, we are ok and rebase is done. + # Check if origin didn't change by fetching again. If origin/os-build + # changed, you might need to do a rebase again or cherry-pick latest ark + # only changes into the rebase branch + git fetch origin + + + # We can now force push/update the os-build branch. Also save the current + # os-build branch just for backup purposes + git checkout -b os-build-save origin/os-build + git checkout os-build + git reset --hard rebase + git push -f origin os-build os-build-save + :: TODO FILL ME IN -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1387 ___ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: [OS-BUILD PATCHv3] redhat: add documentation about the os-build rebase process
From: Herton R. Krzesinski on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1387#note_680795043 Done. ___ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: [OS-BUILD PATCHv3] redhat: add documentation about the os-build rebase process
From: Justin M. Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1387#note_680804597 Acked-by: Justin M. Forbes (via approve button) ___ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: [OS-BUILD PATCHv3] redhat: add documentation about the os-build rebase process
From: Don Zickus on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1387#note_680823644 Acked-by: Don Zickus (via approve button) ___ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
[OS-BUILD PATCH] [redhat] redhat/configs: Update configs for secure IPL
From: Claudio Imbrenda [redhat] redhat/configs: Update configs for secure IPL Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1976884 Upstream Status: RHEL-only Tested: by IBM Conflicts: None This commit fixes a regression from RHEL8, where the following CONFIG entries were created in order to support secure IPL on s390x Signed-off-by: Claudio Imbrenda diff --git a/redhat/configs/ark/generic/s390x/CONFIG_SYSTEM_BLACKLIST_KEYRING b/redhat/configs/ark/generic/s390x/CONFIG_SYSTEM_BLACKLIST_KEYRING new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/ark/generic/s390x/CONFIG_SYSTEM_BLACKLIST_KEYRING @@ -0,0 +1 @@ +CONFIG_SYSTEM_BLACKLIST_KEYRING=y diff --git a/redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_LOAD_IPL_KEYS b/redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_LOAD_IPL_KEYS new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_LOAD_IPL_KEYS @@ -0,0 +1 @@ +# CONFIG_LOAD_IPL_KEYS is not set diff --git a/redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_SYSTEM_BLACKLIST_KEYRING b/redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_SYSTEM_BLACKLIST_KEYRING new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/ark/generic/s390x/zfcpdump/CONFIG_SYSTEM_BLACKLIST_KEYRING @@ -0,0 +1 @@ +# CONFIG_SYSTEM_BLACKLIST_KEYRING is not set diff --git a/redhat/configs/ark/generic/s390x/CONFIG_LOAD_IPL_KEYS b/redhat/configs/common/generic/s390x/CONFIG_LOAD_IPL_KEYS rename from redhat/configs/ark/generic/s390x/CONFIG_LOAD_IPL_KEYS rename to redhat/configs/common/generic/s390x/CONFIG_LOAD_IPL_KEYS index blahblah..blahblah 100644 --- a/redhat/configs/ark/generic/s390x/CONFIG_LOAD_IPL_KEYS +++ b/redhat/configs/common/generic/s390x/CONFIG_LOAD_IPL_KEYS diff --git a/redhat/configs/common/generic/s390x/CONFIG_SIGNATURE b/redhat/configs/common/generic/s390x/CONFIG_SIGNATURE new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/common/generic/s390x/CONFIG_SIGNATURE @@ -0,0 +1 @@ +CONFIG_SIGNATURE=y diff --git a/redhat/configs/common/generic/s390x/CONFIG_SYSTEM_DATA_VERIFICATION b/redhat/configs/common/generic/s390x/CONFIG_SYSTEM_DATA_VERIFICATION new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/common/generic/s390x/CONFIG_SYSTEM_DATA_VERIFICATION @@ -0,0 +1 @@ +CONFIG_SYSTEM_DATA_VERIFICATION=y diff --git a/redhat/configs/common/generic/s390x/zfcpdump/CONFIG_INTEGRITY_ASYMMETRIC_KEYS b/redhat/configs/common/generic/s390x/zfcpdump/CONFIG_INTEGRITY_ASYMMETRIC_KEYS new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/common/generic/s390x/zfcpdump/CONFIG_INTEGRITY_ASYMMETRIC_KEYS @@ -0,0 +1 @@ +# CONFIG_INTEGRITY_ASYMMETRIC_KEYS is not set diff --git a/redhat/configs/common/generic/s390x/zfcpdump/CONFIG_INTEGRITY_PLATFORM_KEYRING b/redhat/configs/common/generic/s390x/zfcpdump/CONFIG_INTEGRITY_PLATFORM_KEYRING new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/common/generic/s390x/zfcpdump/CONFIG_INTEGRITY_PLATFORM_KEYRING @@ -0,0 +1 @@ +# CONFIG_INTEGRITY_PLATFORM_KEYRING is not set diff --git a/redhat/configs/common/generic/s390x/zfcpdump/CONFIG_INTEGRITY_SIGNATURE b/redhat/configs/common/generic/s390x/zfcpdump/CONFIG_INTEGRITY_SIGNATURE new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/common/generic/s390x/zfcpdump/CONFIG_INTEGRITY_SIGNATURE @@ -0,0 +1 @@ +# CONFIG_INTEGRITY_SIGNATURE is not set diff --git a/redhat/configs/common/generic/s390x/zfcpdump/CONFIG_KEXEC_SIG b/redhat/configs/common/generic/s390x/zfcpdump/CONFIG_KEXEC_SIG new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/common/generic/s390x/zfcpdump/CONFIG_KEXEC_SIG @@ -0,0 +1 @@ +# CONFIG_KEXEC_SIG is not set diff --git a/redhat/configs/common/generic/s390x/zfcpdump/CONFIG_SIGNATURE b/redhat/configs/common/generic/s390x/zfcpdump/CONFIG_SIGNATURE new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/common/generic/s390x/zfcpdump/CONFIG_SIGNATURE @@ -0,0 +1 @@ +# CONFIG_SIGNATURE is not set diff --git a/redhat/configs/common/generic/s390x/zfcpdump/CONFIG_SYSTEM_DATA_VERIFICATION b/redhat/configs/common/generic/s390x/zfcpdump/CONFIG_SYSTEM_DATA_VERIFICATION new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/configs/common/generic/s390x/zfcpdump/CONFIG_SYSTEM_DATA_VERIFICATION @@ -0,0 +1 @@ +# CONFIG_SYSTEM_DATA_VERIFICATION is not set diff --git a/redhat/configs/fedora/generic/s390x/CONFIG_LOAD_IPL_KEYS b/redhat/configs/fedora/generic/s390x/CONFIG_LOAD_IPL_KEYS deleted file mode 100644 index blahblah..blahblah 0 --- a/redhat/configs/fedora/generic/s390x/CONFIG_LOAD_IPL_KEYS +++ /dev/null @@ -1 +0,0 @@ -CONFIG_LOAD_IPL_KEYS=y -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1371 __
[OS-BUILD PATCH] redhat: bump RHEL_MAJOR and add the changelog file for it
From: Herton R. Krzesinski redhat: bump RHEL_MAJOR and add the changelog file for it kernel-ark does not track anymore work for RHEL 9/CentOS Stream 9. We look forward to the next major. While "8.99" was chosen as the version for the work preceding RHEL 9, bump the major so the considered version now is "9.99". I'm intentionally not removing redhat/kernel.changelog-8.99 yet in this commit, to avoid any conflicts while this isn't merged. When this change goes in, I'll propose a new merge request for the removal of this old changelog file. Also I'm not including/moving all old changelog entries into the new file, to avoid conflicts in the next os-build rebase. So when this is included/merged the first time, no old entries before last release commit will be in the changelog. However, all changelog entries will be picked up with the first release commit in the next os-build rebase. Signed-off-by: Herton R. Krzesinski diff --git a/Makefile.rhelver b/Makefile.rhelver index blahblah..blahblah 100644 --- a/Makefile.rhelver +++ b/Makefile.rhelver @@ -1,4 +1,4 @@ -RHEL_MAJOR = 8 +RHEL_MAJOR = 9 RHEL_MINOR = 99 # diff --git a/redhat/kernel.changelog-9.99 b/redhat/kernel.changelog-9.99 new file mode 100644 index blahblah..blahblah 100644 --- /dev/null +++ b/redhat/kernel.changelog-9.99 @@ -0,0 +1,2 @@ +# The following bit is important for automation so please do not remove +# END OF CHANGELOG -- https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1388 ___ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: [OS-BUILD PATCH] redhat: bump RHEL_MAJOR and add the changelog file for it
From: Justin M. Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1388#note_680900557 Acked-by: Justin M. Forbes (via approve button) ___ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: [OS-BUILD PATCH] redhat: bump RHEL_MAJOR and add the changelog file for it
From: Don Zickus on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1388#note_680980740 Acked-by: Don Zickus (via approve button) ___ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
