From: Jeff Johnson <quic_jjohnson@quicinc.com>
To: Arnd Bergmann <arnd@kernel.org>,
Herbert Xu <herbert@gondor.apana.org.au>
Cc: <kernel-janitors@vger.kernel.org>,
Nicholas Piggin <npiggin@gmail.com>,
<linux-kernel@vger.kernel.org>, Danny Tsen <dtsen@linux.ibm.com>,
Christophe Leroy <christophe.leroy@csgroup.eu>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Naveen N. Rao" <naveen.n.rao@linux.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
<linuxppc-dev@lists.ozlabs.org>,
"David S . Miller" <davem@davemloft.net>,
<linux-crypto@vger.kernel.org>
Subject: Re: [PATCH] crypto: ppc/curve25519 - add missing MODULE_DESCRIPTION() macro
Date: Fri, 2 Aug 2024 09:13:26 -0700 [thread overview]
Message-ID: <2a1f5b08-5c5e-4c16-89a9-69eb920d1f44@quicinc.com> (raw)
In-Reply-To: <6fdd8f30-4df1-447d-9156-5d2314239e99@app.fastmail.com>
On 8/2/2024 8:16 AM, Arnd Bergmann wrote:
> On Fri, Aug 2, 2024, at 16:27, Jeff Johnson wrote:
>> On 8/2/2024 6:15 AM, Herbert Xu wrote:
>>> On Thu, Jul 18, 2024 at 06:14:18PM -0700, Jeff Johnson wrote:
>>>> Since commit 1fffe7a34c89 ("script: modpost: emit a warning when the
>>>> description is missing"), a module without a MODULE_DESCRIPTION() will
>>>> result in a warning with make W=1. The following warning is being
>>>> observed when building ppc64le with CRYPTO_CURVE25519_PPC64=m:
>>>>
>>>> WARNING: modpost: missing MODULE_DESCRIPTION() in arch/powerpc/crypto/curve25519-ppc64le.o
>>>>
>>>> Add the missing invocation of the MODULE_DESCRIPTION() macro.
>>>>
>>>> Signed-off-by: Jeff Johnson <quic_jjohnson@quicinc.com>
>>>> ---
>>>> arch/powerpc/crypto/curve25519-ppc64le-core.c | 1 +
>>>> 1 file changed, 1 insertion(+)
>>>
>>> Patch applied. Thanks.
>>
>> Great, that was the last of my MODULE_DESCRIPTION patches!!!
>>
>> There are a few more instances of the warning that Arnd has patches for,
>> covering issues that appear in randconfigs that I didn't test.
>
> Are all of your patches in linux-next now, or is there a another
> git tree that has them all?
>
> I can send the ones I have left, but I want to avoid duplication.
>
> Arnd
When this one lands they'll all be in linux-next
prev parent reply other threads:[~2024-08-02 16:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-19 1:14 Jeff Johnson
2024-08-02 13:15 ` Herbert Xu
2024-08-02 14:27 ` Jeff Johnson
2024-08-02 15:10 ` Dan Carpenter
2024-08-02 15:16 ` Arnd Bergmann
2024-08-02 16:13 ` 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=2a1f5b08-5c5e-4c16-89a9-69eb920d1f44@quicinc.com \
--to=quic_jjohnson@quicinc.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@kernel.org \
--cc=christophe.leroy@csgroup.eu \
--cc=davem@davemloft.net \
--cc=dtsen@linux.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=herbert@gondor.apana.org.au \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=naveen.n.rao@linux.ibm.com \
--cc=npiggin@gmail.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
all inboxes | Powered by JetHome®