From: Al Viro <viro@ZenIV.linux.org.uk>
To: Alexey Dobriyan <adobriyan@gmail.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] nfs: add endian annotations
Date: Sun, 11 Sep 2005 06:56:04 +0100 [thread overview]
Message-ID: <20050911055604.GI25261@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20050910164246.GC23850@mipter.zuzino.mipt.ru>
All 3 merged into -bird; one thing that is probably worth doing is separate
type for server-returned error (always __be32). That's a large part of
nfs patch, IIRC - separating it would be worth doing.
This stuff should be split before going upstream, IMO - I'll see what I
can do with that.
prev parent reply other threads:[~2005-09-11 5:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-10 16:42 [PATCH 3/3] nfs: add endian annotations Alexey Dobriyan
2005-09-11 5:56 ` Al Viro [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=20050911055604.GI25261@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=adobriyan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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