From: Sabyasachi Gupta <sabyasachi.linux@gmail.com>
To: Souptick Joarder <jrdr.linux@gmail.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-kernel@vger.kernel.org,
Brajeswar Ghosh <brajeswar.linux@gmail.com>
Subject: Re: [PATCH] fs/block_dev.c: Remove duplicate header
Date: Wed, 30 Jan 2019 07:56:11 +0530 [thread overview]
Message-ID: <CAJr6mf02+B4BrWC8AyLCXNu5wE8u5MPfWC4WrgrJ_9B6Z9DMbQ@mail.gmail.com> (raw)
In-Reply-To: <CAFqt6zawA928gHRtSiKbBC0QcXxZs3U-rZdDF1yyaLjdTHqgFQ@mail.gmail.com>
On Wed, Jan 16, 2019 at 5:46 PM Souptick Joarder <jrdr.linux@gmail.com> wrote:
>
> On Thu, Jan 10, 2019 at 8:55 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>
>
If no further comment, can we get this patch in queue for 5.1 ?
> > ---
> > 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
> >
next prev parent reply other threads:[~2019-01-30 2:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-10 15:25 [PATCH] fs/block_dev.c: Remove duplicate header 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 [this message]
2019-02-13 16:11 ` Sabyasachi Gupta
2019-03-11 15:28 Sabyasachi Gupta
2019-03-11 15:49 ` Souptick Joarder
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=CAJr6mf02+B4BrWC8AyLCXNu5wE8u5MPfWC4WrgrJ_9B6Z9DMbQ@mail.gmail.com \
--to=sabyasachi.linux@gmail.com \
--cc=brajeswar.linux@gmail.com \
--cc=jrdr.linux@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).