From: Christoph Hellwig <hch@infradead.org>
To: "Ma, Jianpeng" <jianpeng.ma@intel.com>
Cc: Christoph Hellwig <hch@infradead.org>,
"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: Re: [RESEND]block: remove unused header
Date: Tue, 21 Apr 2020 05:20:53 -0700 [thread overview]
Message-ID: <20200421122053.GA2944@infradead.org> (raw)
In-Reply-To: <6AA21C22F0A5DA478922644AD2EC308C73C54781@SHSMSX101.ccr.corp.intel.com>
On Tue, Apr 21, 2020 at 11:48:08AM +0000, Ma, Jianpeng wrote:
> Dax related code already removed from this file.
>
> Signed-off-by: Jianpeng Ma <jianpeng.ma@intel.com>
Looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
next prev parent reply other threads:[~2020-04-21 12:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 11:48 [RESEND]block: remove unused header Ma, Jianpeng
2020-04-21 12:20 ` Christoph Hellwig [this message]
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=20200421122053.GA2944@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=dan.j.williams@intel.com \
--cc=jianpeng.ma@intel.com \
--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).