diff for duplicates of <20150421195142.GX4003@linux.intel.com> diff --git a/a/1.txt b/N1/1.txt index 2336351..109afd3 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,4 +1,4 @@ -On Fri, Apr 17, 2015@10:37:15PM +0200, Christoph Hellwig wrote: +On Fri, Apr 17, 2015 at 10:37:15PM +0200, Christoph Hellwig wrote: > The real RFC is the last one which allocates the block_pc specific > data separately in the callers instead of bloating every struct > request with it. I always hated what we did, but with the upcoming diff --git a/a/content_digest b/N1/content_digest index 07cdd31..4bc1803 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -1,10 +1,14 @@ "ref\01429303042-12078-1-git-send-email-hch@lst.de\0" - "From\0willy@linux.intel.com (Matthew Wilcox)\0" - "Subject\0RFC: struct request cleanups\0" + "From\0Matthew Wilcox <willy@linux.intel.com>\0" + "Subject\0Re: RFC: struct request cleanups\0" "Date\0Tue, 21 Apr 2015 15:51:42 -0400\0" + "To\0Christoph Hellwig <hch@lst.de>\0" + "Cc\0axboe@kernel.dk" + linux-nvme@lists.infradead.org + " linux-scsi@vger.kernel.org\0" "\00:1\0" "b\0" - "On Fri, Apr 17, 2015@10:37:15PM +0200, Christoph Hellwig wrote:\n" + "On Fri, Apr 17, 2015 at 10:37:15PM +0200, Christoph Hellwig wrote:\n" "> The real RFC is the last one which allocates the block_pc specific\n" "> data separately in the callers instead of bloating every struct\n" "> request with it. I always hated what we did, but with the upcoming\n" @@ -17,4 +21,4 @@ "crackmonkeys are the ones who are trying to ship it across the network\n" instead of designing a proper network protocol. -996b4c348288cd5609dd1693d79519728bdc208449867e87d8ec968c04f3690f +2d40220bdc4fd049be6751d1bdade03bdba3d029e1fdb39c82cb10df0915a296
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.