From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-block@vger.kernel.org, Keith Busch <kbusch@kernel.org>,
Jens Axboe <axboe@fb.com>, Sagi Grimberg <sagi@grimberg.me>,
Chaitanya Kulkarni <kch@nvidia.com>,
linux-nvme@lists.infradead.org
Subject: Re: [GIT PULL] nvme fixes for Linux 6.16
Date: Thu, 3 Jul 2025 09:42:56 -0600 [thread overview]
Message-ID: <c88dede7-9654-43e6-bb04-47d948e7cfaf@kernel.dk> (raw)
In-Reply-To: <aGZuyPbzY__Rb8Kz@infradead.org>
On 7/3/25 5:51 AM, Christoph Hellwig wrote:
> The following changes since commit c007062188d8e402c294117db53a24b2bed2b83f:
>
> block: fix false warning in bdev_count_inflight_rw() (2025-06-26 07:34:11 -0600)
>
> are available in the Git repository at:
>
> git://git.infradead.org/nvme.git tags/nvme-6.16-2025-07-03
>
> for you to fetch changes up to d6811074203b13f715ce2480ac64c5b1c773f2a5:
>
> nvme-multipath: fix suspicious RCU usage warning (2025-07-01 08:17:02 +0200)
>
> ----------------------------------------------------------------
> nvme fixes for Linux 6.16
>
> - fix incorrect cdw15 value in passthru error logging (Alok Tiwari)
> - fix memory leak of bio integrity in nvmet (Dmitry Bogdanov)
> - refresh visible attrs after being checked (Eugen Hristev)
> - fix suspicious RCU usage warning in the multipath code (Geliang Tang)
> - correctly account for namespace head reference counter (Nilay Shroff)
Pulled, thanks.
--
Jens Axboe
next prev parent reply other threads:[~2025-07-03 15:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-03 11:51 [GIT PULL] nvme fixes for Linux 6.16 Christoph Hellwig
2025-07-03 15:42 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-07-17 11:36 Christoph Hellwig
2025-07-17 11:59 ` 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=c88dede7-9654-43e6-bb04-47d948e7cfaf@kernel.dk \
--to=axboe@kernel.dk \
--cc=axboe@fb.com \
--cc=hch@infradead.org \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--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;
as well as URLs for NNTP newsgroup(s).