From: Keith Busch <kbusch@kernel.org>
To: Max Gurtovoy <mgurtovoy@nvidia.com>
Cc: hch@lst.de, sagi@grimberg.me, linux-nvme@lists.infradead.org,
hare@suse.de, axboe@kernel.dk, oren@nvidia.com,
ngottlieb@nvidia.com, israelr@nvidia.com
Subject: Re: [PATCH v3 0/3] nvme-fabrics: fix un-expected behaviour related to hostnqn and hostid
Date: Mon, 15 May 2023 11:15:00 -0600 [thread overview]
Message-ID: <ZGJolOAHt2AMsDEf@kbusch-mbp> (raw)
In-Reply-To: <20230512154155.38694-1-mgurtovoy@nvidia.com>
Thanks, applied to nvme-6.5.
prev parent reply other threads:[~2023-05-15 17:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-12 15:41 [PATCH v3 0/3] nvme-fabrics: fix un-expected behaviour related to hostnqn and hostid Max Gurtovoy
2023-05-12 15:41 ` [PATCH v3 1/3] nvme-fabrics: unify common code in admin and io queue connect Max Gurtovoy
2023-05-12 15:41 ` [PATCH v3 2/3] nvme-fabrics: check hostid using uuid_equal Max Gurtovoy
2023-05-12 15:41 ` [PATCH v3 3/3] nvme-fabrics: prevent overriding of existing host Max Gurtovoy
2023-05-12 20:27 ` Christoph Hellwig
2023-05-15 17:15 ` Keith Busch [this message]
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=ZGJolOAHt2AMsDEf@kbusch-mbp \
--to=kbusch@kernel.org \
--cc=axboe@kernel.dk \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=israelr@nvidia.com \
--cc=linux-nvme@lists.infradead.org \
--cc=mgurtovoy@nvidia.com \
--cc=ngottlieb@nvidia.com \
--cc=oren@nvidia.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