public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Yu Kuai <yukuai1@huaweicloud.com>
Cc: jack@suse.cz, hch@infradead.org, ebiggers@kernel.org,
	paolo.valente@linaro.org, axboe@kernel.dk,
	linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
	yukuai3@huawei.com, yi.zhang@huawei.com
Subject: Re: [PATCH v4 5/6] elevator: add new field flags in struct elevator_queue
Date: Tue, 18 Oct 2022 08:49:46 -0700	[thread overview]
Message-ID: <Y07LGoAcfODYerpk@infradead.org> (raw)
In-Reply-To: <20220930031906.4164306-6-yukuai1@huaweicloud.com>

Looks good:

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

  reply	other threads:[~2022-10-18 15:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-30  3:19 [PATCH v4 0/6] blk-wbt: simple improvment to enable wbt correctly Yu Kuai
2022-09-30  3:19 ` [PATCH v4 1/6] elevator: remove redundant code in elv_unregister_queue() Yu Kuai
2022-09-30  3:19 ` [PATCH v4 2/6] blk-wbt: remove unnecessary check in wbt_enable_default() Yu Kuai
2022-10-18 15:43   ` Christoph Hellwig
2022-09-30  3:19 ` [PATCH v4 3/6] blk-wbt: make enable_state more accurate Yu Kuai
2022-10-18 15:47   ` Christoph Hellwig
2022-09-30  3:19 ` [PATCH v4 4/6] blk-wbt: don't show valid wbt_lat_usec in sysfs while wbt is disabled Yu Kuai
2022-10-18 15:49   ` Christoph Hellwig
2022-10-19  1:06     ` Yu Kuai
2022-09-30  3:19 ` [PATCH v4 5/6] elevator: add new field flags in struct elevator_queue Yu Kuai
2022-10-18 15:49   ` Christoph Hellwig [this message]
2022-09-30  3:19 ` [PATCH v4 6/6] blk-wbt: don't enable throttling if default elevator is bfq Yu Kuai
2022-10-18 15:50   ` Christoph Hellwig
2022-10-11  8:06 ` [PATCH v4 0/6] blk-wbt: simple improvment to enable wbt correctly Yu Kuai
2022-10-18  2:28   ` Yu Kuai

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=Y07LGoAcfODYerpk@infradead.org \
    --to=hch@infradead.org \
    --cc=axboe@kernel.dk \
    --cc=ebiggers@kernel.org \
    --cc=jack@suse.cz \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paolo.valente@linaro.org \
    --cc=yi.zhang@huawei.com \
    --cc=yukuai1@huaweicloud.com \
    --cc=yukuai3@huawei.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