From: Christoph Hellwig <hch@infradead.org>
To: Jeff Layton <jeff.layton@primarydata.com>
Cc: Christoph Hellwig <hch@infradead.org>,
bfields@fieldses.org, linux-nfs@vger.kernel.org
Subject: Re: [PATCH] NFSd: nfs4_preprocess_seqid_op should only set *stpp on success
Date: Sat, 7 Jun 2014 07:26:34 -0700 [thread overview]
Message-ID: <20140607142634.GA3700@infradead.org> (raw)
In-Reply-To: <20140607102326.3b48b558@tlielax.poochiereds.net>
On Sat, Jun 07, 2014 at 10:23:26AM -0400, Jeff Layton wrote:
> Yeah, I mentioned that to Bruce on IRC. This is not really a bugfix,
> per-se, but more of a defensive coding measure.
Looks fine to me for that,
Reviewed-by: Christoph Hellwig <hch@lst.de>
prev parent reply other threads:[~2014-06-07 14:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 18:56 [PATCH] NFSd: nfs4_preprocess_seqid_op should only set *stpp on success Jeff Layton
2014-06-07 14:08 ` Christoph Hellwig
2014-06-07 14:23 ` Jeff Layton
2014-06-07 14:26 ` Christoph Hellwig [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=20140607142634.GA3700@infradead.org \
--to=hch@infradead.org \
--cc=bfields@fieldses.org \
--cc=jeff.layton@primarydata.com \
--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).