From: kashyap.desai@broadcom.com (Kashyap Desai)
Subject: [PATCH 13/14] megaraid_sas: NVME passthru command support
Date: Mon, 15 Jan 2018 17:46:05 +0530 [thread overview]
Message-ID: <6d58b9ecb0fbb23b04545bb736ca8a39@mail.gmail.com> (raw)
In-Reply-To: <780f280162fa01c41f15aaeb64503ffd@mail.gmail.com>
This patch is not yet included because of the ongoing discussion.
Chris H, Martin et all - How are we moving forward with this patch ?
Thanks, Kashyap
> -----Original Message-----
> From: Sathya Prakash Veerichetty [mailto:sathya.prakash at broadcom.com]
> Sent: Thursday, January 11, 2018 11:37 PM
> To: Keith Busch
> Cc: dgilbert at interlog.com; Bart Van Assche; hch at infradead.org; Kashyap
> Desai; Shivasharan Srikanteshwara; Sumit Saxena; linux-
> nvme at lists.infradead.org; Peter Rivera; linux-scsi at vger.kernel.org
> Subject: RE: [PATCH 13/14] megaraid_sas: NVME passthru command support
>
> >>So even when used as a RAID member, there will be a device handle at
> /dev/sdX for each NVMe device the megaraid controller manages?
> In megaraid controller, you can expose bare NVMe drives and RAID volumes
> created out of NVMe drives, when the RAID volume is created underlying
> member drives will not have /dev/sdX entries associated with them, however
> for bare NVMe drives there will be associated /dev/sdX entries.
next prev parent reply other threads:[~2018-01-15 12:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-05 13:35 [PATCH 13/14] megaraid_sas: NVME passthru command support Shivasharan S
2018-01-08 10:05 ` Christoph Hellwig
2018-01-09 16:37 ` Kashyap Desai
2018-01-09 16:45 ` Christoph Hellwig
2018-01-09 20:50 ` Douglas Gilbert
2018-01-09 23:23 ` Keith Busch
2018-01-10 9:32 ` Kashyap Desai
2018-01-10 10:03 ` Kashyap Desai
2018-01-10 16:22 ` Bart Van Assche
2018-01-10 20:06 ` Douglas Gilbert
2018-01-10 22:14 ` Sathya Prakash Veerichetty
2018-01-11 17:46 ` Keith Busch
2018-01-11 18:07 ` Sathya Prakash Veerichetty
2018-01-15 12:16 ` Kashyap Desai [this message]
2018-01-16 3:06 ` Martin K. Petersen
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=6d58b9ecb0fbb23b04545bb736ca8a39@mail.gmail.com \
--to=kashyap.desai@broadcom.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