Linux block layer
 help / color / mirror / Atom feed
From: Chaitanya Kulkarni <chaitanyak@nvidia.com>
To: Bart Van Assche <bvanassche@acm.org>, Jens Axboe <axboe@kernel.dk>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	Christoph Hellwig <hch@lst.de>, Hannes Reinecke <hare@kernel.org>,
	Damien Le Moal <dlemoal@kernel.org>, Tejun Heo <tj@kernel.org>,
	Josef Bacik <josef@toxicpanda.com>
Subject: Re: [PATCH v7 05/14] block/cgroup: Improve lock context annotations
Date: Fri, 5 Jun 2026 18:15:06 +0000	[thread overview]
Message-ID: <2fc5cfcf-c277-4603-add5-faee336d5ffc@nvidia.com> (raw)
In-Reply-To: <58ddd6e2b960bdfa03d0007984386bc0ba351391.1780682325.git.bvanassche@acm.org>

Looks good.

Reviewed-by: Chaitanya Kulkarni <kch@nvidia.com>

-ck



  reply	other threads:[~2026-06-05 18:15 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-05 18:00 [PATCH v7 00/14] Enable lock context analysis for the block layer core Bart Van Assche
2026-06-05 18:00 ` [PATCH v7 01/14] block: Annotate the queue limits functions Bart Van Assche
2026-06-05 18:13   ` Chaitanya Kulkarni
2026-06-05 18:00 ` [PATCH v7 02/14] block/bdev: Annotate the blk_holder_ops callback functions Bart Van Assche
2026-06-05 18:13   ` Chaitanya Kulkarni
2026-06-05 18:00 ` [PATCH v7 03/14] block/cgroup: Split blkg_conf_prep() Bart Van Assche
2026-06-05 18:14   ` Chaitanya Kulkarni
2026-06-05 18:00 ` [PATCH v7 04/14] block/cgroup: Split blkg_conf_exit() Bart Van Assche
2026-06-05 18:14   ` Chaitanya Kulkarni
2026-06-05 18:00 ` [PATCH v7 05/14] block/cgroup: Improve lock context annotations Bart Van Assche
2026-06-05 18:15   ` Chaitanya Kulkarni [this message]
2026-06-05 18:00 ` [PATCH v7 06/14] block/blk-iocost: Combine two error paths in ioc_qos_write() Bart Van Assche
2026-06-05 18:15   ` Chaitanya Kulkarni
2026-06-05 18:01 ` [PATCH v7 07/14] block/cgroup: Inline blkg_conf_{open,close}_bdev_frozen() Bart Van Assche
2026-06-05 18:15   ` Chaitanya Kulkarni
2026-06-05 18:01 ` [PATCH v7 08/14] block/crypto: Annotate the crypto functions Bart Van Assche
2026-06-05 18:01 ` [PATCH v7 09/14] block/blk-iocost: Split ioc_rqos_throttle() Bart Van Assche
2026-06-05 18:15   ` Chaitanya Kulkarni
2026-06-05 18:01 ` [PATCH v7 10/14] block/blk-iocost: Inline iocg_lock() and iocg_unlock() Bart Van Assche
2026-06-05 18:16   ` Chaitanya Kulkarni
2026-06-05 18:01 ` [PATCH v7 11/14] block/blk-mq-debugfs: Improve lock context annotations Bart Van Assche
2026-06-05 18:16   ` Chaitanya Kulkarni
2026-06-05 18:01 ` [PATCH v7 12/14] block/Kyber: Make the lock context annotations compatible with Clang Bart Van Assche
2026-06-05 18:16   ` Chaitanya Kulkarni
2026-06-05 18:01 ` [PATCH v7 13/14] block/mq-deadline: " Bart Van Assche
2026-06-05 18:16   ` Chaitanya Kulkarni
2026-06-05 18:01 ` [PATCH v7 14/14] block: Enable lock context analysis Bart Van Assche
2026-06-05 18:17   ` Chaitanya Kulkarni
2026-06-05 19:41 ` [PATCH v7 00/14] Enable lock context analysis for the block layer core Jens Axboe

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=2fc5cfcf-c277-4603-add5-faee336d5ffc@nvidia.com \
    --to=chaitanyak@nvidia.com \
    --cc=axboe@kernel.dk \
    --cc=bvanassche@acm.org \
    --cc=dlemoal@kernel.org \
    --cc=hare@kernel.org \
    --cc=hch@lst.de \
    --cc=josef@toxicpanda.com \
    --cc=linux-block@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox