linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Alex Shi <alex.shi@linux.alibaba.com>
Cc: Paolo Valente <paolo.valente@linaro.org>,
	linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] block/bfq: remove unused bfq_class_rt which never used
Date: Wed, 22 Jan 2020 10:31:28 -0700	[thread overview]
Message-ID: <8e4f68d3-28a3-22f6-ae55-814903d990b9@kernel.dk> (raw)
In-Reply-To: <1579596534-257642-1-git-send-email-alex.shi@linux.alibaba.com>

On 1/21/20 1:48 AM, Alex Shi wrote:
> This macro is never used after introduced from commit aee69d78dec0
> ("block, bfq: introduce the BFQ-v0 I/O scheduler as an extra scheduler")
> 
> Better to remove it.

Applied, thanks.

-- 
Jens Axboe


      reply	other threads:[~2020-01-22 17:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-21  8:48 [PATCH] block/bfq: remove unused bfq_class_rt which never used Alex Shi
2020-01-22 17:31 ` Jens Axboe [this message]

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=8e4f68d3-28a3-22f6-ae55-814903d990b9@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=alex.shi@linux.alibaba.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paolo.valente@linaro.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).