From: Sagi Grimberg <sagi@grimberg.me>
To: Ma Shimiao <mashimiao.fnst@cn.fujitsu.com>, hch@lst.de
Cc: linux-kernel@vger.kernel.org, linux-nvme@lists.infradead.org
Subject: Re: [PATCH] drviers/nvme/target: fix max dup length for kstrndup
Date: Sun, 14 Jan 2018 12:34:38 +0200 [thread overview]
Message-ID: <9b9e0f7a-0d59-0630-9d53-0ffa247a5822@grimberg.me> (raw)
In-Reply-To: <20171212093639.21274-1-mashimiao.fnst@cn.fujitsu.com>
Looks good,
Reviewed-by: Sagi Grimberg <sagi@grmberg.me>
prev parent reply other threads:[~2018-01-14 10:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 9:36 [PATCH] drviers/nvme/target: fix max dup length for kstrndup Ma Shimiao
2018-01-14 10:34 ` 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=9b9e0f7a-0d59-0630-9d53-0ffa247a5822@grimberg.me \
--to=sagi@grimberg.me \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=mashimiao.fnst@cn.fujitsu.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).