From: hch@lst.de (Christoph Hellwig)
Subject: [PATCH 1/2] nvme: move command size checks to the core
Date: Wed, 1 May 2019 15:18:21 +0200 [thread overview]
Message-ID: <20190501131821.GA1402@lst.de> (raw)
In-Reply-To: <SN6PR04MB45274A0053D67600108FA903863A0@SN6PR04MB4527.namprd04.prod.outlook.com>
On Tue, Apr 30, 2019@09:30:26PM +0000, Chaitanya Kulkarni wrote:
> Looks good. Just one question about _nvme_check_size(), is there any
> significance for one _ over __ ?
None. I have just copied over what we had before.
prev parent reply other threads:[~2019-05-01 13:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-30 15:38 [PATCH 1/2] nvme: move command size checks to the core Christoph Hellwig
2019-04-30 15:38 ` [PATCH 2/2] nvme: mark nvme_core_init and nvme_core_exit static Christoph Hellwig
2019-04-30 15:52 ` Keith Busch
2019-04-30 16:57 ` Bart Van Assche
2019-04-30 21:30 ` Chaitanya Kulkarni
2019-04-30 15:51 ` [PATCH 1/2] nvme: move command size checks to the core Keith Busch
2019-04-30 16:58 ` Bart Van Assche
2019-04-30 21:30 ` Chaitanya Kulkarni
2019-05-01 13:18 ` 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=20190501131821.GA1402@lst.de \
--to=hch@lst.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