From: Christoph Hellwig <hch@infradead.org>
To: AlanCui4080 <me@alancui.cc>
Cc: Christoph Hellwig <hch@infradead.org>,
Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org
Subject: Re: [PATCH] nvme: make providing NGUID as UUID usage less scary
Date: Mon, 11 May 2026 05:22:33 -0700 [thread overview]
Message-ID: <agHKCd_FwVEQYcvA@infradead.org> (raw)
In-Reply-To: <2MLVK7hsTb2JIM2tKTgqIg@alancui.cc>
On Mon, May 11, 2026 at 04:59:19PM +0800, AlanCui4080 wrote:
> > It is worse. For some reason the commit seems to imply the uuid
> > replaces the nguid and they can be intermixed.
>
> Which you refer to?
The original patch adding the warning.
next prev parent reply other threads:[~2026-05-11 12:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 16:36 [PATCH] nvme: make providing NGUID as UUID usage less scary AlanCui4080
2026-05-07 23:33 ` [PATCH V2] " AlanCui4080
2026-05-10 22:19 ` [PATCH] " Sagi Grimberg
2026-05-11 7:59 ` AlanCui4080
2026-05-11 8:16 ` Christoph Hellwig
2026-05-11 8:59 ` AlanCui4080
2026-05-11 9:16 ` AlanCui4080
2026-05-11 12:22 ` Christoph Hellwig [this message]
2026-05-11 14:48 ` Keith Busch
2026-05-12 6:02 ` Christoph Hellwig
2026-05-11 8:29 ` [PATCH RFC V2 RESEND] " AlanCui4080
2026-05-11 11:26 ` AlanCui4080
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=agHKCd_FwVEQYcvA@infradead.org \
--to=hch@infradead.org \
--cc=linux-nvme@lists.infradead.org \
--cc=me@alancui.cc \
--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