diff for duplicates of <20170616095837.GA14217@lst.de> diff --git a/a/1.txt b/N1/1.txt index 63dcc0f..872c36f 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,13 +1,13 @@ -On Fri, Jun 16, 2017@11:48:32AM +0200, Johannes Thumshirn wrote: +On Fri, Jun 16, 2017 at 11:48:32AM +0200, Johannes Thumshirn wrote: > On 06/16/2017 11:40 AM, Christoph Hellwig wrote: -> > On Fri, Jun 16, 2017@10:20:04AM +0200, Johannes Thumshirn wrote: +> > On Fri, Jun 16, 2017 at 10:20:04AM +0200, Johannes Thumshirn wrote: > >> Strange, as I tested with nvme-loop all the time... > > > > Yeah, it's actually there, but for some reason find on sysfs > > behaves strange: > > -> > root at testvm:~# find /sys -name uuid -> > root at testvm:~# cat /sys/class/nvme/nvme2/nvme2n1/uuid +> > root@testvm:~# find /sys -name uuid +> > root@testvm:~# cat /sys/class/nvme/nvme2/nvme2n1/uuid > > 6665a65b-f42f-469b-800e-a047238649eb > > Wasn't there something that find on sysfs isn't reliable? diff --git a/a/content_digest b/N1/content_digest index 5a112a2..70b5f3c 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -3,21 +3,29 @@ "ref\0bab953e9-7026-5833-9f65-1ef8b90433d7@suse.de\0" "ref\020170616094056.GA12465@lst.de\0" "ref\0905ed2e6-1c1c-f3a3-5391-66e42fb61861@suse.de\0" - "From\0hch@lst.de (Christoph Hellwig)\0" - "Subject\0[PATCH v6 00/10] Implement NVMe Namespace Descriptor Identification\0" + "From\0Christoph Hellwig <hch@lst.de>\0" + "Subject\0Re: [PATCH v6 00/10] Implement NVMe Namespace Descriptor Identification\0" "Date\0Fri, 16 Jun 2017 11:58:37 +0200\0" + "To\0Johannes Thumshirn <jthumshirn@suse.de>\0" + "Cc\0Christoph Hellwig <hch@lst.de>" + Sagi Grimberg <sagi@grimberg.me> + Linux Kernel Mailinglist <linux-kernel@vger.kernel.org> + Linux NVMe Mailinglist <linux-nvme@lists.infradead.org> + Keith Busch <keith.busch@intel.com> + Hannes Reinecke <hare@suse.de> + " Max Gurtovoy <maxg@mellanox.com>\0" "\00:1\0" "b\0" - "On Fri, Jun 16, 2017@11:48:32AM +0200, Johannes Thumshirn wrote:\n" + "On Fri, Jun 16, 2017 at 11:48:32AM +0200, Johannes Thumshirn wrote:\n" "> On 06/16/2017 11:40 AM, Christoph Hellwig wrote:\n" - "> > On Fri, Jun 16, 2017@10:20:04AM +0200, Johannes Thumshirn wrote:\n" + "> > On Fri, Jun 16, 2017 at 10:20:04AM +0200, Johannes Thumshirn wrote:\n" "> >> Strange, as I tested with nvme-loop all the time...\n" "> > \n" "> > Yeah, it's actually there, but for some reason find on sysfs\n" "> > behaves strange:\n" "> > \n" - "> > root at testvm:~# find /sys -name uuid\n" - "> > root at testvm:~# cat /sys/class/nvme/nvme2/nvme2n1/uuid \n" + "> > root@testvm:~# find /sys -name uuid\n" + "> > root@testvm:~# cat /sys/class/nvme/nvme2/nvme2n1/uuid \n" "> > 6665a65b-f42f-469b-800e-a047238649eb\n" "> \n" "> Wasn't there something that find on sysfs isn't reliable?\n" @@ -28,4 +36,4 @@ "\n" Heh. Now we just need the nvme-cli patches to verify it independently :) -c41ce302d56cc7597b49d8f01d8667112f91b905d95bd7a273fd6b360ed2a5c8 +18a30810c34b71b266255f8f612f2039a288648305ea2177b558b80cd1edd872
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.