Linux block layer
 help / color / mirror / Atom feed
From: Qiliang Yuan <qiliang.yuan@linux.dev>
To: Jens Axboe <axboe@kernel.dk>
Cc: Qiliang Yuan <qiliang.yuan@linux.dev>,
	Damien Le Moal <dlemoal@kernel.org>,
	Ming Lei <tom.leiming@gmail.com>,
	Nilay Shroff <nilay@linux.ibm.com>,
	Hannes Reinecke <hare@suse.de>,
	linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH v2 0/2] block: make changing to the current I/O scheduler cheap again
Date: Wed, 18 Nov 2026 20:07:33 -0500	[thread overview]
Message-ID: <20261119010733.7312-1-qiliang.yuan@linux.dev> (raw)
In-Reply-To: <179501805754.17649.16701221943802051712.b4-ty@b4>

On Wed, 18 Nov 2026 09:07:37 -0700, Jens Axboe wrote:
> Applied, thanks!
>
[...]
> [2/2] block: return early when the elevator doesn't change
>       commit: 375a88c6176ffe05e521c2df31b1ceaf4ae5fbaf

This one went in from v2, whose Fixes tag Christoph pointed out was
wrong. v3 changed it to the commit that added the freeze, with the code
unchanged:

Fixes: af2814149883e ("block: freeze the queue in queue_attr_store")

Could you update it in for-next?

v3: https://lore.kernel.org/r/20261116-bug-block-elevator-unchanged-v3-2-cb4dda2dadf4@linux.dev

Thanks,
Qiliang

      reply	other threads:[~2026-11-19  1:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-15  1:58 [PATCH v2 0/2] block: make changing to the current I/O scheduler cheap again Qiliang Yuan
2026-11-15  1:58 ` [PATCH v2 1/2] block: don't request a module for the none elevator Qiliang Yuan
2026-11-15  1:58 ` [PATCH v2 2/2] block: return early when the elevator doesn't change Qiliang Yuan
2026-11-16  6:27   ` Christoph Hellwig
2026-11-18 16:07 ` [PATCH v2 0/2] block: make changing to the current I/O scheduler cheap again Jens Axboe
2026-11-19  1:07   ` Qiliang Yuan [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=20261119010733.7312-1-qiliang.yuan@linux.dev \
    --to=qiliang.yuan@linux.dev \
    --cc=axboe@kernel.dk \
    --cc=dlemoal@kernel.org \
    --cc=hare@suse.de \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nilay@linux.ibm.com \
    --cc=tom.leiming@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