From: Vinod Koul <vkoul@kernel.org>
To: Jeff Johnson <quic_jjohnson@quicinc.com>
Cc: Sinan Kaya <okaya@kernel.org>,
kernel@quicinc.com, linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
Greg KH <gregkh@linuxfoundation.org>
Subject: Re: [PATCH] dmaengine: qcom: add missing MODULE_DESCRIPTION() macros
Date: Thu, 25 Jul 2024 11:21:06 +0530 [thread overview]
Message-ID: <ZqHnynG0pFPryn3E@matsya> (raw)
In-Reply-To: <36f5502c-a07f-4809-aa24-7f996afc0a88@quicinc.com>
On 23-07-24, 11:36, Jeff Johnson wrote:
> On 6/7/2024 10:47 AM, Vinod Koul wrote:
> >
> > On Mon, 03 Jun 2024 10:06:42 -0700, Jeff Johnson wrote:
> >> make allmodconfig && make W=1 C=1 reports:
> >> WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/dma/qcom/hdma_mgmt.o
> >> WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/dma/qcom/hdma.o
> >>
> >> Add the missing invocations of the MODULE_DESCRIPTION() macro, using
> >> the descriptions from the associated Kconfig items.
> >>
> >> [...]
> >
> > Applied, thanks!
> >
> > [1/1] dmaengine: qcom: add missing MODULE_DESCRIPTION() macros
> > commit: 8e9d83d7228f663ef340ebb339eaffc677277bd4
> >
>
> Hi Vinod,
> 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.
We are still in merge window!
FWIW, this is in linus's tree now
--
~Vinod
prev parent reply other threads:[~2024-07-25 5:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 17:06 [PATCH] dmaengine: qcom: add missing MODULE_DESCRIPTION() macros Jeff Johnson
2024-06-03 17:13 ` Jeffrey Hugo
2024-06-07 17:47 ` Vinod Koul
2024-07-23 18:36 ` Jeff Johnson
2024-07-25 5:51 ` Vinod Koul [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=ZqHnynG0pFPryn3E@matsya \
--to=vkoul@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.org \
--cc=kernel@quicinc.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=okaya@kernel.org \
--cc=quic_jjohnson@quicinc.com \
/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).