From: Dipen Patel <dipenp@nvidia.com>
To: Jeff Johnson <quic_jjohnson@quicinc.com>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>
Cc: timestamp@lists.linux.dev, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] hte: tegra-194: add missing MODULE_DESCRIPTION() macro
Date: Tue, 11 Jun 2024 09:24:48 -0700 [thread overview]
Message-ID: <92059885-858c-4a07-9e2d-cda10c6c38bf@nvidia.com> (raw)
In-Reply-To: <20240603-md-hte-tegra194-test-v1-1-83c959a0afdd@quicinc.com>
On 6/3/24 4:22 PM, Jeff Johnson wrote:
> make allmodconfig && make W=1 C=1 reports:
> WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/hte/hte-tegra194-test.o
>
> Add the missing invocation of the MODULE_DESCRIPTION() macro.
>
> Signed-off-by: Jeff Johnson <quic_jjohnson@quicinc.com>
> ---
> drivers/hte/hte-tegra194-test.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/hte/hte-tegra194-test.c b/drivers/hte/hte-tegra194-test.c
> index 8ee038ccf601..df631b5100d2 100644
> --- a/drivers/hte/hte-tegra194-test.c
> +++ b/drivers/hte/hte-tegra194-test.c
> @@ -235,4 +235,5 @@ static struct platform_driver tegra_hte_test_driver = {
> module_platform_driver(tegra_hte_test_driver);
>
> MODULE_AUTHOR("Dipen Patel <dipenp@nvidia.com>");
> +MODULE_DESCRIPTION("NVIDIA Tegra HTE (Hardware Timestamping Engine) test driver");
> MODULE_LICENSE("GPL");
>
> ---
> base-commit: a693b9c95abd4947c2d06e05733de5d470ab6586
> change-id: 20240603-md-hte-tegra194-test-668212d1420f
>
Acked-by: Dipen Patel <dipenp@nvidia.com>
next prev parent reply other threads:[~2024-06-11 16:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 23:22 Jeff Johnson
2024-06-11 16:24 ` Dipen Patel [this message]
2024-06-23 17:53 ` Jeff Johnson
2024-06-25 21:05 ` Dipen Patel
2024-06-25 22:30 ` Jeff Johnson
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=92059885-858c-4a07-9e2d-cda10c6c38bf@nvidia.com \
--to=dipenp@nvidia.com \
--cc=jonathanh@nvidia.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=quic_jjohnson@quicinc.com \
--cc=thierry.reding@gmail.com \
--cc=timestamp@lists.linux.dev \
/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®