From: Christoph Hellwig <hch@infradead.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Christoph Hellwig <hch@infradead.org>,
Linus Torvalds <torvalds@osdl.org>,
linux-kernel@vger.kernel.org, nfs@lists.sourceforge.net,
nfsv4@linux-nfs.org
Subject: Re: [NFS] [GIT] NFS client update for 2.6.16
Date: Wed, 22 Mar 2006 10:25:22 +0000 [thread overview]
Message-ID: <20060322102522.GA7025@infradead.org> (raw)
In-Reply-To: <1142967482.7987.83.camel@lade.trondhjem.org>
On Tue, Mar 21, 2006 at 01:58:01PM -0500, Trond Myklebust wrote:
> Could you, BTW, please post these pending patches? They are clearly not
> in -mm, since these patches have been there for some time without
> conflicting with anything else. The only references I could find were to
> the following thread:
>
> http://thread.gmane.org/gmane.linux.file-systems/7748
>
> which basically just adds a BUG() if you call NFS O_DIRECT with a
> multi-segment iovec.
Yes, that's the latest public version. and nfs is one of the last missing
items.
next prev parent reply other threads:[~2006-03-22 10:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-21 17:11 Trond Myklebust
2006-03-21 17:46 ` [NFS] " Christoph Hellwig
2006-03-21 18:03 ` Chuck Lever
2006-03-21 18:55 ` Christoph Hellwig
2006-03-21 18:08 ` Trond Myklebust
2006-03-21 18:57 ` Christoph Hellwig
2006-03-21 19:06 ` Trond Myklebust
2006-03-21 19:12 ` Chuck Lever
2006-03-22 10:30 ` Christoph Hellwig
2006-03-22 11:35 ` Trond Myklebust
2006-03-21 18:58 ` Trond Myklebust
2006-03-22 10:25 ` Christoph Hellwig [this message]
2006-03-21 17:50 ` Jeff Garzik
2006-03-21 18:12 ` Trond Myklebust
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=20060322102522.GA7025@infradead.org \
--to=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nfs@lists.sourceforge.net \
--cc=nfsv4@linux-nfs.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®