From: Sagi Grimberg <sagi@grimberg.me>
To: Markus Elfring <Markus.Elfring@web.de>,
linux-nvme@lists.infradead.org, Christoph Hellwig <hch@lst.de>
Cc: YueHaibing <yuehaibing@huawei.com>,
zhong jiang <zhongjiang@huawei.com>,
kernel-janitors@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] nvmet: Use PTR_ERR_OR_ZERO() in nvmet_init_discovery()
Date: Fri, 6 Sep 2019 11:13:47 -0700 [thread overview]
Message-ID: <655dc338-b7c9-cd01-1b3e-59fe34c87f6a@grimberg.me> (raw)
In-Reply-To: <b35ec629-f75f-2eee-1db1-98874f486258@web.de>
Reviewed-by: Sagi Grimberg <sagi@grimberg.me>
applied to nvme-5.4
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
prev parent reply other threads:[~2019-09-06 18:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-06 18:00 [PATCH] nvmet: Use PTR_ERR_OR_ZERO() in nvmet_init_discovery() Markus Elfring
2019-09-06 18:13 ` Sagi Grimberg [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=655dc338-b7c9-cd01-1b3e-59fe34c87f6a@grimberg.me \
--to=sagi@grimberg.me \
--cc=Markus.Elfring@web.de \
--cc=hch@lst.de \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=yuehaibing@huawei.com \
--cc=zhongjiang@huawei.com \
/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).