From: jthumshirn@suse.de (Johannes Thumshirn)
Subject: [PATCH 1/2] nvme-fabrics: Fix memory leak when parsing host ID option
Date: Fri, 12 Jan 2018 11:16:57 +0100 [thread overview]
Message-ID: <20180112101656.cscb4rhv3dj264cc@linux-x5ow.site> (raw)
In-Reply-To: <20180111213800.1767-1-roland@kernel.org>
Looks good,
Reviewed-by: Johannes Thumshirn <jthumshirn at suse.de>
Do you mind fixing the same pattern on:
- NVMF_OPT_TRANSPORT
- NVMF_OPT_NQN
- NVMF_OPT_TRADDR
- NVMF_OPT_TRSVCID
- NVMF_OPT_HOST_TRADDR
as well?
Thanks,
Johannes
--
Johannes Thumshirn Storage
jthumshirn at suse.de +49 911 74053 689
SUSE LINUX GmbH, Maxfeldstr. 5, 90409 N?rnberg
GF: Felix Imend?rffer, Jane Smithard, Graham Norton
HRB 21284 (AG N?rnberg)
Key fingerprint = EC38 9CAB C2C4 F25D 8600 D0D0 0393 969D 2D76 0850
next prev parent reply other threads:[~2018-01-12 10:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-11 21:38 [PATCH 1/2] nvme-fabrics: Fix memory leak when parsing host ID option Roland Dreier
2018-01-12 10:16 ` Johannes Thumshirn [this message]
2018-01-12 20:00 ` Roland Dreier
2018-01-14 9:27 ` Sagi Grimberg
2018-01-15 7:44 ` Johannes Thumshirn
2018-01-15 15:23 ` Christoph Hellwig
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=20180112101656.cscb4rhv3dj264cc@linux-x5ow.site \
--to=jthumshirn@suse.de \
/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