diff for duplicates of <20160609134603.GA29820@lst.de> diff --git a/a/1.txt b/N1/1.txt index 93130a8..0a52e2c 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,4 +1,4 @@ -On Wed, Jun 08, 2016 at 09:36:15PM -0700, Nicholas A. Bellinger wrote: +On Wed, Jun 08, 2016@09:36:15PM -0700, Nicholas A. Bellinger wrote: > The configfs ABI should not dictate a single backend use-case. And it doesn't. I actually had a file backend implemented to @@ -16,6 +16,6 @@ PRs are a useful feature on the road map. However we need a separate pluggable backend anyway for distributed backends like RBD or Bart's DLM implementation. Also the current LIO PR implementation will need a lot of work to be usable for NVMe while actually following the -spec in all it's details and to be power ѕafe. The right way to +spec in all it's details and to be power ?afe. The right way to go here is a PR API that allows different backends, and the existing LIO one might be one of them after it's got the needed attention. diff --git a/a/content_digest b/N1/content_digest index 0037286..4f0669d 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -5,22 +5,12 @@ "ref\020160608121932.GA31316@lst.de\0" "ref\0575819BB.7010209@lightbits.io\0" "ref\01465446975.5365.123.camel@haakon3.risingtidesystems.com\0" - "From\0Christoph Hellwig <hch@lst.de>\0" - "Subject\0Re: NVMe over Fabrics target implementation\0" + "From\0hch@lst.de (Christoph Hellwig)\0" + "Subject\0NVMe over Fabrics target implementation\0" "Date\0Thu, 9 Jun 2016 15:46:03 +0200\0" - "To\0Nicholas A. Bellinger <nab@linux-iscsi.org>\0" - "Cc\0Sagi Grimberg <sagi@lightbits.io>" - Christoph Hellwig <hch@lst.de> - axboe@kernel.dk - linux-block@vger.kernel.org - linux-scsi <linux-scsi@vger.kernel.org> - linux-kernel@vger.kernel.org - linux-nvme@lists.infradead.org - keith.busch@intel.com - " target-devel <target-devel@vger.kernel.org>\0" "\00:1\0" "b\0" - "On Wed, Jun 08, 2016 at 09:36:15PM -0700, Nicholas A. Bellinger wrote:\n" + "On Wed, Jun 08, 2016@09:36:15PM -0700, Nicholas A. Bellinger wrote:\n" "> The configfs ABI should not dictate a single backend use-case.\n" "\n" "And it doesn't. I actually had a file backend implemented to\n" @@ -38,8 +28,8 @@ "pluggable backend anyway for distributed backends like RBD or Bart's\n" "DLM implementation. Also the current LIO PR implementation will need\n" "a lot of work to be usable for NVMe while actually following the\n" - "spec in all it's details and to be power \321\225afe. The right way to\n" + "spec in all it's details and to be power ?afe. The right way to\n" "go here is a PR API that allows different backends, and the existing\n" LIO one might be one of them after it's got the needed attention. -c25222837a9ddae6bf257c4f47076b1b5ac9c4b5b078b46c9d154fbbd1192e46 +f32f9284d44c11a137679dd7030527678f47105a0334231a2431346e795c16d1
diff --git a/a/1.txt b/N2/1.txt index 93130a8..e605704 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -19,3 +19,7 @@ a lot of work to be usable for NVMe while actually following the spec in all it's details and to be power ѕafe. The right way to go here is a PR API that allows different backends, and the existing LIO one might be one of them after it's got the needed attention. +-- +To unsubscribe from this list: send the line "unsubscribe linux-scsi" in +the body of a message to majordomo@vger.kernel.org +More majordomo info at http://vger.kernel.org/majordomo-info.html diff --git a/a/content_digest b/N2/content_digest index 0037286..c86df21 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -40,6 +40,10 @@ "a lot of work to be usable for NVMe while actually following the\n" "spec in all it's details and to be power \321\225afe. The right way to\n" "go here is a PR API that allows different backends, and the existing\n" - LIO one might be one of them after it's got the needed attention. + "LIO one might be one of them after it's got the needed attention.\n" + "--\n" + "To unsubscribe from this list: send the line \"unsubscribe linux-scsi\" in\n" + "the body of a message to majordomo@vger.kernel.org\n" + More majordomo info at http://vger.kernel.org/majordomo-info.html -c25222837a9ddae6bf257c4f47076b1b5ac9c4b5b078b46c9d154fbbd1192e46 +7a17a6d183562a68e6ecb88601692cf734e8d4a30c5f87340e2ea45f22d3960d
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.