From: Jens Axboe <axboe@kernel.dk>
To: jack@suse.cz, Yu Kuai <yukuai3@huawei.com>, paolo.valente@linaro.org
Cc: linux-block@vger.kernel.org, yi.zhang@huawei.com,
linux-kernel@vger.kernel.org, cgroups@vger.kernel.org
Subject: Re: [PATCH v3 0/3] block, bfq: minor cleanup and fix
Date: Fri, 18 Feb 2022 06:13:40 -0700 [thread overview]
Message-ID: <164519002068.11187.11125581863819344403.b4-ty@kernel.dk> (raw)
In-Reply-To: <20220129015924.3958918-1-yukuai3@huawei.com>
On Sat, 29 Jan 2022 09:59:21 +0800, Yu Kuai wrote:
> Changes in v3:
> - fix a clerical error in patch 2
>
> Chagnes in v2:
> - add comment in patch 2
> - remove patch 4, since the problem do not exist.
>
> [...]
Applied, thanks!
[1/3] block, bfq: cleanup bfq_bfqq_to_bfqg()
commit: 43a4b1fee098bd38eed9c334d0e0df221ecdf719
[2/3] block, bfq: avoid moving bfqq to it's parent bfqg
commit: c5e4cb0fcbbaa5ad853818c4a2383e9bd147fad6
[3/3] block, bfq: don't move oom_bfqq
commit: 8410f70977734f21b8ed45c37e925d311dfda2e7
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2022-02-18 13:13 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 1:59 [PATCH v3 0/3] block, bfq: minor cleanup and fix Yu Kuai
2022-01-29 1:59 ` Yu Kuai
2022-01-29 1:51 ` Jens Axboe
2022-01-29 1:51 ` Jens Axboe
2022-01-29 2:05 ` yukuai (C)
2022-01-29 2:05 ` yukuai (C)
2022-02-10 11:46 ` yukuai (C)
2022-02-10 11:46 ` yukuai (C)
2022-02-18 8:30 ` yukuai (C)
2022-02-18 8:30 ` yukuai (C)
2022-01-29 1:59 ` [PATCH v3 1/3] block, bfq: cleanup bfq_bfqq_to_bfqg() Yu Kuai
2022-01-29 1:59 ` Yu Kuai
2022-01-29 1:59 ` [PATCH v3 2/3] block, bfq: avoid moving bfqq to it's parent bfqg Yu Kuai
2022-01-29 1:59 ` Yu Kuai
2022-02-08 3:53 ` yukuai (C)
2022-02-08 3:53 ` yukuai (C)
2022-02-08 16:07 ` Paolo Valente
2022-02-08 16:07 ` Paolo Valente
2022-01-29 1:59 ` [PATCH v3 3/3] block, bfq: don't move oom_bfqq Yu Kuai
2022-01-29 1:59 ` Yu Kuai
2022-02-18 13:13 ` 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=164519002068.11187.11125581863819344403.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=cgroups@vger.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=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 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.