From: Jens Axboe <axboe@kernel.dk>
To: josef@toxicpanda.com, hch@lst.de, Tejun Heo <tj@kernel.org>
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
yukuai1@huaweicloud.com
Subject: Re: [PATCHSET v4 block/for-next] blkcg: Improve blkg config helpers and make iolatency init lazy
Date: Thu, 13 Apr 2023 06:47:25 -0600 [thread overview]
Message-ID: <168139004581.7900.17121403006264906726.b4-ty@kernel.dk> (raw)
In-Reply-To: <20230413000649.115785-1-tj@kernel.org>
On Wed, 12 Apr 2023 14:06:45 -1000, Tejun Heo wrote:
> * v2[2] fixes the build failure caused by v1[1] forgetting to update bfq.
>
> * v3[3] drops __acuquires/__releases() changes and updates patch descriptions.
>
> * v4 rebases on top of the current block/for-next.
>
> This patchset:
>
> [...]
Applied, thanks!
[1/4] blkcg: Drop unnecessary RCU read [un]locks from blkg_conf_prep/finish()
commit: 83462a6c971cdc550475b672cf29bd3b53bedf84
[2/4] blkcg: Restructure blkg_conf_prep() and friends
commit: faffaab2895914a803e011600164683bf747fee3
[3/4] blk-iolatency: s/blkcg_rq_qos/iolat_rq_qos/
commit: 3304918758125a0eb18fb480c82945e327b81f78
[4/4] blk-iolatency: Make initialization lazy
commit: a13696b83da4f1e53e192ec3e239afd3a96ff747
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2023-04-13 12:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-13 0:06 [PATCHSET v4 block/for-next] blkcg: Improve blkg config helpers and make iolatency init lazy Tejun Heo
2023-04-13 0:06 ` [PATCH 1/4] blkcg: Drop unnecessary RCU read [un]locks from blkg_conf_prep/finish() Tejun Heo
2023-04-13 4:59 ` Christoph Hellwig
2023-04-13 0:06 ` [PATCH 2/4] blkcg: Restructure blkg_conf_prep() and friends Tejun Heo
2023-04-13 5:00 ` Christoph Hellwig
2023-04-13 0:06 ` [PATCH 3/4] blk-iolatency: s/blkcg_rq_qos/iolat_rq_qos/ Tejun Heo
2023-04-13 0:06 ` [PATCH 4/4] blk-iolatency: Make initialization lazy Tejun Heo
2023-04-13 2:09 ` Yu Kuai
2023-04-13 5:00 ` Christoph Hellwig
2023-04-13 12:47 ` 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=168139004581.7900.17121403006264906726.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=josef@toxicpanda.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tj@kernel.org \
--cc=yukuai1@huaweicloud.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.