From: Michal Simek <michal.simek@amd.com>
To: Jeff Johnson <quic_jjohnson@quicinc.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
"David S. Miller" <davem@davemloft.net>
Cc: linux-crypto@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] crypto: xilinx - add missing MODULE_DESCRIPTION() macro
Date: Mon, 3 Jun 2024 08:52:54 +0200 [thread overview]
Message-ID: <610f8ca3-c2a5-4788-af7f-3fbdd67d0f6b@amd.com> (raw)
In-Reply-To: <20240602-md-zynqmp-aes-gcm-v1-1-e431cb9b558e@quicinc.com>
On 6/3/24 01:17, Jeff Johnson wrote:
> make allmodconfig && make W=1 C=1 reports:
> WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/crypto/xilinx/zynqmp-aes-gcm.o
>
> Add the missing invocation of the MODULE_DESCRIPTION() macro.
>
> Signed-off-by: Jeff Johnson <quic_jjohnson@quicinc.com>
> ---
> drivers/crypto/xilinx/zynqmp-aes-gcm.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/crypto/xilinx/zynqmp-aes-gcm.c b/drivers/crypto/xilinx/zynqmp-aes-gcm.c
> index e61405718840..7f0ec6887a39 100644
> --- a/drivers/crypto/xilinx/zynqmp-aes-gcm.c
> +++ b/drivers/crypto/xilinx/zynqmp-aes-gcm.c
> @@ -446,4 +446,5 @@ static struct platform_driver zynqmp_aes_driver = {
> };
>
> module_platform_driver(zynqmp_aes_driver);
> +MODULE_DESCRIPTION("Xilinx ZynqMP AES Driver");
> MODULE_LICENSE("GPL");
>
> ---
> base-commit: a693b9c95abd4947c2d06e05733de5d470ab6586
> change-id: 20240602-md-zynqmp-aes-gcm-c46078273370
>
Reviewed-by: Michal Simek <michal.simek@amd.com>
Thanks,
Michal
next prev parent reply other threads:[~2024-06-03 6:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-02 23:17 [PATCH] crypto: xilinx - add missing MODULE_DESCRIPTION() macro Jeff Johnson
2024-06-03 6:52 ` Michal Simek [this message]
2024-06-07 12:01 ` Herbert Xu
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=610f8ca3-c2a5-4788-af7f-3fbdd67d0f6b@amd.com \
--to=michal.simek@amd.com \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.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