The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Takashi Sakamoto <o-takashi@sakamocchi.jp>
To: Jeff Johnson <quic_jjohnson@quicinc.com>
Cc: linux1394-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] firewire: add missing MODULE_DESCRIPTION() to test modules
Date: Fri, 24 May 2024 12:40:19 +0900	[thread overview]
Message-ID: <20240524034019.GA276112@workstation.local> (raw)
In-Reply-To: <20240523-md-firewire-uapi-test-v1-1-6be5adcc3aed@quicinc.com>

Hi,

Thank you for your sending the patch.

On Thu, May 23, 2024 at 04:22:34PM -0700, Jeff Johnson wrote:
> Fix the 'make W=1' warnings:
> WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/firewire/uapi-test.o
> WARNING: modpost: missing MODULE_DESCRIPTION() in drivers/firewire/packet-serdes-test.o
> 
> Signed-off-by: Jeff Johnson <quic_jjohnson@quicinc.com>
> ---
>  drivers/firewire/packet-serdes-test.c | 1 +
>  drivers/firewire/uapi-test.c          | 1 +
>  2 files changed, 2 insertions(+)
> 
> diff --git a/drivers/firewire/packet-serdes-test.c b/drivers/firewire/packet-serdes-test.c
> index f93c966e794d..e83b1fece780 100644
> --- a/drivers/firewire/packet-serdes-test.c
> +++ b/drivers/firewire/packet-serdes-test.c
> @@ -579,4 +579,5 @@ static struct kunit_suite packet_serdes_test_suite = {
>  };
>  kunit_test_suite(packet_serdes_test_suite);
>  
> +MODULE_DESCRIPTION("FireWire packet serialization/deserialization unit test suite");
>  MODULE_LICENSE("GPL");
> diff --git a/drivers/firewire/uapi-test.c b/drivers/firewire/uapi-test.c
> index 2fcbede4fab1..bc3f10a2e516 100644
> --- a/drivers/firewire/uapi-test.c
> +++ b/drivers/firewire/uapi-test.c
> @@ -86,4 +86,5 @@ static struct kunit_suite structure_layout_test_suite = {
>  };
>  kunit_test_suite(structure_layout_test_suite);
>  
> +MODULE_DESCRIPTION("FireWire UAPI unit test suite");
>  MODULE_LICENSE("GPL");
> 
> ---
> base-commit: 5c4069234f68372e80e4edfcce260e81fd9da007
> change-id: 20240523-md-firewire-uapi-test-08fb0a9e18de
 
In my opinion, it is not so urgent. I would like to postpone sending it
to mainline until closing the current merge window.


Thanks

Takashi Sakamoto

  reply	other threads:[~2024-05-24  3:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-23 23:22 [PATCH] firewire: add missing MODULE_DESCRIPTION() to test modules Jeff Johnson
2024-05-24  3:40 ` Takashi Sakamoto [this message]
2024-05-26 22:38 ` Takashi Sakamoto

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=20240524034019.GA276112@workstation.local \
    --to=o-takashi@sakamocchi.jp \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux1394-devel@lists.sourceforge.net \
    --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