From: Jeff Johnson <quic_jjohnson@quicinc.com>
To: Abel Vesa <abel.vesa@linaro.org>, Abel Vesa <abelvesa@kernel.org>,
Peng Fan <peng.fan@nxp.com>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Greg KH <gregkh@linuxfoundation.org>
Cc: <linux-clk@vger.kernel.org>, <imx@lists.linux.dev>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <kernel-janitors@vger.kernel.org>
Subject: Re: [PATCH] clk: imx: add missing MODULE_DESCRIPTION() macros
Date: Tue, 23 Jul 2024 11:27:05 -0700 [thread overview]
Message-ID: <13e24ef9-f2e5-478b-8854-0e33a2c497b3@quicinc.com> (raw)
In-Reply-To: <171923430571.3352368.17603224359381270285.b4-ty@linaro.org>
On 6/24/2024 6:05 AM, Abel Vesa wrote:
>
> On Sun, 02 Jun 2024 08:59:17 -0700, Jeff Johnson wrote:
>> make allmodconfig && make W=1 C=1 reports:
>> WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/clk/imx/mxc-clk.o
>> WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/clk/imx/clk-imxrt1050.o
>>
>> Add the missing invocations of the MODULE_DESCRIPTION() macro.
>>
>>
>> [...]
>
> Applied, thanks!
>
> [1/1] clk: imx: add missing MODULE_DESCRIPTION() macros
> commit: 1919d77a9591aa692c8de11540ffc0e7d18eabb4
Hi Abel,
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:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-02 15:59 Jeff Johnson
2024-06-23 17:34 ` Jeff Johnson
2024-06-24 9:05 ` Abel Vesa
2024-06-24 13:05 ` Abel Vesa
2024-07-23 18:27 ` 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=13e24ef9-f2e5-478b-8854-0e33a2c497b3@quicinc.com \
--to=quic_jjohnson@quicinc.com \
--cc=abel.vesa@linaro.org \
--cc=abelvesa@kernel.org \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=imx@lists.linux.dev \
--cc=kernel-janitors@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=peng.fan@nxp.com \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@kernel.org \
--cc=shawnguo@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
all inboxes | Powered by JetHome®