linux-block.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Hisao Tanabe <xtanabe@gmail.com>
Cc: Jens Axboe <axboe@kernel.dk>, linux-block@vger.kernel.org
Subject: Re: [PATCH] block: remove unused variable 'def'
Date: Sun, 7 Apr 2019 23:31:38 -0700	[thread overview]
Message-ID: <20190408063138.GB9257@infradead.org> (raw)
In-Reply-To: <20190407152742.30821-1-xtanabe@gmail.com>

On Mon, Apr 08, 2019 at 12:27:42AM +0900, Hisao Tanabe wrote:
> The 'def' local variable became unused after commit f382fb0bcef4 ("block: remove
> legacy IO schedulers"), let's remove it.
> 
> Signed-off-by: Hisao Tanabe <xtanabe@gmail.com>

Looks good:

Reviewed-by: Christoph Hellwig <hch@lst.de>

  reply	other threads:[~2019-04-08  6:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-07 15:27 [PATCH] block: remove unused variable 'def' Hisao Tanabe
2019-04-08  6:31 ` Christoph Hellwig [this message]
2019-04-08 14:13 ` 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=20190408063138.GB9257@infradead.org \
    --to=hch@infradead.org \
    --cc=axboe@kernel.dk \
    --cc=linux-block@vger.kernel.org \
    --cc=xtanabe@gmail.com \
    /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).