From: "J. Bruce Fields" <bfields@fieldses.org>
To: Neil Brown <neilb@suse.de>
Cc: Al Viro <viro@ftp.linux.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lockd and nfsd endianness annotation fixes
Date: Thu, 26 Jul 2007 21:19:22 -0400 [thread overview]
Message-ID: <20070727011922.GC27538@fieldses.org> (raw)
In-Reply-To: <18089.14397.946323.617318@notabene.brown>
On Fri, Jul 27, 2007 at 10:11:41AM +1000, Neil Brown wrote:
> On Thursday July 26, bfields@fieldses.org wrote:
> > On Thu, Jul 26, 2007 at 05:33:49PM +0100, Al Viro wrote:
> > >
> >
> > Oops, thanks; these are my fault.
> >
> > (How are you finding these? I was assuming sparse, but running a make
> > -C2 just now I didn't see anything that would have suggested these
> > fixes. I'm using whatever's current in Fedora--it says 0.3-1.fc7. Do I
> > need something more recent?)
>
> I have a note about that somewhere.....
>
> > From: Al Viro <viro@ftp.linux.org.uk>
> > Subject: Re: [PATCHSET] nfs endianness annotations
> > Date: Thu, 19 Oct 2006 02:26:00 +0100
> > ....
> >
> > Folks, seriously, please run sparse after changes; it's a simple matter of
> > make C=2 CF=-D__CHECK_ENDIAN__ fs/nfs*/; nothing tricky and it saves a lot
> > of potential PITA...
>
> And with lots of good intentions, I ran this about once, and promptly
> forgot.
Thanks, uh, I probably saw that message too.
Hm, trying it just now--it catches the svclock.c mistake, but not the
one in nfsd/nfs4xdr.c--at least not as far as I can tell.
--b.
next prev parent reply other threads:[~2007-07-27 1:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-26 16:33 [PATCH] lockd and nfsd endianness annotation fixes Al Viro
2007-07-26 22:08 ` J. Bruce Fields
2007-07-27 0:11 ` Neil Brown
2007-07-27 1:19 ` J. Bruce Fields [this message]
2007-07-27 1:38 ` Al Viro
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=20070727011922.GC27538@fieldses.org \
--to=bfields@fieldses.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=viro@ftp.linux.org.uk \
/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