From: Sagi Grimberg <sagi@grimberg.me>
To: Mark O'Donovan <shiftee@posteo.net>, linux-kernel@vger.kernel.org
Cc: linux-nvme@lists.infradead.org, hch@lst.de, axboe@kernel.dk,
kbusch@kernel.org, hare@suse.de
Subject: Re: [PATCH 1/2] nvme-tcp: auth success1 msg always includes resp
Date: Tue, 29 Aug 2023 14:47:13 +0300 [thread overview]
Message-ID: <34c159dc-c534-2329-4049-7e9e8a53cd4d@grimberg.me> (raw)
In-Reply-To: <20230828212033.3244512-1-shiftee@posteo.net>
This is not nvme-tcp specific.
prefix should be "nvme-auth: ..."
I'm assuming that this passes blktests?
Nonetheless looks fine to me.
next prev parent reply other threads:[~2023-08-29 11:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-28 21:20 Mark O'Donovan
2023-08-28 21:20 ` [PATCH 2/2] nvme-tcp: always set valid seq_num in dhchap reply Mark O'Donovan
2023-08-29 11:48 ` Sagi Grimberg
2023-08-29 11:47 ` Sagi Grimberg [this message]
2023-08-29 23:37 ` [PATCH 1/2] nvme-tcp: auth success1 msg always includes resp Mark O'Donovan
2023-09-06 10:59 ` Hannes Reinecke
2023-09-12 11:39 ` 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=34c159dc-c534-2329-4049-7e9e8a53cd4d@grimberg.me \
--to=sagi@grimberg.me \
--cc=axboe@kernel.dk \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=shiftee@posteo.net \
/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
all inboxes | Powered by JetHome®