From: Keith Busch <kbusch@kernel.org>
To: Marco Elver <elver@google.com>
Cc: Nilay Shroff <nilay@linux.ibm.com>,
linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
hch@lst.de, sagi@grimberg.me, axboe@fb.com, bvanassche@acm.org,
gjoyce@linux.ibm.com
Subject: Re: [PATCH v4 00/20] Support Clang context analysis for NVMe host drivers
Date: Wed, 29 Jul 2026 08:06:34 -0600 [thread overview]
Message-ID: <amoI6iw_e3DeACKD@kbusch-mbp> (raw)
In-Reply-To: <CANpmjNN2+m7O206xFDRwyCoihsEr9J972pOFSa5Uc=xx6kkTHw@mail.gmail.com>
On Wed, Jul 29, 2026 at 11:03:52AM +0200, Marco Elver wrote:
> On Tue, 28 Jul 2026 at 19:41, Keith Busch <kbusch@kernel.org> wrote:
> >
> > It doesn't look like there's a single source for updating list.h, so any
> > concern with taking this series through the nvme tree?
>
> I think that's fine; conflicts should appear in -next, but I don't see any yet.
Sounds good, applied to nvme-7.3!
next prev parent reply other threads:[~2026-07-29 14:06 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 11:54 [PATCH v4 00/20] Support Clang context analysis for NVMe host drivers Nilay Shroff
2026-07-13 11:54 ` [PATCH v4 01/20] list: introduce LIST_HEAD_GUARDED Nilay Shroff
2026-07-22 12:15 ` Christoph Hellwig
2026-07-13 11:54 ` [PATCH v4 02/20] list: Permit context-unguarded access with list_empty_careful() Nilay Shroff
2026-07-22 12:15 ` Christoph Hellwig
2026-07-13 11:54 ` [PATCH v4 03/20] nvme: update nvme_passthru_end() signature Nilay Shroff
2026-07-13 11:54 ` [PATCH v4 04/20] nvme: add context annotations for nvme_passthru_{start|stop} Nilay Shroff
2026-07-13 11:54 ` [PATCH v4 05/20] nvme: add context annotations for nvme_ns_head::srcu Nilay Shroff
2026-07-13 11:54 ` [PATCH v4 06/20] nvme: remove redundant initialization of nvme_ns_head::requeue_list Nilay Shroff
2026-07-22 12:15 ` Christoph Hellwig
2026-07-13 11:54 ` [PATCH v4 07/20] nvme: add context annotations for nvme_ns_head::requeue_list Nilay Shroff
2026-07-22 12:16 ` Christoph Hellwig
2026-07-13 11:54 ` [PATCH v4 08/20] nvme: add context annotations for nvme_ns_head::current_path Nilay Shroff
2026-07-22 12:16 ` Christoph Hellwig
2026-07-13 11:54 ` [PATCH v4 09/20] nvme: add context annotations for nvme_dev::shutdown_lock Nilay Shroff
2026-07-13 11:54 ` [PATCH v4 10/20] nvme: remove redundant initialization of delayed_removal_secs Nilay Shroff
2026-07-22 12:16 ` Christoph Hellwig
2026-07-13 11:54 ` [PATCH v4 11/20] nvme: add context annotations for nvme_subsystem::lock Nilay Shroff
2026-07-22 12:17 ` Christoph Hellwig
2026-07-13 11:54 ` [PATCH v4 12/20] nvme: add context annotations for nvme_ctrl::ana_lock Nilay Shroff
2026-07-13 11:54 ` [PATCH v4 13/20] nvme: add context annotations for nvme_subsystems_lock Nilay Shroff
2026-07-22 12:18 ` Christoph Hellwig
2026-07-13 11:54 ` [PATCH v4 14/20] nvme: add context annotations in fabric.c Nilay Shroff
2026-07-13 11:54 ` [PATCH v4 15/20] nvme: add context annotations for nvme_queue::sq_lock Nilay Shroff
2026-07-13 11:54 ` [PATCH v4 16/20] nvme: add context annotations in rdma.c Nilay Shroff
2026-07-22 12:19 ` Christoph Hellwig
2026-07-13 11:54 ` [PATCH v4 17/20] nvme: fix context analysis warning " Nilay Shroff
2026-07-22 12:20 ` Christoph Hellwig
2026-07-13 11:54 ` [PATCH v4 18/20] nvme: add context annotations in tcp.c Nilay Shroff
2026-07-22 12:20 ` Christoph Hellwig
2026-07-13 11:54 ` [PATCH v4 19/20] nvme: fix context analysis warning " Nilay Shroff
2026-07-22 12:20 ` Christoph Hellwig
2026-07-13 11:54 ` [PATCH v4 20/20] nvme: enable context analysis support for nvme host driver Nilay Shroff
2026-07-20 13:22 ` [PATCH v4 00/20] Support Clang context analysis for NVMe host drivers Marco Elver
2026-07-28 17:41 ` Keith Busch
2026-07-29 9:03 ` Marco Elver
2026-07-29 14:06 ` Keith Busch [this message]
2026-07-29 21:40 ` Marco Elver
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=amoI6iw_e3DeACKD@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=axboe@fb.com \
--cc=bvanassche@acm.org \
--cc=elver@google.com \
--cc=gjoyce@linux.ibm.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=nilay@linux.ibm.com \
--cc=sagi@grimberg.me \
/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