From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jeff Layton <jlayton@redhat.com>
Cc: Corentin Labbe <clabbe.montjoie@gmail.com>,
trond.myklebust@primarydata.com, anna.schumaker@netapp.com,
viro@zeniv.linux.org.uk, 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 09:25:53 -0400 [thread overview]
Message-ID: <20170926132553.GA25286@fieldses.org> (raw)
In-Reply-To: <1506424509.3182.0.camel@redhat.com>
On Tue, Sep 26, 2017 at 07:15:09AM -0400, Jeff Layton wrote:
> 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>
Yep, applying, thanks.
--b.
prev parent reply other threads:[~2017-09-26 13:25 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 ` [PATCH 0/3] nfs_common: misc patchs Jeff Layton
2017-09-26 13:25 ` J. Bruce Fields [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=20170926132553.GA25286@fieldses.org \
--to=bfields@fieldses.org \
--cc=anna.schumaker@netapp.com \
--cc=clabbe.montjoie@gmail.com \
--cc=jlayton@redhat.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 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.