All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <20180719162924.GA23917@lst.de>

diff --git a/a/1.txt b/N1/1.txt
index f09222f..3f8cc8f 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,6 +1,6 @@
-On Thu, Jul 19, 2018 at 10:22:40AM -0600, Keith Busch wrote:
-> On Thu, Jul 19, 2018 at 04:04:46PM +0000, Bart Van Assche wrote:
-> > On Thu, 2018-07-19 at 09:56 -0600, Keith Busch wrote:
+On Thu, Jul 19, 2018@10:22:40AM -0600, Keith Busch wrote:
+> On Thu, Jul 19, 2018@04:04:46PM +0000, Bart Van Assche wrote:
+> > On Thu, 2018-07-19@09:56 -0600, Keith Busch wrote:
 > > > Even some scsi drivers are susceptible to losing their requests with the
 > > > reverted behavior: take virtio-scsi for example, which returns RESET_TIMER
 > > > from it's timeout handler. With the behavior everyone seems to want,
@@ -8,7 +8,7 @@ On Thu, Jul 19, 2018 at 10:22:40AM -0600, Keith Busch wrote:
 > > > it was blocked from completion with no way to recover.
 > > 
 > > The patch I had posted handles a completion that occurs while a timeout is
-> > being handled properly. From https://www.mail-archive.com/linux-block@vger.kernel.org/msg22196.html:
+> > being handled properly. From https://www.mail-archive.com/linux-block at vger.kernel.org/msg22196.html:
 > 
 > Sounds like a win-win to me.
 
diff --git a/a/content_digest b/N1/content_digest
index f2fe2c7..1219113 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -8,22 +8,14 @@
  "ref\020180719155616.GG32160@localhost.localdomain\0"
  "ref\07239f833438701fb6ce21d819bc7042af1bc1f8a.camel@wdc.com\0"
  "ref\020180719162240.GH32160@localhost.localdomain\0"
- "From\0hch@lst.de <hch@lst.de>\0"
- "Subject\0Re: [RFC PATCH 3/3] blk-mq: Remove generation seqeunce\0"
+ "From\0hch@lst.de (hch@lst.de)\0"
+ "Subject\0[RFC PATCH 3/3] blk-mq: Remove generation seqeunce\0"
  "Date\0Thu, 19 Jul 2018 18:29:24 +0200\0"
- "To\0Keith Busch <keith.busch@linux.intel.com>\0"
- "Cc\0Bart Van Assche <Bart.VanAssche@wdc.com>"
-  hch@lst.de <hch@lst.de>
-  keith.busch@intel.com <keith.busch@intel.com>
-  linux-nvme@lists.infradead.org <linux-nvme@lists.infradead.org>
-  linux-block@vger.kernel.org <linux-block@vger.kernel.org>
-  axboe@kernel.dk <axboe@kernel.dk>
- " ming.lei@redhat.com <ming.lei@redhat.com>\0"
  "\00:1\0"
  "b\0"
- "On Thu, Jul 19, 2018 at 10:22:40AM -0600, Keith Busch wrote:\n"
- "> On Thu, Jul 19, 2018 at 04:04:46PM +0000, Bart Van Assche wrote:\n"
- "> > On Thu, 2018-07-19 at 09:56 -0600, Keith Busch wrote:\n"
+ "On Thu, Jul 19, 2018@10:22:40AM -0600, Keith Busch wrote:\n"
+ "> On Thu, Jul 19, 2018@04:04:46PM +0000, Bart Van Assche wrote:\n"
+ "> > On Thu, 2018-07-19@09:56 -0600, Keith Busch wrote:\n"
  "> > > Even some scsi drivers are susceptible to losing their requests with the\n"
  "> > > reverted behavior: take virtio-scsi for example, which returns RESET_TIMER\n"
  "> > > from it's timeout handler. With the behavior everyone seems to want,\n"
@@ -31,11 +23,11 @@
  "> > > it was blocked from completion with no way to recover.\n"
  "> > \n"
  "> > The patch I had posted handles a completion that occurs while a timeout is\n"
- "> > being handled properly. From https://www.mail-archive.com/linux-block@vger.kernel.org/msg22196.html:\n"
+ "> > being handled properly. From https://www.mail-archive.com/linux-block at vger.kernel.org/msg22196.html:\n"
  "> \n"
  "> Sounds like a win-win to me.\n"
  "\n"
  "How do we get a fix into 4.18 at this part of the cycle?  I think that\n"
  is the most important prirority right now.
 
-6ce51b69482f7103220f3fa26025fb98f4151d2e05a35cb540ba360196adb6f5
+b3eaa6009ba1c203b96e6327427fda0c9e14762e56c2c0fc5ee6e2dc79eed231

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.