diff for duplicates of <20170808040449.GE842@localhost.localdomain> diff --git a/a/1.txt b/N1/1.txt index a19b06b..8565faf 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,11 +1,11 @@ -On Mon, Aug 07, 2017@08:45:25AM -0700, James Bottomley wrote: -> On Mon, 2017-08-07@20:01 +0530, Kashyap Desai wrote: +On Mon, Aug 07, 2017 at 08:45:25AM -0700, James Bottomley wrote: +> On Mon, 2017-08-07 at 20:01 +0530, Kashyap Desai wrote: > > > > We have to attempt this use case and see how it behaves. I have not > > tried this, so not sure if things are really bad or just some tuning > > may be helpful. I will revert back to you on this. > > -> > I understood request as -??We need some udev rules to be working well +> > I understood request as - We need some udev rules to be working well > > for *same* NVME drives if it is behind <mpt3sas> or native <nvme>. > > Example - If user has OS installed on NVME drive which is behind > > <mpt3sas> driver as SCSI disk should be able to boot if he/she hooked diff --git a/a/content_digest b/N1/content_digest index ee28db3..ce581ae 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -6,19 +6,31 @@ "ref\01502115492.2841.20.camel@HansenPartnership.com\0" "ref\0da1e0ded0c7d4bab1cfa0850488c8fb7@mail.gmail.com\0" "ref\01502120725.2841.28.camel@HansenPartnership.com\0" - "From\0keith.busch@intel.com (Keith Busch)\0" - "Subject\0[PATCH v2 00/13] mpt3sas driver NVMe support:\0" + "From\0Keith Busch <keith.busch@intel.com>\0" + "Subject\0Re: [PATCH v2 00/13] mpt3sas driver NVMe support:\0" "Date\0Tue, 8 Aug 2017 00:04:49 -0400\0" + "To\0James Bottomley <James.Bottomley@hansenpartnership.com>\0" + "Cc\0Kashyap Desai <kashyap.desai@broadcom.com>" + Christoph Hellwig <hch@infradead.org> + Hannes Reinecke <hare@suse.de> + Sreekanth Reddy <sreekanth.reddy@broadcom.com> + linux-scsi@vger.kernel.org + Chaitra Basappa <chaitra.basappa@broadcom.com> + Suganath Prabu Subramani <suganath-prabu.subramani@broadcom.com> + Sathya Prakash Veerichetty <sathya.prakash@broadcom.com> + linux-kernel@vger.kernel.org + linux-nvme@lists.infradead.org + " martin.petersen@oracle.com\0" "\00:1\0" "b\0" - "On Mon, Aug 07, 2017@08:45:25AM -0700, James Bottomley wrote:\n" - "> On Mon, 2017-08-07@20:01 +0530, Kashyap Desai wrote:\n" + "On Mon, Aug 07, 2017 at 08:45:25AM -0700, James Bottomley wrote:\n" + "> On Mon, 2017-08-07 at 20:01 +0530, Kashyap Desai wrote:\n" "> > \n" "> > We have to attempt this use case and see how it behaves. I have not\n" "> > tried this, so not sure if things are really bad or just some tuning\n" "> > may be helpful. I will revert back to you on this.\n" "> > \n" - "> > I understood request as -??We need some udev rules to be working well\n" + "> > I understood request as -\302\240\302\240We need some udev rules to be working well\n" "> > for *same* NVME drives if it is behind <mpt3sas> or native <nvme>.\n" "> > Example - If user has OS installed on NVME drive which is behind\n" "> > <mpt3sas> driver as SCSI disk should be able to boot if he/she hooked\n" @@ -32,4 +44,4 @@ "effort if they have the driver implement NVME_IOCTL_ADMIN_COMMAND, and\n" then have their driver build the MPI NVMe Encapsulated Request from that. -bf0d27c7e8a1f05f26c611097af4783593fc53d8d30b4deae978c2437fddaa4c +96979c55861ffe51bb2c93d2c22df3c249e13cf626b4de1ef7ed072aafe0dfb8
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.