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

diff --git a/a/1.txt b/N1/1.txt
index cc60459..60eae8b 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -1,4 +1,4 @@
-On Wed, Jun 13, 2018@04:11:56PM +0530, Jitendra Bhivare wrote:
+On Wed, Jun 13, 2018 at 04:11:56PM +0530, Jitendra Bhivare wrote:
 > So something like resolves the issue:
 > static void nvme_set_chunk_size(struct nvme_ns *ns)
 > {
diff --git a/a/content_digest b/N1/content_digest
index 901ee48..d284c8c 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -1,10 +1,10 @@
- "ref\00ba3cccb9d2ee7cba50a91bfc92b373a@mail.gmail.com\0"
- "From\0hch@lst.de (Christoph Hellwig)\0"
- "Subject\0Read request exceeding max_hw_sectors_kb\0"
+ "From\0Christoph Hellwig <hch at lst.de>\0"
+ "Subject\0Re: [SPDK] Read request exceeding max_hw_sectors_kb\0"
  "Date\0Wed, 13 Jun 2018 13:47:56 +0200\0"
- "\00:1\0"
+ "To\0spdk@lists.01.org\0"
+ "\01:1\0"
  "b\0"
- "On Wed, Jun 13, 2018@04:11:56PM +0530, Jitendra Bhivare wrote:\n"
+ "On Wed, Jun 13, 2018 at 04:11:56PM +0530, Jitendra Bhivare wrote:\n"
  "> So something like resolves the issue:\n"
  "> static void nvme_set_chunk_size(struct nvme_ns *ns)\n"
  "> {\n"
@@ -23,4 +23,4 @@
  "in handling bogus noiob sizes, so please submit a patch per your above\n"
  analysis.  spdk should be fixed to not expose a bogus noiob size as well.
 
-2128b2896d759c56d253ef80d7afea9ca8f7796b5fd7163b4f79859bfc1c4bc7
+53bd763db17dbfd8ae31a8b636ab6b1d841e33550c1411f592cf3bcec117c9b1

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.