From: Jim Rees <rees@umich.edu>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-nfs@vger.kernel.org
Subject: Re: block layout patches
Date: Thu, 14 Jul 2011 13:09:24 -0400 [thread overview]
Message-ID: <20110714170924.GC2607@merit.edu> (raw)
In-Reply-To: <20110714165348.GA13287@infradead.org>
Christoph Hellwig wrote:
Err, what about actually posting them for review first? The only thing
so far has been all that squashme mess.
Sorry for the missing context. About a month ago I sent out an 88 patch set
for pNFS Bakeathon. That was a squashme mess. Later I sent a 35 patch set,
and got back a number of comments. That's had a number of re-writes
resulting in the current patch set, which is 28 patches.
While you're certainly welcome to review what's there now, it's mostly meant
for Benny to pull into his tree to resolve any issues merging with other
pNFS patches that haven't gone upstream yet.
I have a couple more changes to make before sending upstream:
1. replace the upcall mechanism
2. rebase on Trond's IO changes that are now in his nfs-for-next branch
After that I will be sending the entire patch set to the list and soliciting
comments from reviewers. I would very much appreciate it if you could take
the time to look them over when I do.
next prev parent reply other threads:[~2011-07-14 17:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-14 16:50 block layout patches Jim Rees
2011-07-14 16:53 ` Christoph Hellwig
2011-07-14 17:09 ` Jim Rees [this message]
2011-07-14 17:22 ` Christoph Hellwig
2011-07-14 18:32 ` Benny Halevy
2011-07-15 15:22 ` Jim Rees
2011-07-17 14:58 ` Benny Halevy
2011-07-14 16:55 ` Jim Rees
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=20110714170924.GC2607@merit.edu \
--to=rees@umich.edu \
--cc=hch@infradead.org \
--cc=linux-nfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).