linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Layton <jlayton@redhat.com>
To: Vasily Averin <vvs@virtuozzo.com>,
	Alexander Viro <viro@zeniv.linux.org.uk>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] removed extra extern file_fdatawait_range
Date: Sat, 09 Jun 2018 09:44:01 -0400	[thread overview]
Message-ID: <9e3ad8b27b199384e11e64e09b5ea493a744dd4c.camel@redhat.com> (raw)
In-Reply-To: <6524c785-163b-e416-a587-37f5ad31cdb8@virtuozzo.com>

On Sat, 2018-06-09 at 16:18 +0300, Vasily Averin wrote:
> Jeff added this extern twice in commit a823e4589e68
> 
> Fixes: a823e4589e68 ("mm: add file_fdatawait_range and file_write_and_wait")
> Signed-off-by: Vasily Averin <vvs@virtuozzo.com>
> ---
>  include/linux/fs.h | 2 --
>  1 file changed, 2 deletions(-)
> 
> diff --git a/include/linux/fs.h b/include/linux/fs.h
> index 760d8da..2e98d80 100644
> --- a/include/linux/fs.h
> +++ b/include/linux/fs.h
> @@ -2602,8 +2602,6 @@ static inline int filemap_fdatawait(struct address_space *mapping)
>  
>  extern bool filemap_range_has_page(struct address_space *, loff_t lstart,
>  				  loff_t lend);
> -extern int __must_check file_fdatawait_range(struct file *file, loff_t lstart,
> -						loff_t lend);
>  extern int filemap_write_and_wait(struct address_space *mapping);
>  extern int filemap_write_and_wait_range(struct address_space *mapping,
>  				        loff_t lstart, loff_t lend);

Doh! Good catch.

Reviewed-by: Jeff Layton <jlayton@redhat.com>

      reply	other threads:[~2018-06-09 13:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-09 13:18 [PATCH] removed extra extern file_fdatawait_range Vasily Averin
2018-06-09 13:44 ` Jeff Layton [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=9e3ad8b27b199384e11e64e09b5ea493a744dd4c.camel@redhat.com \
    --to=jlayton@redhat.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=vvs@virtuozzo.com \
    /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).