From: "J. Bruce Fields" <bfields@fieldses.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT] nfsd bugfix for 4.0
Date: Fri, 20 Mar 2015 12:41:30 -0400 [thread overview]
Message-ID: <20150320164130.GG2036@fieldses.org> (raw)
In-Reply-To: <20150320162430.GB18786@infradead.org>
On Fri, Mar 20, 2015 at 09:24:30AM -0700, Christoph Hellwig wrote:
> FYI, I think the patch Kinglong Mee sent today is the better fix,
> together with the mangled patch description in mine it might be better
> to send that after a little bit of testing.
Gah, I'm not keeping up with my mail.
I've got Kinglong Mee's patch queued up as incremental patch on top of
this pull request. I think it's not that critical.
(But Linus if you want to drop this I can submit the revised patch with
other stuff next week, I don't care much either way.)
--b.
next prev parent reply other threads:[~2015-03-20 16:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 16:21 [GIT] nfsd bugfix for 4.0 J. Bruce Fields
2015-03-20 16:24 ` Christoph Hellwig
2015-03-20 16:41 ` J. Bruce Fields [this message]
2015-03-21 17:42 ` Linus Torvalds
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=20150320164130.GG2036@fieldses.org \
--to=bfields@fieldses.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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.