From: Keith Busch <kbusch@kernel.org>
To: Klaus Jensen <its@irrelevant.dk>
Cc: qemu-devel@nongnu.org, Jesper Devantier <foss@defmacro.it>,
qemu-block@nongnu.org, Klaus Jensen <k.jensen@samsung.com>,
Alan Adamson <alan.adamson@oracle.com>
Subject: Re: [PATCH] hw/nvme: fix attachment of private namespaces
Date: Tue, 8 Apr 2025 11:23:20 +0100 [thread overview]
Message-ID: <Z_T5GLESR42edzTV@kbusch-mbp> (raw)
In-Reply-To: <20250408-fix-private-ns-v1-1-28e169b6b60b@samsung.com>
On Tue, Apr 08, 2025 at 12:20:46PM +0200, Klaus Jensen wrote:
> From: Klaus Jensen <k.jensen@samsung.com>
>
> Fix regression when attaching private namespaces that gets attached to
> the wrong controller.
>
> Keep track of the original controller "owner" of private namespaces, and
> only attach if this matches on controller enablement.
Looks good.
Reviewed-by: Keith Busch <kbusch@kernel.org>
next prev parent reply other threads:[~2025-04-08 10:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 10:20 [PATCH] hw/nvme: fix attachment of private namespaces Klaus Jensen
2025-04-08 10:23 ` Keith Busch [this message]
2025-04-08 16:41 ` alan.adamson
2025-04-08 18:56 ` Philippe Mathieu-Daudé
2025-04-09 6:36 ` Klaus Jensen
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=Z_T5GLESR42edzTV@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=alan.adamson@oracle.com \
--cc=foss@defmacro.it \
--cc=its@irrelevant.dk \
--cc=k.jensen@samsung.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).