All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <1540241646.128590.16.camel@acm.org>

diff --git a/a/1.txt b/N1/1.txt
index f232284..38be784 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,4 +1,4 @@
-On Mon, 2018-10-22@22:28 +0200, Johannes Berg wrote:
+On Mon, 2018-10-22 at 22:28 +0200, Johannes Berg wrote:
 > The lockdep report even more or less tells you what's going on. Perhaps
 > we need to find a way to make lockdep not print "lock()" but "start()"
 > or "flush()" for work items ... but if you read it this way, you see:
@@ -17,7 +17,7 @@ clearly doesn't deadlock. So where do you think the bug is? In the direct I/O
 code or in your patch?
 
 The code in the column with label "CPU0" is code called by do_blockdev_direct_IO().
->From the body of that function:
+From the body of that function:
 
 			/* will be released by direct_io_worker */
 			inode_lock(inode);
diff --git a/a/content_digest b/N1/content_digest
index 3a40a54..fc3042c 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -1,12 +1,18 @@
  "ref\020181022151818.135163-1-bvanassche@acm.org\0"
  "ref\013901aed5074f4b1fbd259d03928efb6ab40c65a.camel@sipsolutions.net\0"
  "ref\0094669f3df1690dec5913c2086f6a6d8c470f685.camel@sipsolutions.net\0"
- "From\0bvanassche@acm.org (Bart Van Assche)\0"
- "Subject\0[PATCH] Revert \"workqueue: re-add lockdep dependencies for flushing\"\0"
+ "From\0Bart Van Assche <bvanassche@acm.org>\0"
+ "Subject\0Re: [PATCH] Revert \"workqueue: re-add lockdep dependencies for flushing\"\0"
  "Date\0Mon, 22 Oct 2018 13:54:06 -0700\0"
+ "To\0Johannes Berg <johannes@sipsolutions.net>"
+ " Tejun Heo <tj@kernel.org>\0"
+ "Cc\0linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org>"
+  Christoph Hellwig <hch@lst.de>
+  Sagi Grimberg <sagi@grimberg.me>
+ " linux-nvme @ lists . infradead . org <linux-nvme@lists.infradead.org>\0"
  "\00:1\0"
  "b\0"
- "On Mon, 2018-10-22@22:28 +0200, Johannes Berg wrote:\n"
+ "On Mon, 2018-10-22 at 22:28 +0200, Johannes Berg wrote:\n"
  "> The lockdep report even more or less tells you what's going on. Perhaps\n"
  "> we need to find a way to make lockdep not print \"lock()\" but \"start()\"\n"
  "> or \"flush()\" for work items ... but if you read it this way, you see:\n"
@@ -25,7 +31,7 @@
  "code or in your patch?\n"
  "\n"
  "The code in the column with label \"CPU0\" is code called by do_blockdev_direct_IO().\n"
- ">From the body of that function:\n"
+ "From the body of that function:\n"
  "\n"
  "\t\t\t/* will be released by direct_io_worker */\n"
  "\t\t\tinode_lock(inode);\n"
@@ -35,4 +41,4 @@
  "\n"
  Bart.
 
-8cf37d4da334c890f7efff5d0ed33c9a102b01f08c0774acfdf0e180c6a031f9
+d44b8a6b60a1d6440e366aa8b24a46f67631118df6e53b115d87ee5237cb2b85

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.