From: Christoph Hellwig <hch@infradead.org>
To: "Engel, Amit" <Amit.Engel@dell.com>
Cc: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
Sagi Grimberg <sagi@grimberg.me>
Subject: Re: parse nvme connect Linux error codes properly
Date: Mon, 1 Aug 2022 11:35:58 -0700 [thread overview]
Message-ID: <YugdDtiK59xT4K90@infradead.org> (raw)
In-Reply-To: <CO1PR19MB488539073167D496A9A7D991EE9A9@CO1PR19MB4885.namprd19.prod.outlook.com>
On Mon, Aug 01, 2022 at 04:20:44PM +0000, Engel, Amit wrote:
> I can provide a simple fix for your review if you have no comments to the above analysis
Yes, please send the fix.
next prev parent reply other threads:[~2022-08-01 18:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 16:20 parse nvme connect Linux error codes properly Engel, Amit
2022-08-01 18:35 ` Christoph Hellwig [this message]
2022-08-01 18:41 ` Engel, Amit
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=YugdDtiK59xT4K90@infradead.org \
--to=hch@infradead.org \
--cc=Amit.Engel@dell.com \
--cc=linux-nvme@lists.infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.