All of lore.kernel.org
 help / color / mirror / Atom feed
From: bvanassche@acm.org (Bart Van Assche)
Subject: [PATCH 2/2] nvme: Set physical block size and optimal I/O size according to NVMe 1.4
Date: Thu, 6 Jun 2019 14:48:24 -0700	[thread overview]
Message-ID: <969c0a9c-2e5a-b609-5c3b-411f9f2bf6ca@acm.org> (raw)
In-Reply-To: <BYAPR04MB5749E9F546E6EA5415BEB20686170@BYAPR04MB5749.namprd04.prod.outlook.com>

On 6/6/19 2:42 PM, Chaitanya Kulkarni wrote:
> Looks good. One quick question though do you actually have a controller
> on which you have tested this feature ?

Hi Chaitanya,

 From the cover letter of this patch series: "These patches
compile correctly but have not been tested in any other way."

Bart.

  reply	other threads:[~2019-06-06 21:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-06 21:28 [PATCH 0/2] NVMe 1.4 Identify Namespace Support Bart Van Assche
2019-06-06 21:28 ` [PATCH 1/2] nvme: Introduce NVMe 1.4 Identify Namespace fields in struct nvme_id_ns Bart Van Assche
2019-06-06 21:40   ` Chaitanya Kulkarni
2019-06-07 15:18   ` Martin K. Petersen
2019-06-06 21:28 ` [PATCH 2/2] nvme: Set physical block size and optimal I/O size according to NVMe 1.4 Bart Van Assche
2019-06-06 21:42   ` Chaitanya Kulkarni
2019-06-06 21:48     ` Bart Van Assche [this message]
2019-06-06 21:58       ` Chaitanya Kulkarni
2019-06-07 16:42       ` Christoph Hellwig
2019-06-07 15:19   ` Martin K. Petersen
2019-06-07 16:42   ` Christoph Hellwig
2019-06-07 13:56 ` [PATCH 0/2] NVMe 1.4 Identify Namespace Support Keith Busch
2019-06-07 15:21   ` Martin K. Petersen
2019-06-07 16:26     ` Keith Busch
2019-06-07 16:44       ` 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=969c0a9c-2e5a-b609-5c3b-411f9f2bf6ca@acm.org \
    --to=bvanassche@acm.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.