From: "Nadolski, Edmund" <edmund.nadolski@intel.com>
To: kbusch@kernel.org
Cc: linux-nvme@lists.infradead.org
Subject: Re: [PATCH v3 1/1] nvme: remove unused return code from nvme_alloc_ns
Date: Mon, 16 Dec 2019 08:39:09 -0700 [thread overview]
Message-ID: <4cc7d687-fbd5-45a4-61c8-91aa97728f63@intel.com> (raw)
In-Reply-To: <20191128073015.GA27403@infradead.org>
On 11/28/2019 12:30 AM, Christoph Hellwig wrote:
> Looks good,
>
> Reviewed-by: Christoph Hellwig <hch@lst.de>
Keith, all... any further feedback/comment?
Thanks,
Ed
_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
prev parent reply other threads:[~2019-12-16 15:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-27 17:17 [PATCH v3 0/1] A few code cleanups Edmund Nadolski
2019-11-27 17:17 ` [PATCH v3 1/1] nvme: remove unused return code from nvme_alloc_ns Edmund Nadolski
2019-11-28 7:30 ` Christoph Hellwig
2019-12-16 15:39 ` Nadolski, Edmund [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=4cc7d687-fbd5-45a4-61c8-91aa97728f63@intel.com \
--to=edmund.nadolski@intel.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).