Linux NFS development
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Andrew Morton <akpm@osdl.org>, NeilBrown <neilb@suse.de>,
	linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net
Subject: Re: [NFS] [-mm patch] fs/nfsd/nfs4state.c: make a struct static
Date: Tue, 4 Apr 2006 19:29:13 +0200	[thread overview]
Message-ID: <20060404172913.GT6529@stusta.de> (raw)
In-Reply-To: <20060404165045.GD17709@fieldses.org>

On Tue, Apr 04, 2006 at 12:50:45PM -0400, J. Bruce Fields wrote:
> On Tue, Apr 04, 2006 at 06:30:10PM +0200, Adrian Bunk wrote:
> > On Tue, Apr 04, 2006 at 01:45:04AM -0700, Andrew Morton wrote:
> > >...
> > > Changes since 2.6.16-mm2:
> > >...
> > > +knfsd-locks-flag-nfsv4-owned-locks.patch
> > >...
> > >  knfsd updates.
> > >...
> > 
> > This patch makes the needlessly global struct nfsd_posix_mng_ops static.
> 
> Whoops, thanks, looks good.
> 
> Do you have a script to look for patches that add non-statics?

I diff the output of "make namespacecheck" with the output from the 
-mm kernel before.

> --b.

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:[~2006-04-04 17:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060404014504.564bf45a.akpm@osdl.org>
2006-04-04 16:30 ` [-mm patch] fs/nfsd/nfs4state.c: make a struct static Adrian Bunk
2006-04-04 16:50   ` [NFS] " J. Bruce Fields
2006-04-04 17:29     ` Adrian Bunk [this message]
2006-04-05  2:27 ` 2.6.17-rc1-mm1, nfsd/reiser4 BUG Zan Lynx

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=20060404172913.GT6529@stusta.de \
    --to=bunk@stusta.de \
    --cc=akpm@osdl.org \
    --cc=bfields@fieldses.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=nfs@lists.sourceforge.net \
    /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