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

diff --git a/a/1.txt b/N1/1.txt
index 745c1f0..209f1e4 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -38,3 +38,8 @@ On Mon, Aug 24, 2020 at 02:16:30PM -0700, Keith Busch wrote:
 > WRITE/READ_ONCE() can handle that without a lock, right?
 
 It synchronizes a few fields, sometimes taken over multiple updates.
+
+_______________________________________________
+Linux-nvme mailing list
+Linux-nvme@lists.infradead.org
+http://lists.infradead.org/mailman/listinfo/linux-nvme
diff --git a/a/content_digest b/N1/content_digest
index 95291e9..ec4b1dd 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -3,7 +3,7 @@
  "ref\020200824211630.GA1490518@dhcp-10-100-145-180.wdl.wdc.com\0"
  "From\0Christoph Hellwig <hch@lst.de>\0"
  "Subject\0Re: [PATCH] nvmet-fc: Fix a missed _irqsave version of spin_lock in 'nvmet_fc_fod_op_done()'\0"
- "Date\0Tue, 25 Aug 2020 07:09:40 +0000\0"
+ "Date\0Tue, 25 Aug 2020 09:09:40 +0200\0"
  "To\0Keith Busch <kbusch@kernel.org>\0"
  "Cc\0Sagi Grimberg <sagi@grimberg.me>"
   chaitanya.kulkarni@wdc.com
@@ -54,6 +54,11 @@
  "> afaics, the lock just serializes single writes, in which\n"
  "> WRITE/READ_ONCE() can handle that without a lock, right?\n"
  "\n"
- It synchronizes a few fields, sometimes taken over multiple updates.
+ "It synchronizes a few fields, sometimes taken over multiple updates.\n"
+ "\n"
+ "_______________________________________________\n"
+ "Linux-nvme mailing list\n"
+ "Linux-nvme@lists.infradead.org\n"
+ http://lists.infradead.org/mailman/listinfo/linux-nvme
 
-e8e3ca1c5f16d1deda92fe56d1228a0a8998c08faf336262b6ee580bfbc3aa07
+a5a9ab6d72bba2b7d410a018a16c19d0800b53ce8f2938f51161bccfdcdd1a01

diff --git a/a/content_digest b/N2/content_digest
index 95291e9..5632c5c 100644
--- a/a/content_digest
+++ b/N2/content_digest
@@ -3,16 +3,16 @@
  "ref\020200824211630.GA1490518@dhcp-10-100-145-180.wdl.wdc.com\0"
  "From\0Christoph Hellwig <hch@lst.de>\0"
  "Subject\0Re: [PATCH] nvmet-fc: Fix a missed _irqsave version of spin_lock in 'nvmet_fc_fod_op_done()'\0"
- "Date\0Tue, 25 Aug 2020 07:09:40 +0000\0"
+ "Date\0Tue, 25 Aug 2020 09:09:40 +0200\0"
  "To\0Keith Busch <kbusch@kernel.org>\0"
  "Cc\0Sagi Grimberg <sagi@grimberg.me>"
-  chaitanya.kulkarni@wdc.com
-  kernel-janitors@vger.kernel.org
+  Christophe JAILLET <christophe.jaillet@wanadoo.fr>
   james.smart@broadcom.com
+  hch@lst.de
+  chaitanya.kulkarni@wdc.com
   linux-nvme@lists.infradead.org
   linux-kernel@vger.kernel.org
-  Christophe JAILLET <christophe.jaillet@wanadoo.fr>
- " hch@lst.de\0"
+ " kernel-janitors@vger.kernel.org\0"
  "\00:1\0"
  "b\0"
  "On Mon, Aug 24, 2020 at 02:16:30PM -0700, Keith Busch wrote:\n"
@@ -56,4 +56,4 @@
  "\n"
  It synchronizes a few fields, sometimes taken over multiple updates.
 
-e8e3ca1c5f16d1deda92fe56d1228a0a8998c08faf336262b6ee580bfbc3aa07
+78bc0e4789e63902f3f562e243cd6c4d3e788446b57ce52431c59022cf30e27e

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.