diff for duplicates of <20170829082523.GA10487@lst.de> diff --git a/a/1.txt b/N1/1.txt index 9432f55..6571ab8 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,7 +1,7 @@ -On Mon, Aug 28, 2017 at 01:21:20PM -0700, J Freyensee wrote: -> > > �����horrible.��One idea would be to rename the current struct nvme_ns -> > > �����to struct nvme_ns_link or similar and use the nvme_ns name for the -> > > �����new structure.��But that would involve a lot of churn. +On Mon, Aug 28, 2017@01:21:20PM -0700, J Freyensee wrote: +> > > ?????horrible.??One idea would be to rename the current struct nvme_ns +> > > ?????to struct nvme_ns_link or similar and use the nvme_ns name for the +> > > ?????new structure.??But that would involve a lot of churn. > > > > maybe nvme_ns_primary? > diff --git a/a/content_digest b/N1/content_digest index a13f918..ec945a8 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -2,22 +2,15 @@ "ref\020170823175815.3646-8-hch@lst.de\0" "ref\0bee7c6c3-bf6b-8f7e-ad8f-fd5e238a94ef@grimberg.me\0" "ref\01503951680.4860.3.camel@linux.intel.com\0" - "From\0Christoph Hellwig <hch@lst.de>\0" - "Subject\0Re: [PATCH 07/10] nvme: track shared namespaces\0" + "From\0hch@lst.de (Christoph Hellwig)\0" + "Subject\0[PATCH 07/10] nvme: track shared namespaces\0" "Date\0Tue, 29 Aug 2017 10:25:23 +0200\0" - "To\0J Freyensee <james_p_freyensee@linux.intel.com>\0" - "Cc\0Sagi Grimberg <sagi@grimberg.me>" - Christoph Hellwig <hch@lst.de> - Jens Axboe <axboe@kernel.dk> - Keith Busch <keith.busch@intel.com> - linux-block@vger.kernel.org - " linux-nvme@lists.infradead.org\0" "\00:1\0" "b\0" - "On Mon, Aug 28, 2017 at 01:21:20PM -0700, J Freyensee wrote:\n" - "> > > \303\257\302\277\302\275\303\257\302\277\302\275\303\257\302\277\302\275\303\257\302\277\302\275\303\257\302\277\302\275horrible.\303\257\302\277\302\275\303\257\302\277\302\275One idea would be to rename the current struct nvme_ns\n" - "> > > \303\257\302\277\302\275\303\257\302\277\302\275\303\257\302\277\302\275\303\257\302\277\302\275\303\257\302\277\302\275to struct nvme_ns_link or similar and use the nvme_ns name for the\n" - "> > > \303\257\302\277\302\275\303\257\302\277\302\275\303\257\302\277\302\275\303\257\302\277\302\275\303\257\302\277\302\275new structure.\303\257\302\277\302\275\303\257\302\277\302\275But that would involve a lot of churn.\n" + "On Mon, Aug 28, 2017@01:21:20PM -0700, J Freyensee wrote:\n" + "> > > ?????horrible.??One idea would be to rename the current struct nvme_ns\n" + "> > > ?????to struct nvme_ns_link or similar and use the nvme_ns name for the\n" + "> > > ?????new structure.??But that would involve a lot of churn.\n" "> > \n" "> > maybe nvme_ns_primary?\n" "> \n" @@ -36,4 +29,4 @@ "I suspect the only way that would make my taste happy is to call\n" this new one nvme_ns, but that would lead to a lot of churn. -cfb4861f54eb0c44e5829704930c875092d60d00526600d2c789d3a7e5835d21 +b49c564bddf13ffd70b5f48809942449cf9ee03b0fbff5d7b532014c395f61fe
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.