From: Jens Axboe <axboe@kernel.dk>
To: Kemeng Shi <shikemeng@huawei.com>, josef@toxicpanda.com, tj@kernel.org
Cc: linux-kernel@vger.kernel.org, cgroups@vger.kernel.org,
linux-block@vger.kernel.org
Subject: Re: [PATCH v2 0/3] A few cleanup patches for blk-iolatency.c
Date: Tue, 01 Nov 2022 08:17:56 -0600 [thread overview]
Message-ID: <166731227683.256723.3065138031958824780.b4-ty@kernel.dk> (raw)
In-Reply-To: <20221018111240.22612-1-shikemeng@huawei.com>
On Tue, 18 Oct 2022 19:12:37 +0800, Kemeng Shi wrote:
> This series contains three cleanup patches to remove redundant check,
> correct comment and simplify struct iolatency_grp in blk-iolatency.c.
>
Applied, thanks!
[1/3] block: Remove redundant parent blkcg_gp check in check_scale_change
commit: b6e03072a91ecc815c9f62037871d621b09df2b3
[2/3] block: Correct comment for scale_cookie_change
commit: 77445572e643538019d9919669ddf36efb6a353a
[3/3] block: Replace struct rq_depth with unsigned int in struct iolatency_grp
commit: 718ac0e343f8fd81ab042aa4936d25fe10f6b318
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-11-01 14:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 11:12 [PATCH v2 0/3] A few cleanup patches for blk-iolatency.c Kemeng Shi
2022-10-18 11:12 ` Kemeng Shi
[not found] ` <20221018111240.22612-1-shikemeng-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2022-10-18 11:12 ` [PATCH v2 1/3] block: Remove redundant parent blkcg_gp check in check_scale_change Kemeng Shi
2022-10-18 11:12 ` Kemeng Shi
2022-10-18 11:12 ` [PATCH v2 2/3] block: Correct comment for scale_cookie_change Kemeng Shi
2022-10-18 11:12 ` Kemeng Shi
[not found] ` <20221018111240.22612-3-shikemeng-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2022-11-01 9:38 ` Kemeng Shi
2022-11-01 9:38 ` Kemeng Shi
2022-11-02 14:11 ` Josef Bacik
2022-11-02 14:11 ` Josef Bacik
2022-10-18 11:12 ` [PATCH v2 3/3] block: Replace struct rq_depth with unsigned int in struct iolatency_grp Kemeng Shi
2022-10-18 11:12 ` Kemeng Shi
2022-11-01 14:17 ` 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=166731227683.256723.3065138031958824780.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=cgroups@vger.kernel.org \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shikemeng@huawei.com \
--cc=tj@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.