From: "Ma, Jianpeng" <jianpeng.ma@intel.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: "axboe@kernel.dk" <axboe@kernel.dk>,
"Williams, Dan J" <dan.j.williams@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: [RESEND]block: remove unused header
Date: Tue, 21 Apr 2020 11:48:08 +0000 [thread overview]
Message-ID: <6AA21C22F0A5DA478922644AD2EC308C73C54781@SHSMSX101.ccr.corp.intel.com> (raw)
Dax related code already removed from this file.
Signed-off-by: Jianpeng Ma <jianpeng.ma@intel.com>
---
fs/block_dev.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/fs/block_dev.c b/fs/block_dev.c
index 52b6f646cdbd..4163435dc231 100644
--- a/fs/block_dev.c
+++ b/fs/block_dev.c
@@ -19,7 +19,6 @@
#include <linux/module.h>
#include <linux/blkpg.h>
#include <linux/magic.h>
-#include <linux/dax.h>
#include <linux/buffer_head.h>
#include <linux/swap.h>
#include <linux/pagevec.h>
--
2.17.1
> -----Original Message-----
> From: Christoph Hellwig <hch@infradead.org>
> Sent: Tuesday, April 21, 2020 7:33 PM
> To: Ma, Jianpeng <jianpeng.ma@intel.com>
> Cc: axboe@kernel.dk; Williams, Dan J <dan.j.williams@intel.com>; linux-
> kernel@vger.kernel.org
> Subject: Re: block: remove unused header
>
> On Tue, Apr 21, 2020 at 05:48:46AM +0000, Ma, Jianpeng wrote:
> > >From 95218bc1d79f2bcbdd8819be26efa698868a34ca Mon Sep 17 00:00:00
> 2001
> > From: Jianpeng Ma <jianpeng.ma@intel.com>
> > Date: Tue, 21 Apr 2020 01:15:24 -0400
> > Subject: [PATCH] block: remove unused header.
> >
> > Dax related code already removed from this file.
> >
> > Signed-off-by: Jianpeng Ma <jianpeng.ma@intel.com>
>
> Except for the mangled patch format this looks good:
>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
>
> Can you resend it with proper patch headers?
next reply other threads:[~2020-04-21 11:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 11:48 Ma, Jianpeng [this message]
2020-04-21 12:20 ` [RESEND]block: remove unused header Christoph Hellwig
2020-04-21 15:51 ` Jens Axboe
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=6AA21C22F0A5DA478922644AD2EC308C73C54781@SHSMSX101.ccr.corp.intel.com \
--to=jianpeng.ma@intel.com \
--cc=axboe@kernel.dk \
--cc=dan.j.williams@intel.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.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 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).