From: Christoph Hellwig <hch@lst.de>
To: Hannes Reinecke <hare@suse.de>
Cc: Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Keith Busch <kbusch@kernel.org>,
linux-nvme@lists.infradead.org, Mark Lehrer <mark.lehrer@wdc.com>
Subject: Re: [PATCH] nvme-fabrics: clarify AUTHREQ result handling
Date: Sun, 8 Jan 2023 19:21:36 +0100 [thread overview]
Message-ID: <20230108182136.GB25544@lst.de> (raw)
In-Reply-To: <20221208074920.43828-1-hare@suse.de>
Thanks,
applied to nvme-6.3.
prev parent reply other threads:[~2023-01-08 18:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 7:49 [PATCH] nvme-fabrics: clarify AUTHREQ result handling Hannes Reinecke
2022-12-08 10:35 ` Sagi Grimberg
2023-01-08 18:21 ` Christoph Hellwig [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=20230108182136.GB25544@lst.de \
--to=hch@lst.de \
--cc=hare@suse.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mark.lehrer@wdc.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