From: Jens Axboe <axboe@kernel.dk>
To: tj@kernel.org, Chengming Zhou <zhouchengming@bytedance.com>
Cc: paolo.valente@linaro.org, josef@toxicpanda.com,
linux-block@vger.kernel.org, cgroups@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] blk-cgroup: some cleanup
Date: Thu, 06 Apr 2023 16:17:59 -0600 [thread overview]
Message-ID: <168081947971.7640.13634484209341526558.b4-ty@kernel.dk> (raw)
In-Reply-To: <20230406145050.49914-1-zhouchengming@bytedance.com>
On Thu, 06 Apr 2023 22:50:47 +0800, Chengming Zhou wrote:
> These are some cleanup patches of blk-cgroup. Thanks for review.
>
> v2:
> - Add Acked tags from Tejun.
>
> Chengming Zhou (3):
> block, bfq: remove BFQ_WEIGHT_LEGACY_DFL
> blk-cgroup: delete cpd_bind_fn of blkcg_policy
> blk-cgroup: delete cpd_init_fn of blkcg_policy
>
> [...]
Applied, thanks!
[1/3] block, bfq: remove BFQ_WEIGHT_LEGACY_DFL
commit: e9f2f3f590289681c71d0137d4e5e88421f934c6
[2/3] blk-cgroup: delete cpd_bind_fn of blkcg_policy
commit: d1023165eef83dace7cc6299af904f26272baaca
[3/3] blk-cgroup: delete cpd_init_fn of blkcg_policy
commit: 650e2cb50f3fc45d0585ed8609db9519f6c9bcd8
Best regards,
--
Jens Axboe
next prev parent reply other threads:[~2023-04-06 22:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 14:50 Chengming Zhou
2023-04-06 14:50 ` [PATCH v2 1/3] block, bfq: remove BFQ_WEIGHT_LEGACY_DFL Chengming Zhou
2023-04-06 14:50 ` [PATCH v2 2/3] blk-cgroup: delete cpd_bind_fn of blkcg_policy Chengming Zhou
2023-04-06 14:50 ` [PATCH v2 3/3] blk-cgroup: delete cpd_init_fn " Chengming Zhou
2023-04-06 22:17 ` Jens Axboe [this message]
2023-04-07 18:41 ` [PATCH v2 0/3] blk-cgroup: some cleanup Bart Van Assche
2023-04-07 18:44 ` Jens Axboe
2023-04-07 19:45 ` Bart Van Assche
2023-04-08 3:37 ` [External] " Chengming Zhou
2023-04-08 14:31 ` Chengming Zhou
2023-04-10 1:57 ` Yu Kuai
2023-04-10 18:47 ` Bart Van Assche
2023-04-10 22:20 ` Bart Van Assche
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=168081947971.7640.13634484209341526558.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=paolo.valente@linaro.org \
--cc=tj@kernel.org \
--cc=zhouchengming@bytedance.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
all inboxes | Powered by JetHome®