All of lore.kernel.org
 help / color / mirror / Atom feed
diff for duplicates of <aNVahJkpJVVTVEkK@google.com>

diff --git a/a/1.txt b/N1/1.txt
index d363be4..0b7359e 100644
--- a/a/1.txt
+++ b/N1/1.txt
@@ -24,3 +24,9 @@ straightaway, but not feed it into -next until the merge window closes.  The 0-d
 bots scrapes kvm-x86, so that'd get us some early build-bot exposure, and we can
 stop bugging the non-KVM folks.  Then when the dust settles on the KVM changes,
 I can throw them into the same topic branch.
+
+
+_______________________________________________
+Linux-f2fs-devel mailing list
+Linux-f2fs-devel@lists.sourceforge.net
+https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
diff --git a/a/content_digest b/N1/content_digest
index d7c169a..8f33016 100644
--- a/a/content_digest
+++ b/N1/content_digest
@@ -6,92 +6,91 @@
  "ref\0b67dd7cd-2c1c-4566-badf-32082d8cd952@redhat.com\0"
  "ref\0aNVFrZDAkHmgNNci@google.com\0"
  "ref\03a82a197-495f-40c3-ae1b-500453e3d1ec@redhat.com\0"
- "From\0Sean Christopherson <seanjc@google.com>\0"
- "Subject\0Re: [PATCH kvm-next V11 4/7] KVM: guest_memfd: Use guest mem inodes instead of anonymous inodes\0"
+ "From\0Sean Christopherson via Linux-f2fs-devel <linux-f2fs-devel@lists.sourceforge.net>\0"
+ "Subject\0Re: [f2fs-dev] [PATCH kvm-next V11 4/7] KVM: guest_memfd: Use guest mem inodes instead of anonymous inodes\0"
  "Date\0Thu, 25 Sep 2025 08:06:44 -0700\0"
  "To\0David Hildenbrand <david@redhat.com>\0"
- "Cc\0Shivank Garg <shivankg@amd.com>"
-  Ackerley Tng <ackerleytng@google.com>
-  willy@infradead.org
-  akpm@linux-foundation.org
-  pbonzini@redhat.com
-  shuah@kernel.org
-  vbabka@suse.cz
-  brauner@kernel.org
-  viro@zeniv.linux.org.uk
-  dsterba@suse.com
-  xiang@kernel.org
-  chao@kernel.org
-  jaegeuk@kernel.org
+ "Cc\0jgowans@amazon.com"
+  mhocko@suse.com
+  jack@suse.cz
+  kvm@vger.kernel.org
+  dhavale@google.com
+  linux-btrfs@vger.kernel.org
+  aik@amd.com
+  papaluri@amd.com
+  kalyazin@amazon.com
+  peterx@redhat.com
+  linux-mm@kvack.org
   clm@fb.com
-  josef@toxicpanda.com
-  kent.overstreet@linux.dev
+  ddutile@redhat.com
+  linux-kselftest@vger.kernel.org
+  shdhiman@amd.com
+  gshan@redhat.com
+  ying.huang@linux.alibaba.com
+  shuah@kernel.org
+  roypat@amazon.co.uk
+  matthew.brost@intel.com
+  linux-coco@lists.linux.dev
   zbestahu@gmail.com
-  jefflexu@linux.alibaba.com
-  dhavale@google.com
-  lihongbo22@huawei.com
   lorenzo.stoakes@oracle.com
-  Liam.Howlett@oracle.com
-  rppt@kernel.org
-  surenb@google.com
-  mhocko@suse.com
-  ziy@nvidia.com
-  matthew.brost@intel.com
-  joshua.hahnjy@gmail.com
-  rakie.kim@sk.com
-  byungchul@sk.com
-  gourry@gourry.net
-  ying.huang@linux.alibaba.com
+  linux-bcachefs@vger.kernel.org
+  ira.weiny@intel.com
   apopple@nvidia.com
-  tabba@google.com
-  paul@paul-moore.com
   jmorris@namei.org
-  serge@hallyn.com
-  pvorel@suse.cz
-  bfoster@redhat.com
-  vannapurve@google.com
+  willy@infradead.org
+  hch@infradead.org
   chao.gao@intel.com
-  bharata@amd.com
+  tabba@google.com
+  ziy@nvidia.com
+  rientjes@google.com
+  yuzhao@google.com
+  xiang@kernel.org
   nikunj@amd.com
-  michael.day@amd.com
-  shdhiman@amd.com
+  gourry@gourry.net
+  serge@hallyn.com
+  Shivank Garg <shivankg@amd.com>
+  thomas.lendacky@amd.com
+  ashish.kalra@amd.com
+  chao.p.peng@intel.com
   yan.y.zhao@intel.com
+  byungchul@sk.com
+  michael.day@amd.com
   Neeraj.Upadhyay@amd.com
-  thomas.lendacky@amd.com
   michael.roth@amd.com
-  aik@amd.com
-  jgg@nvidia.com
-  kalyazin@amazon.com
-  peterx@redhat.com
-  jack@suse.cz
-  hch@infradead.org
-  cgzones@googlemail.com
-  ira.weiny@intel.com
-  rientjes@google.com
-  roypat@amazon.co.uk
-  chao.p.peng@intel.com
-  amit@infradead.org
-  ddutile@redhat.com
+  bfoster@redhat.com
+  bharata@amd.com
+  josef@toxicpanda.com
+  Liam.Howlett@oracle.com
+  Ackerley Tng <ackerleytng@google.com>
+  dsterba@suse.com
+  viro@zeniv.linux.org.uk
+  jefflexu@linux.alibaba.com
+  jaegeuk@kernel.org
   dan.j.williams@intel.com
-  ashish.kalra@amd.com
-  gshan@redhat.com
-  jgowans@amazon.com
-  pankaj.gupta@amd.com
-  papaluri@amd.com
-  yuzhao@google.com
-  suzuki.poulose@arm.com
+  surenb@google.com
+  vbabka@suse.cz
+  paul@paul-moore.com
+  joshua.hahnjy@gmail.com
+  brauner@kernel.org
   quic_eberman@quicinc.com
-  linux-bcachefs@vger.kernel.org
-  linux-btrfs@vger.kernel.org
+  rakie.kim@sk.com
+  cgzones@googlemail.com
+  pvorel@suse.cz
   linux-erofs@lists.ozlabs.org
-  linux-f2fs-devel@lists.sourceforge.net
-  linux-fsdevel@vger.kernel.org
-  linux-mm@kvack.org
+  kent.overstreet@linux.dev
   linux-kernel@vger.kernel.org
+  linux-f2fs-devel@lists.sourceforge.net
+  pankaj.gupta@amd.com
   linux-security-module@vger.kernel.org
-  kvm@vger.kernel.org
-  linux-kselftest@vger.kernel.org
- " linux-coco@lists.linux.dev\0"
+  lihongbo22@huawei.com
+  amit@infradead.org
+  linux-fsdevel@vger.kernel.org
+  pbonzini@redhat.com
+  akpm@linux-foundation.org
+  vannapurve@google.com
+  suzuki.poulose@arm.com
+  rppt@kernel.org
+ " jgg@nvidia.com\0"
  "\00:1\0"
  "b\0"
  "On Thu, Sep 25, 2025, David Hildenbrand wrote:\n"
@@ -119,6 +118,12 @@
  "straightaway, but not feed it into -next until the merge window closes.  The 0-day\n"
  "bots scrapes kvm-x86, so that'd get us some early build-bot exposure, and we can\n"
  "stop bugging the non-KVM folks.  Then when the dust settles on the KVM changes,\n"
- I can throw them into the same topic branch.
+ "I can throw them into the same topic branch.\n"
+ "\n"
+ "\n"
+ "_______________________________________________\n"
+ "Linux-f2fs-devel mailing list\n"
+ "Linux-f2fs-devel@lists.sourceforge.net\n"
+ https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
 
-0d6864bda6e2dedb4f142e67631c90e2603459660a0f69095adf3b4de5485d8e
+3f424c02998e5bf56ddd6d8f28f0372aa44eae9dc3af8a94372d5b5059322624

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.