linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@kernel.org>
To: Tom Talpey <tom@talpey.com>, Chuck Lever <cel@kernel.org>
Cc: NeilBrown <neilb@suse.de>, Jonathan Corbet <corbet@lwn.net>,
	Chuck Lever <chuck.lever@oracle.com>,
	Olga Kornievskaia <kolga@netapp.com>,
	Dai Ngo <Dai.Ngo@oracle.com>,
	linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] nfsd: add a MODULE_DESCRIPTION
Date: Fri, 21 Jul 2023 06:27:49 -0400	[thread overview]
Message-ID: <b6b4b7888cf0a82ee7332be0f434aa749d029f92.camel@kernel.org> (raw)
In-Reply-To: <f188db26-fb30-4f4b-8bf9-f975bd718605@talpey.com>

On Thu, 2023-07-20 at 20:00 -0400, Tom Talpey wrote:
> Personally I like Jeff's text. There's zero need to overthink this.
> 

It's like this patch was tailor-made for bikeshedding. ;)

Personally, I'm fine with any reasonable string here. My main concern
was just to silence the warning.

> Jul 20, 2023 7:30:34 PM Chuck Lever <cel@kernel.org>:
> 
> > On Fri, Jul 21, 2023 at 08:07:16AM +1000, NeilBrown wrote:
> > > On Thu, 20 Jul 2023, Jeff Layton wrote:
> > > > I got this today from modpost:
> > > > 
> > > >     WARNING: modpost: missing MODULE_DESCRIPTION() in fs/nfsd/nfsd.o
> > > > 
> > > > Add a module description.
> > > > 
> > > > Signed-off-by: Jeff Layton <jlayton@kernel.org>
> > > > ---
> > > > fs/nfsd/nfsctl.c | 1 +
> > > > 1 file changed, 1 insertion(+)
> > > > 
> > > > diff --git a/fs/nfsd/nfsctl.c b/fs/nfsd/nfsctl.c
> > > > index 1b8b1aab9a15..7070969a38b5 100644
> > > > --- a/fs/nfsd/nfsctl.c
> > > > +++ b/fs/nfsd/nfsctl.c
> > > > @@ -1626,6 +1626,7 @@ static void __exit exit_nfsd(void)
> > > > }
> > > > 
> > > > MODULE_AUTHOR("Olaf Kirch <okir@monad.swb.de>");
> > > > +MODULE_DESCRIPTION("The Linux kernel NFS server");
> > > 
> > > Of 9176 MODULE_DESCRIPTIONs in Linux, 21 start with "The ".
> > > Does having that word add anything useful?
> > > Amusingly 129 end with a period.  I wonder what Jon Corbet would prefer
> > > :-)
> > 
> > The Ohio State University has set a bad precedent.
> > 
> > I think we can drop "The".
> > 
> > 
> > > A few tell us what the module does.
> > > "Measures" "Provides"....
> > > Do we want "Implements" ??
> > 
> > I don't find "Implements" to be either conventional or illuminating.
> > 
> > 
> > > 232 start "Driver " and 214 are "Driver for"....
> > > Should we have "Server for" ??
> > > 
> > > 26 start "Linux" ... which seems a bit redundant
> > >   12 contain "for Linux".  67 mention linux in some way.
> > > 28 contain the word "kernel" - also redundant.
> > > Only three (others) mention "Linux kernel"
> > 
> > One of which is the new in-kernel SMB server, interestingly.
> > 
> > I don't think "Linux kernel" or even "in-kernel" is needed here.
> > Both should be obvious from the context.
> > 
> > 
> > > drivers/pcmcia/cs.c:MODULE_DESCRIPTION("Linux Kernel Card Services");
> > > fs/ksmbd/server.c:MODULE_DESCRIPTION("Linux kernel CIFS/SMB SERVER");
> > > fs/orangefs/orangefs-mod.c:MODULE_DESCRIPTION("The Linux Kernel VFS interface to ORANGEFS");
> > > 
> > > hmmm..  192 contain the word "module".  Fortunately none say
> > >   "Linux kernel module for ..."
> > > I would have found that to be a step too far.
> > > 
> > > I'd like to suggest
> > > 
> > >   "Implements Server for NFS - v2, 3, v4.{0,1,2}"
> > > 
> > > But that would require excessive #ifdef magic to get right.
> > 
> > "Network File System server" works for me.
> > 
> > 
> > > A small part of me wants to suggest:
> > > 
> > >    "nfsd"
> > > 
> > > but maybe I'm just in a whimsical mood today.
> > 
> > I'm resisting the urge to add "RFCs 1813, 7530, 8881, et al."
> > Whimsy, indeed. ;-)
> > 
> > 
> > > NeilBrown
> > > 
> > > 
> > > > MODULE_LICENSE("GPL");
> > > > module_init(init_nfsd)
> > > > module_exit(exit_nfsd)
> > > > -- 
> > > > 2.41.0
> > > > 
> > > > 
> > > 

-- 
Jeff Layton <jlayton@kernel.org>

      reply	other threads:[~2023-07-21 10:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-20 13:34 [PATCH] nfsd: add a MODULE_DESCRIPTION Jeff Layton
2023-07-20 14:23 ` Chuck Lever III
2023-07-20 22:07 ` NeilBrown
2023-07-20 23:29   ` Chuck Lever
2023-07-21  0:00     ` Tom Talpey
2023-07-21 10:27       ` Jeff Layton [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=b6b4b7888cf0a82ee7332be0f434aa749d029f92.camel@kernel.org \
    --to=jlayton@kernel.org \
    --cc=Dai.Ngo@oracle.com \
    --cc=cel@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=corbet@lwn.net \
    --cc=kolga@netapp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=tom@talpey.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;
as well as URLs for NNTP newsgroup(s).