From: Jeff Johnson <quic_jjohnson@quicinc.com>
To: Mathieu Poirier <mathieu.poirier@linaro.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
<linux-remoteproc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <kernel-janitors@vger.kernel.org>
Subject: Re: [PATCH] rpmsg: char: add missing MODULE_DESCRIPTION() macro
Date: Tue, 23 Jul 2024 11:42:03 -0700 [thread overview]
Message-ID: <bc1296e1-9f0f-477b-96d2-1a68f3347e33@quicinc.com> (raw)
In-Reply-To: <Zmc3H6PN8WPpgXNN@p14s>
On 6/10/2024 10:25 AM, Mathieu Poirier wrote:
> On Tue, Jun 04, 2024 at 06:53:44PM -0700, Jeff Johnson wrote:
>> make allmodconfig && make W=1 C=1 reports:
>> WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/rpmsg/rpmsg_char.o
>>
>> Add the missing invocation of the MODULE_DESCRIPTION() macro.
>>
>> Signed-off-by: Jeff Johnson <quic_jjohnson@quicinc.com>
>> ---
>> drivers/rpmsg/rpmsg_char.c | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/rpmsg/rpmsg_char.c b/drivers/rpmsg/rpmsg_char.c
>> index d7a342510902..73b9fa113b34 100644
>> --- a/drivers/rpmsg/rpmsg_char.c
>> +++ b/drivers/rpmsg/rpmsg_char.c
>> @@ -566,4 +566,5 @@ static void rpmsg_chrdev_exit(void)
>> module_exit(rpmsg_chrdev_exit);
>>
>> MODULE_ALIAS("rpmsg:rpmsg_chrdev");
>> +MODULE_DESCRIPTION("RPMSG device interface");
>> MODULE_LICENSE("GPL v2");
>>
>
> Applied
>
> Thanks,
> Mathieu
Hi,
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.
Thanks!
/jeff
prev parent reply other threads:[~2024-07-23 18:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 1:53 [PATCH] rpmsg: char: add missing MODULE_DESCRIPTION() macro Jeff Johnson
2024-06-10 17:25 ` Mathieu Poirier
2024-07-23 18:42 ` Jeff Johnson [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=bc1296e1-9f0f-477b-96d2-1a68f3347e33@quicinc.com \
--to=quic_jjohnson@quicinc.com \
--cc=andersson@kernel.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.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 read-only IMAP folder(s) and NNTP newsgroup(s).