From: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
To: Masahiro Yamada <masahiroy@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Nicolas Schier <nicolas@fjasle.eu>,
Arnd Bergmann <arnd@kernel.org>
Cc: linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] script: modpost: require a MODULE_DESCRIPTION()
Date: Tue, 11 Mar 2025 12:54:08 -0700 [thread overview]
Message-ID: <ffa8d0d4-269a-4bae-9dea-adc221819b17@oss.qualcomm.com> (raw)
In-Reply-To: <20250311-moddesc-error-v1-1-79adedf48d0e@oss.qualcomm.com>
On 3/11/2025 12:49 PM, Jeff Johnson wrote:
> Since commit 1fffe7a34c89 ("script: modpost: emit a warning when the
> description is missing"), a module without a MODULE_DESCRIPTION() has
> resulted in a warning with make W=1. Since that time, all known
> instances of this issue have been fixed. Therefore, now make it an
> error if a MODULE_DESCRIPTION() is not present.
>
> Signed-off-by: Jeff Johnson <jeff.johnson@oss.qualcomm.com>
> ---
> did my treewide cleanup for v6.11, Arnd had a few more stragglers that
> he was going to fix. I hope that by posting, some of the 0-day bots
> will pick it up and hopefully provide some feedback.
>
> Note: I'm not really sure if *all* of these have been fixed. After I
guess I should have done another 'b4 send --reflect' after I modified my cover
letter <blush>
Pretend this line is immediately after the cut
next prev parent reply other threads:[~2025-03-11 19:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-11 19:49 Jeff Johnson
2025-03-11 19:54 ` Jeff Johnson [this message]
2025-03-13 0:34 ` Masahiro Yamada
2025-03-22 15:45 ` Masahiro Yamada
2025-04-06 15:23 ` Guenter Roeck
2025-04-06 15:59 ` Guenter Roeck
2025-04-06 16:06 ` Arnd Bergmann
2025-04-06 17:06 ` Guenter Roeck
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=ffa8d0d4-269a-4bae-9dea-adc221819b17@oss.qualcomm.com \
--to=jeff.johnson@oss.qualcomm.com \
--cc=arnd@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=nathan@kernel.org \
--cc=nicolas@fjasle.eu \
/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
all inboxes | Powered by JetHome®