All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: David Miller <davem@davemloft.net>,
	neilb@cse.unsw.edu.au, trond.myklebust@fys.uio.no,
	linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net,
	netdev@vger.kernel.org
Subject: Re: [RFC: 2.6 patch] net/sunrpc/: possible cleanups
Date: Sun, 2 Oct 2005 16:41:13 +0200	[thread overview]
Message-ID: <20051002144113.GM4212@stusta.de> (raw)
In-Reply-To: <20051001164019.GB8633@mipter.zuzino.mipt.ru>

On Sat, Oct 01, 2005 at 08:40:19PM +0400, Alexey Dobriyan wrote:
> On Sat, Oct 01, 2005 at 04:20:41PM +0200, Adrian Bunk wrote:
> > -/* Just increments the mechanism's reference count and returns its input: */
> > -struct gss_api_mech * gss_mech_get(struct gss_api_mech *);
> > -
> 
> > -struct gss_api_mech *
> > +static struct gss_api_mech *
> >  gss_mech_get(struct gss_api_mech *gm)
> 
> Comment is lost.


The comment made sense for the prototype at the header, but the function 
now has only one caller in the file where it's defined.


If someone needs a comment to figure out what a function whose complete 
contents is

static struct gss_api_mech *
gss_mech_get(struct gss_api_mech *gm)
{
        __module_get(gm->gm_owner);
        return gm;
}

does, the problem is not a missing comment.


cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

  reply	other threads:[~2005-10-02 14:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-01 14:20 [RFC: 2.6 patch] net/sunrpc/: possible cleanups Adrian Bunk
2005-10-01 16:40 ` Alexey Dobriyan
2005-10-02 14:41   ` Adrian Bunk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-05-30 20:56 Adrian Bunk
2005-05-06 23:13 Adrian Bunk

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=20051002144113.GM4212@stusta.de \
    --to=bunk@stusta.de \
    --cc=adobriyan@gmail.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@cse.unsw.edu.au \
    --cc=netdev@vger.kernel.org \
    --cc=nfs@lists.sourceforge.net \
    --cc=trond.myklebust@fys.uio.no \
    /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.