From: Jeff Johnson <quic_jjohnson@quicinc.com>
To: Alexandre Belloni <alexandre.belloni@bootlin.com>,
Jiaxun Yang <jiaxun.yang@flygoat.com>
Cc: <linux-rtc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<kernel-janitors@vger.kernel.org>
Subject: Re: [PATCH] rtc: add missing MODULE_DESCRIPTION() macro
Date: Wed, 26 Jun 2024 09:10:26 -0700 [thread overview]
Message-ID: <33171087-01da-445e-8125-e563b9abb471@quicinc.com> (raw)
In-Reply-To: <20240608-md-drivers-rtc-v1-1-5f44222adfae@quicinc.com>
On 6/8/2024 10:52 PM, Jeff Johnson wrote:
> On x86, make allmodconfig && make W=1 C=1 reports:
> WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/rtc/lib_test.o
> WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/rtc/rtc-goldfish.o
> WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/rtc/rtc-omap.o
> WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/rtc/rtc-rc5t583.o
> WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/rtc/rtc-tps65910.o
> WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/rtc/rtc-twl.o
>
> Add the missing invocation of the MODULE_DESCRIPTION() macro to all
> files which have a MODULE_LICENSE(). This includes rtc-mpc5121.c,
> which does not produce a warning with the x86 allmodconfig since it is
> not built for x86, but it may cause this warning with Freescale PPC
> configurations.
>
> Signed-off-by: Jeff Johnson <quic_jjohnson@quicinc.com>
Following up to see if anything else is needed from me. Hoping to see this in
linux-next so I can remove it from my tracking spreadsheet :)
/jeff
next prev parent reply other threads:[~2024-06-26 16:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-09 5:52 [PATCH] rtc: add missing MODULE_DESCRIPTION() macro Jeff Johnson
2024-06-26 16:10 ` Jeff Johnson [this message]
2024-06-27 22:35 ` Alexandre Belloni
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=33171087-01da-445e-8125-e563b9abb471@quicinc.com \
--to=quic_jjohnson@quicinc.com \
--cc=alexandre.belloni@bootlin.com \
--cc=jiaxun.yang@flygoat.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.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