From: hch@infradead.org (Christoph Hellwig)
Subject: [PATCH] nvmet: remove unreachable code
Date: Tue, 9 Oct 2018 09:50:12 -0700 [thread overview]
Message-ID: <20181009165012.GA2126@infradead.org> (raw)
In-Reply-To: <20180823025845.13150-1-chaitanya.kulkarni@wdc.com>
On Wed, Aug 22, 2018@07:58:45PM -0700, Chaitanya Kulkarni wrote:
> Get rid of the unreachable code in the nvmet_parse_discovery_cmd().
> Keep the error message identical to the admin-cmd.c and io-cmd*.c
>
> Signed-off-by: Chaitanya Kulkarni <chaitanya.kulkarni at wdc.com>
Thanks,
applied to nvme-4.20.
prev parent reply other threads:[~2018-10-09 16:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-23 2:58 [PATCH] nvmet: remove unreachable code Chaitanya Kulkarni
2018-10-09 16:50 ` Christoph Hellwig [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=20181009165012.GA2126@infradead.org \
--to=hch@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 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.