From: Christoph Hellwig <hch@lst.de>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: Christoph Hellwig <hch@lst.de>,
Jeff Layton <jeff.layton@primarydata.com>,
linux-nfs@vger.kernel.org,
Sachin Bhamare <sachin.bhamare@primarydata.com>,
Jeff Layton <jlayton@primarydata.com>
Subject: Re: [PATCH 2/2] nfsd: fix pNFS return on close semantics
Date: Tue, 28 Apr 2015 19:49:34 +0200 [thread overview]
Message-ID: <20150428174934.GA5887@lst.de> (raw)
In-Reply-To: <20150428160353.GN4083@fieldses.org>
On Tue, Apr 28, 2015 at 12:03:53PM -0400, J. Bruce Fields wrote:
> > I'm ok with a cc to stable, but it's a bit borderline. Note that currently
> > you even applied my two patches to your 4.2 incoming queue, not even 4.1..
>
> Yeah, those -incoming branches are random works-in-progress and will get
> rebased frequently, I'll move the other to for-4.1 and leave this one
> for 4.2.
I would prefer if we could queue it up for 4.1 if possible.
next prev parent reply other threads:[~2015-04-28 17:49 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-27 12:50 two pNFS server fixes for 4.1, V2 Christoph Hellwig
2015-04-27 12:50 ` [PATCH 1/2] nfsd/blocklayout: pretend we can send deviceid notifications Christoph Hellwig
2015-04-27 20:36 ` J. Bruce Fields
2015-04-27 12:50 ` [PATCH 2/2] nfsd: fix pNFS return on close semantics Christoph Hellwig
2015-04-27 20:39 ` J. Bruce Fields
2015-04-27 23:30 ` Jeff Layton
2015-04-28 8:14 ` Christoph Hellwig
2015-04-28 16:03 ` J. Bruce Fields
2015-04-28 17:49 ` Christoph Hellwig [this message]
2015-04-28 17:54 ` Trond Myklebust
2015-04-28 18:11 ` Christoph Hellwig
2015-04-28 15:51 ` J. Bruce Fields
-- strict thread matches above, loose matches on Subject: below --
2015-04-26 15:48 two pNFS server fixes for 4.1 Christoph Hellwig
2015-04-26 15:48 ` [PATCH 2/2] nfsd: fix pNFS return on close semantics Christoph Hellwig
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=20150428174934.GA5887@lst.de \
--to=hch@lst.de \
--cc=bfields@fieldses.org \
--cc=jeff.layton@primarydata.com \
--cc=jlayton@primarydata.com \
--cc=linux-nfs@vger.kernel.org \
--cc=sachin.bhamare@primarydata.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.