From: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
To: Steve French <smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Steve French
<steve.french-7I+n7zu2hftEKMMhf/gKZA@public.gmane.org>,
Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
Subject: Re: [PATCH 2/2] CIFS: Fix duplicate line introduced by clone_file_range patch
Date: Tue, 1 Mar 2016 07:50:50 +0100 [thread overview]
Message-ID: <20160301065050.GD31969@lst.de> (raw)
In-Reply-To: <1456791058-92940-1-git-send-email-smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On Mon, Feb 29, 2016 at 06:10:58PM -0600, Steve French wrote:
> Commit 04b38d601239b4 ("vfs: pull btrfs clone API to vfs layer")
> added a duplicated line (in cifsfs.c) which causes a sparse compile
> warning.
>
> Signed-off-by: Steve French <steve.french-7I+n7zu2hftEKMMhf/gKZA@public.gmane.org>
> CC: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
Oops. The fix looks fine to me:
Reviewed-by: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
prev parent reply other threads:[~2016-03-01 6:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <smfrench@gmail.com>
2016-03-01 0:04 ` [PATCH 1/3] s390x: fix condition to choose correct function Steve French
2016-03-01 0:04 ` Steve French
[not found] ` <1456790652-92638-1-git-send-email-smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-03-01 0:05 ` Steve French
2016-03-01 0:05 ` Steve French
2016-03-01 0:09 ` Steve French
2016-03-01 0:10 ` [PATCH 2/2] CIFS: Fix duplicate line introduced by clone_file_range patch Steve French
[not found] ` <1456791058-92940-1-git-send-email-smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-03-01 0:11 ` Fwd: " Steve French
2016-03-01 0:11 ` Steve French
2016-03-01 6:50 ` 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=20160301065050.GD31969@lst.de \
--to=hch-jcswghmuv9g@public.gmane.org \
--cc=linux-cifs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=smfrench-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=steve.french-7I+n7zu2hftEKMMhf/gKZA@public.gmane.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.