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

diff --git a/a/1.txt b/N1/1.txt
index c4218f1..ca4545a 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,3 +1,8 @@
 Unless I'm missing something this fails to advertise multiple command
 support in the CAP property, as well as the enablement in the CC
 property.  How does the host manage to even use this?
+
+_______________________________________________
+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 5c73b50..04444cd 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -3,16 +3,21 @@
  "Subject\0Re: [PATCH V4 0/9] nvmet: add ZBD backend support\0"
  "Date\0Wed, 2 Dec 2020 10:20:19 +0100\0"
  "To\0Chaitanya Kulkarni <chaitanya.kulkarni@wdc.com>\0"
- "Cc\0linux-block@vger.kernel.org"
-  linux-nvme@lists.infradead.org
+ "Cc\0damien.lemoal@wdc.com"
   sagi@grimberg.me
-  hch@lst.de
-  damien.lemoal@wdc.com
- " johannes.thumshirn@wdc.com\0"
+  johannes.thumshirn@wdc.com
+  linux-nvme@lists.infradead.org
+  linux-block@vger.kernel.org
+ " hch@lst.de\0"
  "\00:1\0"
  "b\0"
  "Unless I'm missing something this fails to advertise multiple command\n"
  "support in the CAP property, as well as the enablement in the CC\n"
- property.  How does the host manage to even use this?
+ "property.  How does the host manage to even use this?\n"
+ "\n"
+ "_______________________________________________\n"
+ "Linux-nvme mailing list\n"
+ "Linux-nvme@lists.infradead.org\n"
+ http://lists.infradead.org/mailman/listinfo/linux-nvme
 
-6877af8ff555ec10531c0ebb191ee73b073d00112eb3b434d6f981f40c0a8caa
+1abf219cc521dc482e13bcd36ed32dffe8c4e631d3d27ed1a43aa31d74928466

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.