Re: [OS-BUILD PATCHv2] configs: enable CONFIG_LEDS_BRIGHTNESS_HW_CHANGED
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1169#note_598017347 Acked-by: Justin 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] perf: enable CoreSight support
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1167#note_596781310 Acked-by: Justin 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] perf: enable CoreSight support
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1167#note_596780470 > I prefer cutting this down to be arm-specific and "trade the spec file complexity", since I see no reason for x86 (and other arch) customers (which I believe is a majority) to install completely useless packages. This is valid. I wasn't thinking about the dep on install, only the build side. As I didn't make the original change in Fedora, I was just verifying that we had this functionality and saw how it was put in. > A better question is, whether linking opencsd would allow the x86 users to e.g. analyse the coresight trace from perf.data obtained on aarch64. In such case, it would make sense. I would have to look at the code to see, or Fedora has been built this way for about a year, so any existing Fedora perf package should be a valid way to test. ___ 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 0/5] ark: Set Architecture Level Set to Z14 for s390
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1144#note_596135080 > is it worth throwing a 'include in release' label and seeing if this can build in eln? I have tagged it with "include in release" and done a test build with it against ELN koji: https://koji.fedoraproject.org/koji/taskinfo?taskID=69629902 The test build was successful, though I can't boot it anywhere to verify that it is working as intended. ___ 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 0/5] ark: Set Architecture Level Set to Z14 for s390
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1144#note_595919862 > glibc 2.34 will detect `-march=z14` and refuse to run on z13 or earlier, to avoid hard-to-diagnose crashes later. We learned the hard way that this very desirable during the ppc64le bringup. Would it still detect this if the kernel running in the build root is a z13 kernel? There are kernel advantages to limiting supported hardware, but z13 added the vector bits, I don't recall z14 adding much instruction wise, so perhaps there is no benefit to building userspace with z14? ___ 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 0/5] ark: Set Architecture Level Set to Z14 for s390
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1144#note_595910611 > do we know which s390x machines ELN builds on? The koji builders are Z13. They are running a Fedora kernel to do the build, so the 5.13-rc5 eln build was done in koji running 5.12.8-300.fc34. These tend to be updated regularly with Fedora, but we do not plan to set to Z14 in Fedora. Of course the build root is running eln userspace packages, so we would need to ensure that nothing in userspace requires Z14, or it will fail. I don't recall Z14 adding a bunch of new instructions, so this might not be an issue. ___ 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] perf: enable CoreSight support
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1167#note_595825564 Curious on this, as Fedora has been building with CORESIGHT for a bit now (since July 2020). We did not case the changes on arch, and simply added openscd-devel as a buildreq for everyone and pass CORESIGHT=1 to perf_make. This builds fine across all arches, even though it is unnecessary. As coresight is an arm specific thing, it is really only used in arch/arm/util/ files and shouldn't be a problem for other architectures. Which makes me ask, do we trade spec complexity for more specific build command line, or do we go the simple spec route and expect it to continue working? ___ 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 0/0] kernel.spec: tools: sync with RHEL 8
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1155#note_595488507 We have been building with it here since rc4. ___ 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 0/0] [redhat] New configs in drivers/hwtracing
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1085#note_592234983 Acked-by: Justin 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] all: Changing CONFIG_UV_SYSFS to build uv_sysfs.ko as a loadable
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1165#note_592015240 I haven't had a request to turn on UV for Fedora, and I am not sure that there is anyone interested in it, but I don't have an issue with flipping it on if anyone is. ___ 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 0/0] Fix sysctl_unprivileged_bpf_disabled sysctl
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1162#note_591410772 Acked-by: Justin 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] Enable NITRO_ENCLAVES on RHEL
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1163#note_591028806 Acked-by: Justin 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 0/0] Fix sysctl_unprivileged_bpf_disabled sysctl
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1162#note_590350124 Added "include in releases" as the kernel will not build without it. I added it to dist-git for rc4 in Fedora, which is building with this patch now successfully. ___ 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] RHEL: disable io_uring support
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1159#note_590315781 Acked-by: Justin 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] RHEL: disable io_uring support
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1159#note_587024136 So it seems Jens is against this for upstream, as IO_URING is "a core feature, and something that more and more apps or libraries are relying on", which is the direction it is heading. I would still like to see the patch follow the path of removing the if EXPERT, which follows a couple of other patches that we are carrying and makes it very clear in our source repository and in dist- git which setting a kernel is going to be built for. ___ 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] RHEL: disable io_uring support
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1159#note_586022475 Or just wait it out, I submitted it upstream. Pavel has at least acked it: https://lore.kernel.org/io- uring/0d335e81-9a94-ca60-5659-bb46080b9...@gmail.com/T/#t ___ 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] RHEL: disable io_uring support
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1159#note_585992923 And x86_64 at least has completed the build successfully for ELN with expert removed and CONFIG_IO_URING turned off: ``` >cat ./lib/modules/5.13.0-0.rc3.20210526gitad9f25d33860.27.eln110.x86_64/config | grep IO_URING # CONFIG_IO_URING is not set ``` ___ 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] RHEL: disable io_uring support
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1159#note_585939162 Not sure what Kconfig options you are saying it adds. In this case, it only adds one for CONFIG_IO_URING. Running a test with the following diff show no unset config options or mismatches in either case when I set CONFIG_IO_URING=y for Fedora and off for ELN. Diff below: `diff --git a/init/Kconfig b/init/Kconfig index 1ea12c64e4c9..0decca696bf7 100644 --- a/init/Kconfig +++ b/init/Kconfig @@ -1621,7 +1621,7 @@ config AIO this option saves about 7k. config IO_URING - bool "Enable IO uring support" if EXPERT + bool "Enable IO uring support" select IO_WQ default y help diff --git a/redhat/configs/common/generic/CONFIG_IO_URING b/redhat/configs/common/generic/CONFIG_IO_URING new file mode 100644 index ..dcae2b3a1327 --- /dev/null +++ b/redhat/configs/common/generic/CONFIG_IO_URING @@ -0,0 +1 @@ +# CONFIG_IO_URING is not set diff --git a/redhat/configs/fedora/generic/CONFIG_IO_URING b/redhat/configs/fedora/generic/CONFIG_IO_URING new file mode 100644 index ..eff85c7a8f85 --- /dev/null +++ b/redhat/configs/fedora/generic/CONFIG_IO_URING @@ -0,0 +1 @@ +CONFIG_IO_URING=y ` And the resulting configs: `>grep IO_URING redhat/configs/kernel-*.config redhat/configs/kernel-aarch64-debug-fedora.config:CONFIG_IO_URING=y redhat/configs/kernel-aarch64-debug-rhel.config:# CONFIG_IO_URING is not set redhat/configs/kernel-aarch64-fedora.config:CONFIG_IO_URING=y redhat/configs/kernel-aarch64-rhel.config:# CONFIG_IO_URING is not set redhat/configs/kernel-armv7hl-debug-fedora.config:CONFIG_IO_URING=y redhat/configs/kernel-armv7hl-fedora.config:CONFIG_IO_URING=y redhat/configs/kernel-armv7hl-lpae-debug-fedora.config:CONFIG_IO_URING=y redhat/configs/kernel-armv7hl-lpae-fedora.config:CONFIG_IO_URING=y redhat/configs/kernel-i686-debug-fedora.config:CONFIG_IO_URING=y redhat/configs/kernel-i686-fedora.config:CONFIG_IO_URING=y redhat/configs/kernel-ppc64le-debug-fedora.config:CONFIG_IO_URING=y redhat/configs/kernel-ppc64le-debug-rhel.config:# CONFIG_IO_URING is not set redhat/configs/kernel-ppc64le-fedora.config:CONFIG_IO_URING=y redhat/configs/kernel-ppc64le-rhel.config:# CONFIG_IO_URING is not set redhat/configs/kernel-s390x-debug-fedora.config:CONFIG_IO_URING=y redhat/configs/kernel-s390x-debug-rhel.config:# CONFIG_IO_URING is not set redhat/configs/kernel-s390x-fedora.config:CONFIG_IO_URING=y redhat/configs/kernel-s390x-rhel.config:# CONFIG_IO_URING is not set redhat/configs/kernel-s390x-zfcpdump-rhel.config:# CONFIG_IO_URING is not set redhat/configs/kernel-x86_64-debug-fedora.config:CONFIG_IO_URING=y redhat/configs/kernel-x86_64-debug-rhel.config:# CONFIG_IO_URING is not set redhat/configs/kernel-x86_64-fedora.config:CONFIG_IO_URING=y redhat/configs/kernel-x86_64-rhel.config:# CONFIG_IO_URING is not set` Of course things seem to be building as expected on rawhide, the config doesn't change. I am testing a build in ELN to be sure, though I exect if issues show up, they would also show up with the original patch as they would be the result of turning off CONFIG_IO_URING. ___ 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] RHEL: disable io_uring support
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1159#note_585922609 ugh, you are correct, and annoyingly it doesn't show in our config prior to build. I think I would rather see this patch changed to remove EXPERT than to change the default on RHEL_DIFFERENCES. That way we are very clear on what is set and where. ___ 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] RHEL: disable io_uring support
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1159#note_585905834 This patch seems completely unnecessary. As it stands, CONFIG_IO_URING is locked behind CONFIG_EXPERT which is disabled for both Fedora and ELN/RHEL. If that situation changes, and it is no longer locked behind CONFIG_EXPERT, it will be presented as a new config option for both Fedora and ELN/RHEL. At that point, you can decide if you want to enable it or not, without having to patch the Kconfig. As it stands right now, you can not enable it at all. Nacked-by: Justin Forbes ___ 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 0/0] kernel.spec: tools: sync with RHEL 8
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1155#note_585871204 I added the tag, so it should be in tomorrow's build. Not really happy with an additional 76 lines to the spec, but I don't see another way. ___ 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 0/5] ark: Set Architecture Level Set to Z14 for s390
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1144#note_585698139 > If I need to push an other version I can add the Fedora update as well. This MR already got way bigger than I expected. So I don't see a problem in adding one more commit. Either way, if you do it in this request, I am happy to take it. If it goes in as a separate MR, fedora specific changes do not require the same ack structure. I review/ack/merge, though with s390x I tend to take whatever you folks recommend. > My understanding so far was that common/ should contain configs that are shared between ark and fedora and not that common/ contains the defaults which can be overwritten in ark/ and fedora/. This is indeed the case in theory, if an entry is in common, it should ideally be the same, with no corresponding entry in fedora or ark directory. In practice, the scripts tend to generate a bit differently. The intention is to run a clean up script on a regular interval which consolidates entries in fedora and ark if they are the same, and removes common if they are different. For this particular case I don't think an entry is necessary in common if they are going to be different, but I do have to ask if we really need them to be different. Does Fedora need to support older hardware here? I am fine with either answer, I really don't know what hardware people are running Fedora on for s390x. ___ 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] team: mark team driver as deprecated
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1063#note_584373061 Acked-by: Justin 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 PATCHv2 0/5] ark: Set Architecture Level Set to Z14 for s390
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1144#note_583699147 Acked-by: Justin 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] Make CRYPTO_EC also builtin
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1150#note_583670885 Acked-by: Justin 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 0/0] Miscellaneous updates for Makefiles and related documentation
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1152#note_582708834 Acked-by: Justin 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] perf: link libtraceevent dynamically
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1148#note_581053570 I have just tested with similar changes to kernel-tools in Fedora (libtraceevent is not packaged for F33, but is for F34+). Seems this is worthwhile. ___ 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 0/3] ark: Set Architecture Level Set to Z14 for s390
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1144#note_579901839 As this is the merge request creating the dependency on those, the best path forward is to put them in common instead of pending-common. The make dist-configs breakage doesn't happen until this MR goes in, and if they are in common it won't happen after it goes in either. If they need reviewers from other areas, you can CC them and they will get reviewed that way, or we can try to add the right people ___ 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 0/3] ark: Set Architecture Level Set to Z14 for s390
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1144#note_579494927 I would suggest not changing pending-common. That is the location for pre-reviewed, automated defaults. Nothing should be created there without a corresponding MR to get that config reviewed and move it to common. ___ 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 0/0] kernel.spec: Add support to store build artifacts
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1035#note_578321120 Right, so the Makefile generates vmlinux.h if the value is null, and copies it over if the value is set to something. We could probably simplify this even more. I assumed there was a flag passed in cki to rpmbuild for --only-tools or something, but I don't see it. If we had such a flag, we could key off of that and set VMLINUX_H to the path for this specific kernel in kernel-devel. If we are building without that flag, it would be null and then generate it's own. ___ 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] perf: enable CTF support
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1140#note_577067435 This is how we build in Fedora. ___ 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] perf: enable dynamic linking of libbpf
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/#note_575712896 Not sure about a scratch build, but this is merged as of 3 days ago, so the actual builds of the ELN kernel from the last couple of days are using it. https://koji.fedoraproject.org/koji/buildinfo?buildID=1747130 ___ 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 0/0] Improve generation of boot loader specification files
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1042#note_573638944 We have been building with this for a couple of days now, and I haven't seen any issues on test systems. ___ 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] Disable CONFIG_NETFILTER_XTABLES_COMPAT
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1126#note_572523304 I am okay with it. I will just need to see if it is something I need to keep on for the existing stable Fedora releases, but turning it off for F35 and newer is acceptable. ___ 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] team: mark team driver as deprecated
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1063#note_572520688 The scripts that generate these requests also go through RHMAINTAINERS and look for the proper reviewer. They are added via the Cc Lines in the MR, and that is how they are added as reviewers even if not a member of the project. I am not sure why it doesn't allow you to add non members via the UI but it does work via Cc lines. ___ 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] perf: enable dynamic linking of libbpf
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/#note_571904765 There is now a patch queued for upstream, which fixes the build issue. I am okay with this going in, if it is merged before that patch lands, I will do a temp MR to include it in releases. Acked-by: Justin M. Forbes ___ 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] Fix branch creation for releases based on tags
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/351#note_571531270 Reverting this for now, it seems to not work as intended: fatal: 'ark/patches/master' is not a commit and a branch 'ark/master' cannot be created from it ___ 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] Keep sctp and l2tp modules in modules-extra
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1117#note_570447318 I don't know that it would be worthwhile, I think it might be easier to write something to check it after the fact, or even the script to verify against sources. Honestly, if we stop building a module and the entry is just abandoned in the extra list for a bit, that is unfortunate, but not really problematic. Modules moving from extras to kernel-modules due to deps is a real issue, and there are a number of ways to monitor 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 PATCH] Keep sctp and l2tp modules in modules-extra
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1117#note_570334250 It should work both ways, the email bridge seems a big laggy today though. instead of instant, it is on a delay. Email comments end up on gitlab and gitlab comments should end up in email though. ___ 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] Keep sctp and l2tp modules in modules-extra
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1117#note_570289882 We do want it to ignore files that do not actually exist, othrewise we would have to change the extras list to be per arch, and frankly that sounds like more than I want to deal with. I can very easily add something to the kerneltest scripts that run on x86_64 at least after every build to diff modules-extra with the previous build. It would be a start, though I think we could do something similar with rpminspect output in bodhi QA. All rawhide and eln builds get filed in bodhi. ___ 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] Keep sctp and l2tp modules in modules-extra
From: Justin Forbes on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1117#note_570213935
> Anyway, the commands I used are: time find . -name "Makefile\*" -exec
grep '.o' {} ; > /tmp/don.list (3 seconds) for i in `cat
redhat/rhel_files/*.list.rhel redhat/fedora_files/*.list.fedora`;do
mod="$(echo $i | sed 's/ko$/o/')"; grep -q $mod /tmp/don.list || echo
"Bad module: $i"; done|wc -l
I don't think that addresses the issue, I think the issue is when a new
module comes along with a dep on a module that was in extras, and moves
the extras module back to kernel-modules. The only real way to do that
is to diff the file lists of module every time and list anything missing
that was in the previous verison.
___
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 0/0] Improve generation of boot loader specification files
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1042#note_570170011 From the upstream thread, it seems that building for different targets can cause problems, for instance, building ppc64 fails, but building ppc64le on a ppc64 host works. Cross compiling can either bypass or introduce the issue. S390x native works in koji. I am assuming the pahole fix will address all of these corner cases. ___ 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 0/0] Improve generation of boot loader specification files
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1042#note_570158863 I added an include in releases to this patch. Note, while the build fails, it is only aarch64 that is failing. Koji is still producing build and rpms for all other arch, you just have to install them from koji as they will not end up in a compose until aarch64 is fixed. ___ 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 0/0] Improve generation of boot loader specification files
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1042#note_570157165 @dzickusrh Not that I am aware of, the patches I have seen thrown around upstream are to pahole, not the kernel. This is still being actively discussed, with the last message in the thread 10 hours ago. ___ 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] perf: enable dynamic linking of libbpf
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/#note_570153780 So, it turns out this can be problematic for ARK/Rawhide. I just added this to the kernel-tools package for rawhide, and the issue is, libbpf- devel is missing hashmap.h. My ongoing concern, is this tree builds linus' branch pretty much daily. as libbpf has been moving very quickly the last several releases, how often are we going to fail a build because perf is using some new bpf feature that has made it into linus' tree, and not made it to the last libbpf package? Right now, we are building the 5.13 merge window, and libbpf was last updated months ago. ___ 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] Keep sctp and l2tp modules in modules-extra
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1117#note_569297906 There is something coming that will help with that. When rpminspect is used for autoqa in bodhi, we should see a notification when files move. ___ 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 PATCHv19 0/4] [redhat] Add GIT macro to Makefile and Makefile.common:
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/issues/40#note_569259804 I was waiting until the merge window closes to do the Fedora configs, which would properly test this. Either close it, and I can reopen if it doesn't, or I will close the issue once I have done them and verified that it does. ___ 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 PATCHv19 0/4] [redhat] Add GIT macro to Makefile and Makefile.common:
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/issues/39#note_569259385 I thought this was fixed with MR https://gitlab.com/cki-project/kernel- ark/-/merge_requests/1061 ___ 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] perf: enable dynamic linking of libbpf
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/#note_569176912 Is libbpf a separate package in RHEL? In Fedora it is built as part of the kernel-tools package, but that package is not ported over to ELN/RHEL because kernel-tools is built as part of kernel. The kernel package does not create a libbpf or libbpf-devel package in ELN or RHEL. ___ 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] perf: enable dynamic linking of libbpf
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/#note_569180382 Nevermind, looks like it is a separate package in Fedora as well with an epoch set so it overrides the kernel-tools package. Which begs, the question, why weren't we just told to drop it from kernel-tools. Jiri is who asked it be added to kernel-tools and sent the patch to do so, and then packaged it himself separatetly but left me maintaining it in tools as well? ___ 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] spec: Add bzip2 dependency to perf package
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1103#note_568799018 Yes, sorry. Just meant I should have caught it when looking at other differences between the fedora tools package, and the ark tools subpackage. ___ 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] spec: Add bzip2 dependency to perf package
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1103#note_567984832 Not sure how this was missed here, Jiri added it to kernel-tools in Fedora a couple of years ago. ___ 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 PATCHv19 0/4] [redhat] Add GIT macro to Makefile and Makefile.common:
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/issues/48#note_567145528 Wait just a minute on that, there is a filter issue with the surface modules merge. I am testing a fix, but your x86_64 build will fail until I get that pushed. ___ 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 PATCHv19 0/4] [redhat] Add GIT macro to Makefile and Makefile.common:
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/issues/48#note_567130107 No, it is not, the issue came up a while ago in Linux next, and they fixed it for everything but aarch64. I have brought it up with upstream maintainers and was told: > the fix is being worked on, just figuring the proper way at the moment: > https://lore.kernel.org/bpf/20210427182053.ttiuxdt675lzmvk3@kafai- mbp.dhcp.thefacebook.com/T/#mb49c7d3d32700fa0e9c8b019fa3bf9d9e0cc3bf5 I am still pushing to rawhide because the build data for other architectures is useful and relevant. Closing this as it is an upstream issue that will be fixed in ark within a day of the fix landing upstream. ___ 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 PATCHv19 0/4] [redhat] Add GIT macro to Makefile and Makefile.common:
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/issues/47#note_567069865 Did a test build with # CONFIG_DEBUG_INFO_BTF is not set, this is not the problem, I get the same output. ___ 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 0/0] Drop the %{variant} macro and fix --with-vanilla
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1088#note_566256679 Ahh, sorry. there are plenty of things in the spec that I just don't ever use, but as long as they are useful, I am happy to keep them. My comment had the desired effect, in that I wanted some feedback from people who do build vanilla kernels, and how they wanted them labelled. ___ 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 0/0] Drop the %{variant} macro and fix --with-vanilla
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1088#note_566198724 As I recall, the problem with --with-vanilla is rpm complains over -vanilla. I think there are 2 possible fixes, changing the variant from "-vanilla" to ".vanilla", or just dropping the variant all together. In my opinion, I prefer this solution because it cleans up the spec quite a bit, but I am also not a big user of "--with-vanilla". For people wishing to have vanilla marked, you can always 'echo vanilla > localversion", though it wouldn't be automated based on the build args. ___ 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] New configs in fs/nfs
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/788#note_566098257 Steve, I left it off in Fedora because of "This is intended for developers only. The READ_PLUS operation has been shown to have issues under specific conditions and should not be used in production." At what point to you expect it to be safe to turn on for stable Fedora releases? ___ 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 PATCHv19 0/4] [redhat] Add GIT macro to Makefile and Makefile.common:
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/issues/45#note_566062987 Of note, the commit log from 8da650b56e4fec39041edc15f2c328e2b7d29717: > A few more fixes for local builds. None of this works until .1 Until I have tagged and pushed kernel-5.12.1-0, do not expect the fedora-5.12 branch to be effective. I mainly pushed it so that Peter could do the arm clean ups that he typically does for stable releases as he has time, and so that fixes from 5.11 could be applied and don't get forgotten. I should have everything working today at some point. ___ 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 PATCHv19 0/4] [redhat] Add GIT macro to Makefile and Makefile.common:
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/issues/45#note_566036154 Tags are there, I never did a tag push because I hadn't gotten that far in the release yet for 5.12.1 and 5.11.18 builds. I changed my sync script to push them when I pull from greg though. Sorry about 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 PATCHv19 0/4] [redhat] Add GIT macro to Makefile and Makefile.common:
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/issues/44#note_565170086 This was fixed with f23ad26468fce25011739cf9980761ef81483c43 Sorry, was getting to it, today's build was broken in multiple ways, and I have been workign through them. ___ 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 0/0] Make package versioning reproducible for snapshot builds
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1061#note_563988223 Thanks for doing this, it looks good. ___ 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] Don't create empty pending-common files on pending-fedora commits
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1060#note_563122710 Looks good to me. I will definitely give it a good workout when I start moving the Fedora configs ___ 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 PATCHv4 0/4] nvme: update error handling and ana_state to work well with device-mapper-multipath
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1024#note_562824788 While I am not particularly happy about it, I understand the situation. I said it could be merged when it gets the acks, as the code is RHEL only, and the patch will be dropped from stable Fedora releases. I thought @ptalbert was going to merge it at some point this week. ___ 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 PATCHv19 0/4] [redhat] Add GIT macro to Makefile and Makefile.common:
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/issues/39#note_562665828 Of note, I think the reason this does not exist, and no one has cared to put in the effort, is because dist-git is still considered the canonical source of truth for Fedora builds, and if you want an exact reproduction of that day, this is where you would build it from. The kernel-ark tree is used for development, releases are tagged because it is helpful for debugging issues with a specific build, but the versioning changing makes complete sense because you are not reproducing the exact build, you are building something possibly quite different. If you wanted the exact build, you would use dist-git. ___ 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 PATCHv19 0/4] [redhat] Add GIT macro to Makefile and Makefile.common:
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/issues/39#note_562648033 > We want to use this exact moment as the date in the NVR. But, I believe we should read that from the commit date for that tag, not from the shell script checking the system clock after it has been tagged. We can't use the exact moment, the version string on a snapshot is as long as practical, we can barely append 'test' for a test build due to rpm limitation. It could be that date I suppose. Though there is nothing there that guarantees it matches what was tagged. > If there are local changes, they should be committed locally (not necessarily tagged) and that would affect the commit date though, right? > > Can we make it so that if there are no local changes — if this is a pristine copy of earlier sources — we get the same NVR? If I am rebuilding a package today from the exact sources that were tagged 3 weeks ago, I believe the date should be 3 weeks ago, not today. I don't think this is a versioning issue, so much as a script issue. The right way to do this would be to add a make reproduceable-build target which did a clean checkout of that tag and disgarded all untracked files, then it used that date. That target does not exist right now, and there is no way for current targets to validate that what you are building is in fact identical. The actual kernel patches are checked for uncommitted changes, but the rpm files, configs, etc are not. ___ 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 PATCHv19 0/4] [redhat] Add GIT macro to Makefile and Makefile.common:
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/issues/39#note_562593935 Koji has nothing to do with the date tag in the n-v-r, the date tag is when 'make release' was run, which may not be the same date that release is pushed to dist-git with 'make dist-git', and neither of those dates have any direct correlation to when the build was submitted to koji. The git tag in the NVR is the git tag of the upstream commit used. The tag in the kernel-ark tree is placed on the commit used in os-build to make that release, and the date is the date at which the make release was tagged. Make dist-all-rpm is used for testing and development purposes, and expects that there may be changes not from a tagged release, so it can intentionally change the goalpost. Make dist-git is what I would use to create an exact copy of a release. ___ 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 PATCHv4] Export ark infrastructure files
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/968#note_557234552 I guess we get to test that additional failure path more quickly than I had hoped. Since this was merged, the nightly 'Prepare Release' script fails with `$ git push gitlab "$(git describe)" fatal: v5.4-2-gfca5c95176e2 cannot be resolved to branch fatal: the remote end hung up unexpectedly` ___ 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 PATCHv19 0/4] [redhat] Add GIT macro to Makefile and Makefile.common:
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/issues/43#note_555971912 Fixed with https://gitlab.com/cki-project/kernel- ark/-/commit/8691fd224224aa9aecce9ad2105e4b0828f5cd8d ___ 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 PATCHv19 0/4] [redhat] Add GIT macro to Makefile and Makefile.common:
From: Justin Forbes on gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/issues/42#note_555188897
> `kernel` and `kernel-debug` are both just metapackages.
>
> When `%{debugbuildsenabled}` is 0, can we still produce a `kernel-
debug` metapackage?
This would be a possible solution. Don't think there is any problem with
multiple meta packages.
___
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 PATCHv19 0/4] [redhat] Add GIT macro to Makefile and Makefile.common:
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/issues/42#note_555185290 It is not a use case that has an easy solution within the confines of rpm/dnf right now, though the simple way to do it would be to write up repo builder script that grabs the latest build daily if it has changed. If kernel-debug exists, delete the non-debug packages, otherwise keep the base packages, run createrepo and add a dnf config for kernels from that local repository. ___ 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 PATCHv19 0/4] [redhat] Add GIT macro to Makefile and Makefile.common:
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/issues/42#note_555112975 > Ok, that's what I had assumed. Can we make the naming consistent though, while still accomplishing that? The naming is inline with package guidelines. rcX releases are in fact upstream releases (you can download the tarball on kernel.org). The git snapshots are not releases, and are snapshots. Versioning follows for each. As to the sub packages, producing only kernel-debug for a non debug build will break a whole lot of the things we wish to test. The existance of a package called 'kernel' is fairly critical. Inverting the naming would just be confusing for everyone involved. Again, we want those scripts which just rely on 'kernel' to test the debug kernel frequently, but also the non debug kernel at least once a week (we have had issues where things worked in a debug kernel, and broke in non debug). As to the users who prefer to only run non-debug kernels, they get those in Rawhide nodebug, or only do updates on Monday evening or Tuesday morning. > I'm not sure what you mean by the no-debug repository? https://dl.fedoraproject.org/pub/alt/rawhide-kernel-nodebug/ It is set to ensure that people always get the latest debug kernel with a 'dnf update' for people using the rawhide repository for other things, they can exclude kernel in the rawhide repository config, for people using stable kernel but running a rawhide kernel, stable versions will always be lower. In either case, adding rawhide-nodebug as a separate repository will keep the intended kernel installed. We added this repository and model in 2012. ___ 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 PATCHv19 0/4] [redhat] Add GIT macro to Makefile and Makefile.common:
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/issues/42#note_555069659 The reason that this is set is because there is overhead in running debug builds. We have a whole lot of users willing to run a rawhide kernel for day to day, and the testing we get from that is very valuable. The agreement we have, is the first build for each new rcX is built as a release kernel. That is also copied off to the rawhide no- debug repository so we have a secure-boot signed kernel there which is not a debug kernel. The debug builds in between are much more useful for various testing mechanisms, and for users who are more interested in test environments than running their desktop off of it, though we do have a few users who will run their desktops on those builds as well. Making the in between releases debug only kind of forces some testing that would not otherwise occur, and leads to frequent finds of new lockdep issue, etc. The 'make debug' and 'make release' commands mentioned in the spec file should be changed, they are a relic from the pre-kernel-ark days when I did have to run 'make release' for every rcX build and 'make debug' to get back to snapshots. Those commands would just flip the bit in the spec file and bumpspec for the changelog. ___ 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] Fix `Make dist-srpm` issue with CONFIG_VDPA
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1034#note_553977999 This is addressed by MR 1033, though it turns it off. ___ 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 PATCHv4] docs: Update docs to reflect newer workflow.
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/772#note_553972180 Yes, this seems correct. For the default case, no one should have to care beyond "origin" ___ 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 0/0] filter-modules.sh.fedora: drop unused list "iiodrvs"
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1029#note_553909018 This does seem to work as expected. kernel/drivers/gpu/drm/tiny/ is moved from kernel-core to kernel-modules on armv7 and aarch64, etc. Thanks for cleaning this up! ___ 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 0/0] filter-modules.sh.fedora: drop unused list "iiodrvs"
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1029#note_552940252 Given the nature of it, I did an include-in-release for Fedora, will compare the next builds with the previous. ___ 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] New configs in drivers/vdpa
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/837#note_552600093 @sgarzarella That wouldn't be a part of this MR, but I just turned it on for Fedora, it will be enabled starting with kernel-5.11.15. ___ 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 PATCHv19 0/4] [redhat] Add GIT macro to Makefile and Makefile.common:
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/issues/41#note_551800150 Just as an update, for a quick temp fix, I modified the fedora-5.11 tree to always set it to 0, and I can manually bump it if I end up doing a second build for any reason. Better solution to come in 5.12 ___ 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 PATCHv19 0/4] [redhat] Add GIT macro to Makefile and Makefile.common:
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/issues/41#note_550951201 > This would be handy. Because, otherwise I can't determine a tagname automatically based only on a "package-version" name. Currently, I need first to grep all available tags for kernel-5.11.13, find the tag with suffix -15 and only after checkout to it. Okay, will look at getting this built into the scripts. In the meantime, grep all available tags for kernel-5.11.13 should return exactly 1 result, and the same goes for any 5.11.x that we actually shipped to a stable fedora release. ___ 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 PATCHv19 0/4] [redhat] Add GIT macro to Makefile and Makefile.common:
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/issues/41#note_550913432 There are a couple of things here: > Fedora RPM tagging in the ARK kernel began in May 2020 for fc33. This line is not entirely accurate, as ARK was only used for Rawhide from May of 2020 until the 5.11 rebases happened last month. At that point, ARK was used for all 5.11.* releases. They are not tagged differently because they are not different in any way. The script to do stable releases literally sits on the same commit (currently in the fedora-5.11 branch) and does: ``` for release in `cat redhat/release_targets`; do case "$release" in 34) build=300 ;; 33) build=200 ;; 32) build=100 ;; esac make IS_FEDORA=1 DIST=".fc$release" BUILDID="" BUILD=$build RHDISTGIT_BRANCH=f$release dist-git; done ``` There have been cases where the configs differ across versions, but that is not currently the case Any time that case does pop up, it will be notated in redhat/rebase-notes.txt. The source tarball and patch set are identical as they are built from the same script based on the same commit on the same branch. The 15 mentioned there is somewhat relevant in that it is the 15th tagged build of 5.11, but given that we very rarely do more than one build of a given upstream release, just searching for 5.11.13 will likely find you the tag you are looking for. I suppose we could reset that number with every version bump so that it would match the last digit of BUILD always. ___ 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 0/5] nvme: update error handling and ana_state to work well with device-mapper-multipath
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1024#note_550884624 I have to be honest, I am not too thrilled at the idea of taking a patch set which has been rejected upstream into ARK. RHEL is one thing, with he guarantee of a stable ABI. there is a lot less churn. This tree merges with the linus tree daily, and will continue to do so long after RHEL is branched off to be it's own thing. A patch which has been rejected upstream will have to be maintained and merge issues dealt with indefinitely. ___ 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 PATCHv19 0/4] [redhat] Add GIT macro to Makefile and Makefile.common:
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/issues/40#note_548390887 Two more odd observations about the error. First, I closed all of those MRs yestrday, and when the script ran again, it just recreated them, even though there should be no config issues (files are in pending- fedora, the config should be sane). Second, it creates the files in pending-fedora, it does not create files in pending-common (and shouldn't need to because the configs options are not exposed for RHEL), but the MR is for new empty files in common. Typical behavior would create files in pending-common and create an MR to move those to common. ___ 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 PATCHv19 0/4] [redhat] Add GIT macro to Makefile and Makefile.common:
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/issues/39#note_547946553 It is an important distinction that the typical package has an upstream source repository, and dist-git. We have essentially 2 different upstream repositories and dist-git, so having the date generated the way it does gives me some information about the kernel-ark repository, while the git tag gives me some information about upstream, both are useful in day to day at a glance. ___ 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 PATCHv19 0/4] [redhat] Add GIT macro to Makefile and Makefile.common:
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/issues/39#note_547944992 kernel-5.11.0-155 kernel-5.11.0-156 kernel-5.11.0-157 kernel-5.11.0-158 These are tags by an autogenerated by scripts and have nothing to do with dist-git because most of them were not used. Of those, only kernel-5.11.0-155 was built for rawhide, with an extra build of 156 for F34. The rest of them were never in dist-git at all. `` does distinguish the actual tag applied and is useful there. The date is useful in being able to quickly see when a build was last done, or more importantly to distinguish quickly if a script failed and ark-latest does not have a valid new build. As we build rawhide almost daily, and in the morning, I can tell you what I build in dist-git today was in Linus' tree yesterday most of the time. There is a 1 day difference in most cases. It is static, and as a maintainer it is much more useful as a representation of when the tree was built vs when linus handled a pull request. Remember, this date doesn't necessarily correlate with when I generate dist-git so much as when ark-latest is composed in practice. It has happened several times that I don't get to a build until the next day, but before the script runs. By the time that finishes koji, it looks like a fresh build, but it is probably time to start the next one because that was older. Developers are doing various things from os- build, but from a maintainer standpoint, dist-git is only generated from ark-latest. As to whether `` remains where it is, or is moved to between the 0 and rc, I just don't care all that much. The reasons for keeping it at the end are, it seems more logical with the build number being at the end, as versioning gets more granular from left to right. It also falls into the "if it ain't broke" category in that it has been there for a good 10 years now, and I don't see any particular advantage to changing it. But in the end, it doesn't really make a ton of difference to me. Perhaps some of the ELN developers and maintainers would have stronger opinions there as they have a *lot* more tooling around completed builds than Fedora does. ___ 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 PATCHv19 0/4] [redhat] Add GIT macro to Makefile and Makefile.common:
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/issues/39#note_547885204 https://www.kernel.org/ for reference. ___ 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 PATCHv19 0/4] [redhat] Add GIT macro to Makefile and Makefile.common:
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/issues/39#note_547881033 rc releases such as kernel-5.12.0-0.rc6.184 are built as release kernels which is why they differ. It is an actual upstream release. ___ 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 PATCHv19 0/4] [redhat] Add GIT macro to Makefile and Makefile.common:
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/issues/39#note_547745411 Date in this case is very much important and different in that the git commit there is the upstream (Linus tree) commit, and not the kernel-ark commit id. Date gives us a bit more information as to what changes might have gone in between when Linus last pushed code, and when we created the dist-git for it. In fact, in all cases, I would assume git ID will give you the date of the upstream source commit, and date should be when the package was prepared for Fedora. Otherwise, the date is basically redundant information. ___ 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 PATCHv19 0/4] [redhat] Add GIT macro to Makefile and Makefile.common:
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/issues/39#note_547725975 The decision to drop `` to 1 was made after 5.12 started as the numbers are climbing inconsistently with what we want. Realistically 100/200/300 have special meaning for Fedora stable releases, and rawhide should always be below 100. As to moving the `` to before the rc, I don't have particularly strong opinion on it, it has always been used just before the fedora release for well over a decade at this point, so that was where it was kept when we added the git tag. Though `` was typically '1'. For instance: kernel-5.6.0-0.rc2.git2.1.fc33 kernel-3.0-0.rc6.git0.1.fc16 My only concern might be that someone has a script somewhere expecting behavior that has existed for over a decade. ___ 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 PATCHv19 0/4] [redhat] Add GIT macro to Makefile and Makefile.common:
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/issues/39#note_547598365 As a prerelease kernel, we have never relied on for ordering, nor should we. This is not a valid 5.12 release. 5.12.0-1 should supercede it. I will say that the release bump is not entirely necessary, though you can get into the case of building multiple snapshots in the same day (rarely), and it can matter. I thought the solution we agreed upon was to reset the release number for each kernel series, so when we start snapshots for 5.13, that 186 drops back to 1. ___ 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] Use upstream/master for merge-base with fallback to master
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/995#note_546051611 When you create a fork on gitlab, it should automatically keep it in sync with the project that you sync from, which means origin/master doesn't really go out of date any more than os-build would, and a git pull of origin/master should be the same as a pull on upstream/master if you configured kernel-ark as upstream. ___ 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] Use upstream/master for merge-base with fallback to master
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/995#note_545178822 @dzickusrh Our documentation has been wrong for a year. Cloning the project to your own namespace should grab all branches, so origin/master should still just work. origin/ should point to their sync of master. upstream/master should point to the kernel-ark/master branch directly. ___ 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] Use upstream/master for merge-base with fallback to master
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/995#note_544834861 Yes, for the stable branches, we don't care about master. I use $UPSTREAM as a variable for the git --log, upstream is passed as an argument for genspec and defined in Makefile.common, though that should be broken out into an included file just for variables likely to change by branch. I might argue that most people don't care about upstream/master because if you are working off of this tree directly, or if you cloned it through gitlab to your own account, origin/master would be preferred. upstream/master was a relic from when we asked people to actually add a separate remote, which hasn't really been the case in a year. ___ 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 0/0] drm/amdgpu: kernel page size fixes from AMD's drm-next branch
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/991#note_544408706 Looks like this is upstream now, closing this one out. ___ 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 0/0] drm/amdgpu: kernel page size fixes from AMD's drm-next branch
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/991#note_543049010 I have just tagged it with "include in releases". This will bring it into dist-git builds without having to merge the MR, and it can just stay this way until it is properly merged upstream. The 5.11 version of this one for stable Fedora is already merged and should be included in the 5.11.12 builds. ___ 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 0/0] [redhat] New configs in drivers/vdpa
From: Justin Forbes on gitlab.com Merge Request: https://gitlab.com/cki-project/kernel-ark/-/merge_requests/321 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_VDPA: Enable this module to support vDPA device that uses a datapath which complies with virtio specifications with vendor specific control path. Symbol: VDPA [=n] Type : tristate Defined at drivers/vdpa/Kconfig:2 Prompt: vDPA drivers Location: -> Device Drivers --- Cc: "Michael S. Tsirkin" Cc: Jason Wang Cc: rhvirt-patc...@redhat.com ___ 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] spec: Add %bcond_with toolchain_clang option
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/894#note_535065257 That seems comical ___ 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] spec: Add %bcond_with toolchain_clang option
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/894#note_535063843 Ugh, sorry, I thought I did, but that was when I accidentally closed it instead. I failed hard that day. Acked-by: Justin Forbes ___ 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 initial support for centos stream dist-git sync on Makefiles
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/977#note_533479061 GL usernames are much less likely to map to whoami. ___ 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] Export ark infrastructure files
From: Justin Forbes on gitlab.com https://gitlab.com/cki-project/kernel-ark/-/merge_requests/968#note_526661348 I am okay with the added time and failure path, the benefit to the community is strong with this. ___ 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
