From: Christoph Hellwig <hch@lst.de>
To: Keith Busch <kbusch@meta.com>
Cc: linux-nvme@lists.infradead.org, hch@lst.de, sagi@grimberg.me,
mlombard@redhat.com, hare@suse.de, shinichiro.kawasaki@wdc.com,
Keith Busch <kbusch@kernel.org>
Subject: Re: [PATCH-RFC 0/5] nvme: fix initialization memleak
Date: Tue, 4 Jun 2024 06:24:10 +0200 [thread overview]
Message-ID: <20240604042410.GB28748@lst.de> (raw)
In-Reply-To: <20240603230524.3854115-1-kbusch@meta.com>
On Mon, Jun 03, 2024 at 04:05:18PM -0700, Keith Busch wrote:
> From: Keith Busch <kbusch@kernel.org>
>
> The pci driver is the only one runtime tested. Everything else is
> compile tested, except for apple.
The highlevel flow looks good to me. FYI, TCP/loop and to a lesser
extent the other fabrics transports can be exercised using blktests
nicely.
next prev parent reply other threads:[~2024-06-04 4:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-03 23:05 [PATCH-RFC 0/5] nvme: fix initialization memleak Keith Busch
2024-06-03 23:05 ` [PATCH-RFC 1/5] nvme: apple: fix device reference counting Keith Busch
2024-06-03 23:17 ` Keith Busch
2024-06-03 23:05 ` [PATCH-RFC 2/5] nvme: tcp: split controller bringup handling Keith Busch
2024-06-04 0:35 ` Caleb Sander
2024-06-04 2:44 ` Keith Busch
2024-06-04 4:23 ` Christoph Hellwig
2024-06-04 6:47 ` Hannes Reinecke
2024-06-03 23:05 ` [PATCH-RFC 3/5] nvme: rdma: " Keith Busch
2024-06-03 23:05 ` [PATCH-RFC 4/5] nvme: fc: " Keith Busch
2024-06-03 23:05 ` [PATCH-RFC 5/5] nvme: split device add from initialzation Keith Busch
2024-06-04 4:24 ` Christoph Hellwig [this message]
2024-06-04 14:51 ` [PATCH-RFC 0/5] nvme: fix initialization memleak Sagi Grimberg
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=20240604042410.GB28748@lst.de \
--to=hch@lst.de \
--cc=hare@suse.de \
--cc=kbusch@kernel.org \
--cc=kbusch@meta.com \
--cc=linux-nvme@lists.infradead.org \
--cc=mlombard@redhat.com \
--cc=sagi@grimberg.me \
--cc=shinichiro.kawasaki@wdc.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox