All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Johnson <quic_jjohnson@quicinc.com>
To: Joel Becker <jlbec@evilplan.org>, Christoph Hellwig <hch@lst.de>
Cc: <linux-kernel@vger.kernel.org>, <kernel-janitors@vger.kernel.org>
Subject: Re: [PATCH] samples: configfs: add missing MODULE_DESCRIPTION() macro
Date: Thu, 20 Jun 2024 09:46:48 -0700	[thread overview]
Message-ID: <1d5dc2bb-773c-4877-9660-fff5517c2df3@quicinc.com> (raw)
In-Reply-To: <20240601-md-samples-configfs-v1-1-83ef2d3c0088@quicinc.com>

On 6/1/2024 5:12 PM, Jeff Johnson wrote:
> make allmodconfig && make W=1 C=1 reports:
> WARNING: modpost: missing MODULE_DESCRIPTION() in samples/configfs/configfs_sample.o
> 
> Add the missing invocation of the MODULE_DESCRIPTION() macro.
> 
> Signed-off-by: Jeff Johnson <quic_jjohnson@quicinc.com>
> ---
>  samples/configfs/configfs_sample.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/samples/configfs/configfs_sample.c b/samples/configfs/configfs_sample.c
> index 37a657b25d58..fd5d163828c5 100644
> --- a/samples/configfs/configfs_sample.c
> +++ b/samples/configfs/configfs_sample.c
> @@ -364,4 +364,5 @@ static void __exit configfs_example_exit(void)
>  
>  module_init(configfs_example_init);
>  module_exit(configfs_example_exit);
> +MODULE_DESCRIPTION("Sample configfs module");
>  MODULE_LICENSE("GPL");
> 
> ---
> base-commit: b050496579632f86ee1ef7e7501906db579f3457
> change-id: 20240601-md-samples-configfs-946b278a9d47
> 

I don't see this in linux-next yet so following up to see if anything else is
needed to get this merged.

  reply	other threads:[~2024-06-20 16:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-02  0:12 [PATCH] samples: configfs: add missing MODULE_DESCRIPTION() macro Jeff Johnson
2024-06-20 16:46 ` Jeff Johnson [this message]
2024-07-09 22:20   ` Jeff Johnson
2024-07-10  6:17     ` Christoph Hellwig
2024-07-10 12:59     ` Greg Kroah-Hartman

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=1d5dc2bb-773c-4877-9660-fff5517c2df3@quicinc.com \
    --to=quic_jjohnson@quicinc.com \
    --cc=hch@lst.de \
    --cc=jlbec@evilplan.org \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.