From: Thorsten Leemhuis on
gitlab.com
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/2943#note_1843...
I did a test build with today's linux-next[1] to check how it would handled
three new modules I recently had to add to mod-internal respectively
redhat/fedora_files/filter-modules.sh.fedora due to changes in next.
Everything went smoothly for the new kunit test module net_test[2].
But ptn36502 now ended up in modules-core and tracked aux-bridge into it, too.
That does not seem ideal. I mean: sure, it ensures things will work, but
unless I'm missing something this means that modules-core will slowly grow
over time with modules that better should be somewhere else -- unless somebody
occasionally (e.g. after every merge window?) sits down and checks which
modules ended up where (which I guess might be something that easily gets
forgotten).
If that's what we want that's fine with me, just mentioning it because I
noticed it.
/me prays he did not do something stupid during his tests
[1] If anyone cares about the logs:
* my regular -next build from today
https://download.copr.fedorainfracloud.org/results/@kernel-
vanilla/next/fedora-40-x86_64/07252462-next-next-all/builder-live.log.gz
* the one with the two commits from this MR:
https://download.copr.fedorainfra
cloud.org/results/thl/testing/fedora-40-x86_64/07253400-kernel/builder-
live.log.gz
[2]
https://gitlab.com/knurd42/linux/-/commit/c4a33ee7bf712b18ca5ef382ad0d8e88
9a9fe20f
[3]
https://gitlab.com/knurd42/linux/-/commit/7e16c5ed523869999b521f1bfae5539f
ca67f7f5