From: Al Viro <viro@ftp.linux.org.uk>
To: linux-kernel@vger.kernel.org
Cc: neilb@cse.unsw.edu.au, trond.myklebust@fys.uio.no
Subject: [PATCHSET] nfs endianness annotations
Date: Tue, 10 Oct 2006 04:10:31 +0100 [thread overview]
Message-ID: <E1GX80l-00049E-00@ZenIV.linux.org.uk> (raw)
Series below does endianness annotations of nfs and nfsd; it had been
sitting in my tree for quite a while. In part it's based on Alexey's
patches.
I thought to hold it back until the next merge window, but since we
do get new breakage that would be instantly caught by endianness checks...
IMO it makes sense to see if that puppy could be merged at this point.
In any case, the first patch in series is absolutely needed - it's
fixing a genuine recently introduced bug.
Comments are welcome.
next reply other threads:[~2006-10-10 3:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-10 3:10 Al Viro [this message]
[not found] <E1GX7zV-00047C-PO@ZenIV.linux.org.uk>
2006-10-18 21:26 ` [PATCHSET] nfs endianness annotations Trond Myklebust
2006-10-19 0:31 ` Neil Brown
2006-10-19 1:26 ` Al Viro
2006-10-19 2:55 ` Neil Brown
2006-10-19 5:30 ` Grant Coady
2006-10-19 6:32 ` Neil Brown
2006-10-19 23:22 ` Randy Dunlap
2006-10-19 11:49 ` 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=E1GX80l-00049E-00@ZenIV.linux.org.uk \
--to=viro@ftp.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox