From: Jeff Layton <jlayton@redhat.com>
To: Corentin Labbe <clabbe.montjoie@gmail.com>,
trond.myklebust@primarydata.com, anna.schumaker@netapp.com,
bfields@fieldses.org, viro@zeniv.linux.org.uk
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 0/3] nfs_common: misc patchs
Date: Tue, 26 Sep 2017 07:15:09 -0400 [thread overview]
Message-ID: <1506424509.3182.0.camel@redhat.com> (raw)
In-Reply-To: <20170926071407.31719-1-clabbe.montjoie@gmail.com>
On Tue, 2017-09-26 at 09:14 +0200, Corentin Labbe wrote:
> Hello
>
> The origin of this series is a build warning fix.
> But reading the code show me two other possible patch.
>
> Regards
>
> Corentin Labbe (3):
> nfs_common: fix build warning in grace.c
> nfs_common: move locks_in_grace comment at the right place
> nfs_common: convert int to bool
>
> fs/nfs_common/grace.c | 24 ++++++++++++------------
> include/linux/fs.h | 4 ++--
> 2 files changed, 14 insertions(+), 14 deletions(-)
>
Looks like a reasonable set of cleanups. Probably fine for v4.15?
Reviewed-by: Jeff Layton <jlayton@redhat.com>
next prev parent reply other threads:[~2017-09-26 11:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-26 7:14 [PATCH 0/3] nfs_common: misc patchs Corentin Labbe
2017-09-26 7:14 ` [PATCH 1/3] nfs_common: fix build warning in grace.c Corentin Labbe
2017-09-26 7:14 ` [PATCH 2/3] nfs_common: move locks_in_grace comment at the right place Corentin Labbe
2017-09-26 7:14 ` [PATCH 3/3] nfs_common: convert int to bool Corentin Labbe
2017-09-26 11:15 ` Jeff Layton [this message]
2017-09-26 13:25 ` [PATCH 0/3] nfs_common: misc patchs J. Bruce Fields
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=1506424509.3182.0.camel@redhat.com \
--to=jlayton@redhat.com \
--cc=anna.schumaker@netapp.com \
--cc=bfields@fieldses.org \
--cc=clabbe.montjoie@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.com \
--cc=viro@zeniv.linux.org.uk \
/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).