diff for duplicates of <20170925161155.GC8463@localhost.localdomain> diff --git a/a/1.txt b/N1/1.txt index 94bf1ff..14795eb 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,4 +1,4 @@ -On Mon, Sep 25, 2017 at 03:40:29PM +0200, Christoph Hellwig wrote: +On Mon, Sep 25, 2017@03:40:29PM +0200, Christoph Hellwig wrote: > Introduce a new struct nvme_ns_head [1] that holds information about > an actual namespace, unlike struct nvme_ns, which only holds the > per-controller namespace information. For private namespaces there @@ -16,8 +16,8 @@ On Mon, Sep 25, 2017 at 03:40:29PM +0200, Christoph Hellwig wrote: > 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. > -> Signed-off-by: Christoph Hellwig <hch@lst.de> +> Signed-off-by: Christoph Hellwig <hch at lst.de> Looks good; I can live with 'nvme_ns_head'. -Reviewed-by: Keith Busch <keith.busch@intel.com> +Reviewed-by: Keith Busch <keith.busch at intel.com> diff --git a/a/content_digest b/N1/content_digest index 6f49d3b..9331b82 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,16 +1,11 @@ "ref\020170925134031.10548-1-hch@lst.de\0" "ref\020170925134031.10548-8-hch@lst.de\0" - "From\0Keith Busch <keith.busch@intel.com>\0" - "Subject\0Re: [PATCH 7/9] nvme: track shared namespaces\0" + "From\0keith.busch@intel.com (Keith Busch)\0" + "Subject\0[PATCH 7/9] nvme: track shared namespaces\0" "Date\0Mon, 25 Sep 2017 10:11:55 -0600\0" - "To\0Christoph Hellwig <hch@lst.de>\0" - "Cc\0Jens Axboe <axboe@kernel.dk>" - Sagi Grimberg <sagi@grimberg.me> - linux-nvme@lists.infradead.org - " linux-block@vger.kernel.org\0" "\00:1\0" "b\0" - "On Mon, Sep 25, 2017 at 03:40:29PM +0200, Christoph Hellwig wrote:\n" + "On Mon, Sep 25, 2017@03:40:29PM +0200, Christoph Hellwig wrote:\n" "> Introduce a new struct nvme_ns_head [1] that holds information about\n" "> an actual namespace, unlike struct nvme_ns, which only holds the\n" "> per-controller namespace information. For private namespaces there\n" @@ -28,10 +23,10 @@ "> 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" - "> Signed-off-by: Christoph Hellwig <hch@lst.de>\n" + "> Signed-off-by: Christoph Hellwig <hch at lst.de>\n" "\n" "Looks good; I can live with 'nvme_ns_head'.\n" "\n" - Reviewed-by: Keith Busch <keith.busch@intel.com> + Reviewed-by: Keith Busch <keith.busch at intel.com> -2fbde9874b4714f800f7c13d8a6412e45c60c6c8154f8d314c6d989271cfc8ad +2aecf36fc0f52f38f8005fca08a83507ebd2e4c16dbc6ffc5027ad0f869c2ab1
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.