From: Petr Mladek <pmladek@suse.com>
To: Jeff Johnson <quic_jjohnson@quicinc.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Steven Rostedt <rostedt@goodmis.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Sergey Senozhatsky <senozhatsky@chromium.org>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] vsprintf: add missing MODULE_DESCRIPTION() macro
Date: Wed, 24 Jul 2024 16:02:08 +0200 [thread overview]
Message-ID: <ZqEJYJScuEJpo778@pathway.suse.cz> (raw)
In-Reply-To: <9614c130-d90a-4023-87fd-0b3b12516021@quicinc.com>
On Tue 2024-07-23 11:53:34, Jeff Johnson wrote:
> On 6/12/2024 4:31 AM, Petr Mladek wrote:
> > On Fri 2024-05-31 19:42:25, Jeff Johnson wrote:
> >> make allmodconfig && make W=1 C=1 reports:
> >> WARNING: modpost: missing MODULE_DESCRIPTION() in lib/test_printf.o
> >> WARNING: modpost: missing MODULE_DESCRIPTION() in lib/test_scanf.o
> >>
> >> Add the missing invocations of the MODULE_DESCRIPTION() macro.
> >>
> >> Signed-off-by: Jeff Johnson <quic_jjohnson@quicinc.com>
> >
> > JFYI, the patch has been comitted into printk/linux.git,
> > branch for-6.11.
> >
> > Best Regards,
> > Petr
>
> Hi Petr,
> I see this landed in linux-next, but is not currently in Linus' tree for 6.11.
> Will you be able to have this pulled during the merge window?
> I'm trying to eradicate all of these warnings before 6.11 rc-final.
The pull request is still being discussed, see
https://lore.kernel.org/r/CAHk-=whU_woFnFN-3Jv2hNCmwLg_fkrT42AWwxm-=Ha5BmNX4w@mail.gmail.com
If the printk rework part is not acceptable then I'll send these
trivial changes separately.
Best Regards,
Petr
PS: I have sent the pull request late because I have had vacation
previous two weeks.
next prev parent reply other threads:[~2024-07-24 14:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-01 2:42 Jeff Johnson
2024-06-12 11:29 ` Petr Mladek
2024-06-12 11:31 ` Petr Mladek
2024-07-23 18:53 ` Jeff Johnson
2024-07-24 14:02 ` Petr Mladek [this message]
2024-07-24 14:32 ` Jeff Johnson
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=ZqEJYJScuEJpo778@pathway.suse.cz \
--to=pmladek@suse.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=quic_jjohnson@quicinc.com \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.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
all inboxes | Powered by JetHome®