linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Chengguang Xu <cgxu519@gmx.com>,
	linux-block@vger.kernel.org, linux-fsdevel@vger.kernel.org
Cc: viro@zeniv.linux.org.uk, axboe@kernel.dk
Subject: Re: [PATCH v2] fs/block_dev.c: remove unused include
Date: Tue, 09 Apr 2019 08:01:45 -0700	[thread overview]
Message-ID: <1554822105.161891.2.camel@acm.org> (raw)
In-Reply-To: <20190409103752.28532-1-cgxu519@gmx.com>

On Tue, 2019-04-09 at 18:37 +0800, Chengguang Xu wrote:
> Just remove unused include <linux/badblocks.h> from
> fs/block_dev.c.

Reviewed-by: Bart Van Assche <bvanassche@acm.org>



  reply	other threads:[~2019-04-09 15:01 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-09 10:37 [PATCH v2] fs/block_dev.c: remove unused include Chengguang Xu
2019-04-09 15:01 ` Bart Van Assche [this message]
2019-04-09 23:17 ` Al Viro

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=1554822105.161891.2.camel@acm.org \
    --to=bvanassche@acm.org \
    --cc=axboe@kernel.dk \
    --cc=cgxu519@gmx.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-fsdevel@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).