All of lore.kernel.org
 help / color / mirror / Atom feed

diff for duplicates of <20180514122211.GB807@ming.t460p>

diff --git a/a/1.txt b/N1/1.txt
index 1996ade..4188d46 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,6 +1,6 @@
 Hi Jianchao,
 
-On Mon, May 14, 2018 at 06:05:50PM +0800, jianchao.wang wrote:
+On Mon, May 14, 2018@06:05:50PM +0800, jianchao.wang wrote:
 > Hi ming
 > 
 > On 05/14/2018 05:38 PM, Ming Lei wrote:
@@ -98,7 +98,7 @@ index f509d37b2fb8..44e38be259f2 100644
 > > Could you dump the stack trace of EH0 reset task? So that we may see
 > > where EH0 reset kthread hangs.
 > 
-> root@will-ThinkCentre-M910s:/home/will/Desktop# cat /proc/2273/stack 
+> root at will-ThinkCentre-M910s:/home/will/Desktop# cat /proc/2273/stack 
 > [<0>] blk_execute_rq+0xf7/0x150
 > [<0>] __nvme_submit_sync_cmd+0x94/0x110
 > [<0>] nvme_submit_sync_cmd+0x1b/0x20
@@ -114,7 +114,7 @@ index f509d37b2fb8..44e38be259f2 100644
 Even without this patch, the above hang can happen in reset context,
 so this issue isn't related with the introduced 'reset_lock'.
 
-> root@will-ThinkCentre-M910s:/home/will/Desktop# cat /proc/2275/stack 
+> root at will-ThinkCentre-M910s:/home/will/Desktop# cat /proc/2275/stack 
 > [<0>] nvme_eh_work+0x11a/0x4b0
 > [<0>] process_one_work+0x3ca/0xaa0
 > [<0>] worker_thread+0x89/0x6c0
diff --git a/a/content_digest b/N1/content_digest
index f099c92..e7ca27d 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -11,27 +11,14 @@
   "ref\000008cb38d-aa91-6ab7-64d9-417d6c53a1eb\@oracle.com\0"
 ]
 [
-  "From\0Ming Lei <ming.lei\@redhat.com>\0"
+  "From\0ming.lei\@redhat.com (Ming Lei)\0"
 ]
 [
-  "Subject\0Re: [PATCH V5 0/9] nvme: pci: fix & improve timeout handling\0"
+  "Subject\0[PATCH V5 0/9] nvme: pci: fix & improve timeout handling\0"
 ]
 [
   "Date\0Mon, 14 May 2018 20:22:13 +0800\0"
 ]
-[
-  "To\0jianchao.wang <jianchao.w.wang\@oracle.com>\0"
-]
-[
-  "Cc\0Keith Busch <keith.busch\@intel.com>",
-  " Jens Axboe <axboe\@kernel.dk>",
-  " linux-block\@vger.kernel.org",
-  " James Smart <james.smart\@broadcom.com>",
-  " Christoph Hellwig <hch\@lst.de>",
-  " Sagi Grimberg <sagi\@grimberg.me>",
-  " linux-nvme\@lists.infradead.org",
-  " Laurence Oberman <loberman\@redhat.com>\0"
-]
 [
   "\0000:1\0"
 ]
@@ -41,7 +28,7 @@
 [
   "Hi Jianchao,\n",
   "\n",
-  "On Mon, May 14, 2018 at 06:05:50PM +0800, jianchao.wang wrote:\n",
+  "On Mon, May 14, 2018\@06:05:50PM +0800, jianchao.wang wrote:\n",
   "> Hi ming\n",
   "> \n",
   "> On 05/14/2018 05:38 PM, Ming Lei wrote:\n",
@@ -139,7 +126,7 @@
   "> > Could you dump the stack trace of EH0 reset task? So that we may see\n",
   "> > where EH0 reset kthread hangs.\n",
   "> \n",
-  "> root\@will-ThinkCentre-M910s:/home/will/Desktop# cat /proc/2273/stack \n",
+  "> root at will-ThinkCentre-M910s:/home/will/Desktop# cat /proc/2273/stack \n",
   "> [<0>] blk_execute_rq+0xf7/0x150\n",
   "> [<0>] __nvme_submit_sync_cmd+0x94/0x110\n",
   "> [<0>] nvme_submit_sync_cmd+0x1b/0x20\n",
@@ -155,7 +142,7 @@
   "Even without this patch, the above hang can happen in reset context,\n",
   "so this issue isn't related with the introduced 'reset_lock'.\n",
   "\n",
-  "> root\@will-ThinkCentre-M910s:/home/will/Desktop# cat /proc/2275/stack \n",
+  "> root at will-ThinkCentre-M910s:/home/will/Desktop# cat /proc/2275/stack \n",
   "> [<0>] nvme_eh_work+0x11a/0x4b0\n",
   "> [<0>] process_one_work+0x3ca/0xaa0\n",
   "> [<0>] worker_thread+0x89/0x6c0\n",
@@ -188,4 +175,4 @@
   "Ming"
 ]
 
-7c4540bf9bc4c3d2b21ca04e77008aaf1888ab09d0ce31c1ce1c5f14a46836c1
+cc8152582eed97fc9abbb57f73facdf15470a194201b6d547533bcf1e9dd562b
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.