diff for duplicates of <6d58b9ecb0fbb23b04545bb736ca8a39@mail.gmail.com> diff --git a/a/1.txt b/N1/1.txt index 1f9dc25..a2056da 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -5,12 +5,12 @@ 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] +> From: Sathya Prakash Veerichetty [mailto:sathya.prakash@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 +> Cc: dgilbert@interlog.com; Bart Van Assche; hch@infradead.org; Kashyap > Desai; Shivasharan Srikanteshwara; Sumit Saxena; linux- -> nvme at lists.infradead.org; Peter Rivera; linux-scsi at vger.kernel.org +> nvme@lists.infradead.org; Peter Rivera; linux-scsi@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 diff --git a/a/content_digest b/N1/content_digest index 23fedc9..b0055f9 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -6,9 +6,19 @@ "ref\0e407e98c266c060412bfa8b64ded18df@mail.gmail.com\0" "ref\020180111174619.GA2860@localhost.localdomain\0" "ref\0780f280162fa01c41f15aaeb64503ffd@mail.gmail.com\0" - "From\0kashyap.desai@broadcom.com (Kashyap Desai)\0" - "Subject\0[PATCH 13/14] megaraid_sas: NVME passthru command support\0" + "From\0Kashyap Desai <kashyap.desai@broadcom.com>\0" + "Subject\0RE: [PATCH 13/14] megaraid_sas: NVME passthru command support\0" "Date\0Mon, 15 Jan 2018 17:46:05 +0530\0" + "To\0Sathya Prakash Veerichetty <sathya.prakash@broadcom.com>" + " Keith Busch <keith.busch@intel.com>\0" + "Cc\0dgilbert@interlog.com" + Bart Van Assche <Bart.VanAssche@wdc.com> + hch@infradead.org + Shivasharan Srikanteshwara <shivasharan.srikanteshwara@broadcom.com> + Sumit Saxena <sumit.saxena@broadcom.com> + linux-nvme@lists.infradead.org + Peter Rivera <peter.rivera@broadcom.com> + " linux-scsi@vger.kernel.org\0" "\00:1\0" "b\0" "This patch is not yet included because of the ongoing discussion.\n" @@ -18,12 +28,12 @@ "Thanks, Kashyap\n" "\n" "> -----Original Message-----\n" - "> From: Sathya Prakash Veerichetty [mailto:sathya.prakash at broadcom.com]\n" + "> From: Sathya Prakash Veerichetty [mailto:sathya.prakash@broadcom.com]\n" "> Sent: Thursday, January 11, 2018 11:37 PM\n" "> To: Keith Busch\n" - "> Cc: dgilbert at interlog.com; Bart Van Assche; hch at infradead.org; Kashyap\n" + "> Cc: dgilbert@interlog.com; Bart Van Assche; hch@infradead.org; Kashyap\n" "> Desai; Shivasharan Srikanteshwara; Sumit Saxena; linux-\n" - "> nvme at lists.infradead.org; Peter Rivera; linux-scsi at vger.kernel.org\n" + "> nvme@lists.infradead.org; Peter Rivera; linux-scsi@vger.kernel.org\n" "> Subject: RE: [PATCH 13/14] megaraid_sas: NVME passthru command support\n" ">\n" "> >>So even when used as a RAID member, there will be a device handle at\n" @@ -33,4 +43,4 @@ "> member drives will not have /dev/sdX entries associated with them, however\n" > for bare NVMe drives there will be associated /dev/sdX entries. -1b66831b452c9e38a8f3788bf26b3ba75864cb103bc5ad147c852a52eace086b +a539cb5ef22fbefce95889117f6533cdefb3e3f1a136a6369380836b2db67494
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.