From: "Vincenzo Palazzo" <vincenzopalazzodev@gmail.com>
To: "Masahiro Yamada" <masahiroy@kernel.org>
Cc: <linux-kbuild@vger.kernel.org>, "Roland Kletzing" <devzero@web.de>
Subject: Re: [PATCH v1 1/1] script: modpost: emit warning when description is missing
Date: Wed, 08 Mar 2023 09:46:57 +0100 [thread overview]
Message-ID: <CR0VD9KDRYVJ.2N3C1FVZA1DFR@vincent-arch> (raw)
In-Reply-To: <CAK7LNAS598SxdLDoVLFdBtEynzhFZHD0Z1cHeuDHLaJJvL6b0w@mail.gmail.com>
On Tue Mar 7, 2023 at 3:34 AM CET, Masahiro Yamada wrote:
> On Tue, Mar 7, 2023 at 2:42 AM Vincenzo Palazzo
> <vincenzopalazzodev@gmail.com> wrote:
> >
> > Emit a warning when the mod description is missed.
> >
> > Reported-by: Roland Kletzing <devzero@web.de>
> > Link: https://bugzilla.kernel.org/show_bug.cgi?id=10770
> > Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
> > ---
> > scripts/mod/modpost.c | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> > diff --git a/scripts/mod/modpost.c b/scripts/mod/modpost.c
> > index efff8078e395..c63156ba4e5e 100644
> > --- a/scripts/mod/modpost.c
> > +++ b/scripts/mod/modpost.c
> > @@ -1824,6 +1824,9 @@ static void read_symbols(const char *modname)
> > }
> > }
> >
> > + if (!get_modinfo(&info, "description"))
> > + warn("missing MODULE_DESCRIPTION() in %s\n", modname);
> > +
> > for (sym = info.symtab_start; sym < info.symtab_stop; sym++) {
> > symname = remove_dot(info.strtab + sym->st_name);
> >
> > --
> > 2.39.2
> >
>
>
> Linus requires a clean build log these days.
> This patch would sprinkle warning messages,
> and I am sure it will result in a rejection.
I see, thanks to let me know!
> The best we can do would print the warnings
> only when W=1.
I will do it in a v2 later today, thanks!
Cheers!
Vincent.
prev parent reply other threads:[~2023-03-08 8:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-06 17:41 [PATCH v1 1/1] script: modpost: emit warning when description is missing Vincenzo Palazzo
2023-03-07 2:34 ` Masahiro Yamada
2023-03-08 8:46 ` Vincenzo Palazzo [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=CR0VD9KDRYVJ.2N3C1FVZA1DFR@vincent-arch \
--to=vincenzopalazzodev@gmail.com \
--cc=devzero@web.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=masahiroy@kernel.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;
as well as URLs for NNTP newsgroup(s).