linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Souptick Joarder <jrdr.linux@gmail.com>
To: Sabyasachi Gupta <sabyasachi.linux@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Al Viro <viro@zeniv.linux.org.uk>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs/block_dev.c: Remove duplicate header
Date: Mon, 11 Mar 2019 21:19:19 +0530	[thread overview]
Message-ID: <CAFqt6zb4yG6ZZ=Fh2dWc5GnxJA5T7BRAxjXXfRxdJ1dSn_QtUA@mail.gmail.com> (raw)
In-Reply-To: <5c867e95.1c69fb81.4f15a.e5e4@mx.google.com>

On Mon, Mar 11, 2019 at 8:58 PM Sabyasachi Gupta
<sabyasachi.linux@gmail.com> wrote:
>
> Remove linux/dax.h which is included more than once.
>
> Signed-off-by: Sabyasachi Gupta <sabyasachi.linux@gmail.com>

Acked-by: Souptick Joarder <jrdr.linux@gmail.com>

> ---
>  fs/block_dev.c | 1 -
>  1 file changed, 1 deletion(-)
>
> diff --git a/fs/block_dev.c b/fs/block_dev.c
> index cdda48f..8abcdb6 100644
> --- a/fs/block_dev.c
> +++ b/fs/block_dev.c
> @@ -29,7 +29,6 @@
>  #include <linux/namei.h>
>  #include <linux/log2.h>
>  #include <linux/cleancache.h>
> -#include <linux/dax.h>
>  #include <linux/badblocks.h>
>  #include <linux/task_io_accounting_ops.h>
>  #include <linux/falloc.h>
> --
> 2.7.4
>

  reply	other threads:[~2019-03-11 15:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-11 15:28 [PATCH] fs/block_dev.c: Remove duplicate header Sabyasachi Gupta
2019-03-11 15:49 ` Souptick Joarder [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-01-10 15:25 Sabyasachi Gupta
2019-01-10 15:25 ` Sabyasachi Gupta
2019-01-16 12:16 ` Souptick Joarder
2019-01-16 12:16   ` Souptick Joarder
2019-01-30  2:26   ` Sabyasachi Gupta
2019-02-13 16:11     ` Sabyasachi Gupta

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='CAFqt6zb4yG6ZZ=Fh2dWc5GnxJA5T7BRAxjXXfRxdJ1dSn_QtUA@mail.gmail.com' \
    --to=jrdr.linux@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sabyasachi.linux@gmail.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).