From: Vlastimil Babka <vbabka@suse.cz>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Damian Tometzki <damian@riscv-rocks.de>,
Masahiro Yamada <masahiroy@kernel.org>,
Jeff Johnson <jeff.johnson@oss.qualcomm.com>
Cc: Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Hyeonggon Yoo <42.hyeyoo@gmail.com>
Subject: Re: [GIT PULL] Kbuild updates for v6.15-rc1
Date: Mon, 7 Apr 2025 10:34:29 +0200 [thread overview]
Message-ID: <bb3d1391-d155-4e83-9103-818cd1a82c66@suse.cz> (raw)
In-Reply-To: <CAHk-=wh-k04MsoEC0SGKff2Snm6bBF_e+0pHOKwaWv4umZ_SnQ@mail.gmail.com>
On 4/6/25 18:50, Linus Torvalds wrote:
> On Sat, 5 Apr 2025 at 22:43, Damian Tometzki <damian@riscv-rocks.de> wrote:
>>
>> i got the following error after this pull request.
>>
>> MODPOST Module.symvers
>> ERROR: modpost: missing MODULE_DESCRIPTION() in lib/tests/slub_kunit.o
>> make[3]: *** [/home/damian/kernel/linux/scripts/Makefile.modpost:147: Module.symvers] Error 1
>> make[2]: *** [/home/damian/kernel/linux/Makefile:1956: modpost] Error 2
>> make[1]: *** [/home/damian/kernel/linux/Makefile:248: __sub-make] Error 2
>> make[1]: Leaving directory '/home/damian/kernel/build'
>> make: *** [Makefile:248: __sub-make] Error 2
>
> I think I'll downgrade the error() to a warn() again, and make
> SLUB_TINY depend on !COMPILE_TEST.
Ack, thanks.
> And I'm not even convinced we should require module descriptions for
> silly test modules, but whatever.
>
> We'll see if something else pops up, but making the lack of a module
> description a fatal error was clearly not right as-is.
>
> Linus
>
> [*] In fact, I'm not convinced SLUB_TINYT ever makes sense at all, but
> that may be too unrelated to this to worry about.
Back when it was introduced, it allowed removing SLAB without breaking some
particular small systems, so I'd say it was worth it :) But since the
savings are mostly coming from not allocating for performance rather than
the disabled code size, we could probably easily turn it to a non-intrusive
boot option and not regress anyone.
prev parent reply other threads:[~2025-04-07 8:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-05 22:04 [GIT PULL] Kbuild updates for v6.15-rc1 Masahiro Yamada
2025-04-05 22:50 ` pr-tracker-bot
2025-04-06 5:43 ` Damian Tometzki
2025-04-06 16:50 ` Linus Torvalds
2025-04-06 20:41 ` Stephen Rothwell
2025-04-07 8:34 ` Vlastimil Babka [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bb3d1391-d155-4e83-9103-818cd1a82c66@suse.cz \
--to=vbabka@suse.cz \
--cc=42.hyeyoo@gmail.com \
--cc=damian@riscv-rocks.de \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox