diff for duplicates of <562E40BB.6040404@gmail.com> diff --git a/a/1.txt b/N1/1.txt index 355f225..4ca10ce 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,5 +1,5 @@ On 10/25/2015 10:36 PM, Lan Tianyu wrote: -> On 2015?10?24? 02:36, Alexander Duyck wrote: +> On 2015年10月24日 02:36, Alexander Duyck wrote: >> I was thinking about it and I am pretty sure the dummy write approach is >> problematic at best. Specifically the issue is that while you are >> performing a dummy write you risk pulling in descriptors for data that diff --git a/a/content_digest b/N1/content_digest index cb47361..5954640 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -2,13 +2,34 @@ "ref\0562A7E33.4080800@gmail.com\0" "ref\0562DBBC9.4000104@intel.com\0" "From\0Alexander Duyck <alexander.duyck@gmail.com>\0" - "Subject\0[Intel-wired-lan] [RFC Patch 00/12] IXGBE: Add live migration support for SRIOV NIC\0" + "Subject\0Re: [RFC Patch 00/12] IXGBE: Add live migration support for SRIOV NIC\0" "Date\0Mon, 26 Oct 2015 08:03:23 -0700\0" - "To\0intel-wired-lan@osuosl.org\0" + "To\0Lan Tianyu <tianyu.lan@intel.com>" + bhelgaas@google.com + carolyn.wyborny@intel.com + donald.c.skidmore@intel.com + eddie.dong@intel.com + nrupal.jani@intel.com + yang.z.zhang@intel.com + agraf@suse.de + kvm@vger.kernel.org + pbonzini@redhat.com + qemu-devel@nongnu.org + emil.s.tantilov@intel.com + intel-wired-lan@lists.osuosl.org + jeffrey.t.kirsher@intel.com + jesse.brandeburg@intel.com + john.ronciak@intel.com + linux-kernel@vger.kernel.org + linux-pci@vger.kernel.org + matthew.vick@intel.com + mitch.a.williams@intel.com + netdev@vger.kernel.org + " shannon.nelson@intel.com\0" "\00:1\0" "b\0" "On 10/25/2015 10:36 PM, Lan Tianyu wrote:\n" - "> On 2015?10?24? 02:36, Alexander Duyck wrote:\n" + "> On 2015\345\271\26410\346\234\21024\346\227\245 02:36, Alexander Duyck wrote:\n" ">> I was thinking about it and I am pretty sure the dummy write approach is\n" ">> problematic at best. Specifically the issue is that while you are\n" ">> performing a dummy write you risk pulling in descriptors for data that\n" @@ -41,4 +62,4 @@ "\n" - Alex -a084a7d14d81bfba33ce639158b6d5a2aba0d57961177c80775c6ad5a07be75c +c3288daca73690efce82a085c35554e31824ebbfcee1eef391d734931de13b46
diff --git a/a/1.txt b/N2/1.txt index 355f225..4ca10ce 100644 --- a/a/1.txt +++ b/N2/1.txt @@ -1,5 +1,5 @@ On 10/25/2015 10:36 PM, Lan Tianyu wrote: -> On 2015?10?24? 02:36, Alexander Duyck wrote: +> On 2015年10月24日 02:36, Alexander Duyck wrote: >> I was thinking about it and I am pretty sure the dummy write approach is >> problematic at best. Specifically the issue is that while you are >> performing a dummy write you risk pulling in descriptors for data that diff --git a/a/content_digest b/N2/content_digest index cb47361..1ee2f1f 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -2,13 +2,34 @@ "ref\0562A7E33.4080800@gmail.com\0" "ref\0562DBBC9.4000104@intel.com\0" "From\0Alexander Duyck <alexander.duyck@gmail.com>\0" - "Subject\0[Intel-wired-lan] [RFC Patch 00/12] IXGBE: Add live migration support for SRIOV NIC\0" + "Subject\0Re: [Qemu-devel] [RFC Patch 00/12] IXGBE: Add live migration support for SRIOV NIC\0" "Date\0Mon, 26 Oct 2015 08:03:23 -0700\0" - "To\0intel-wired-lan@osuosl.org\0" + "To\0Lan Tianyu <tianyu.lan@intel.com>" + bhelgaas@google.com + carolyn.wyborny@intel.com + donald.c.skidmore@intel.com + eddie.dong@intel.com + nrupal.jani@intel.com + yang.z.zhang@intel.com + agraf@suse.de + kvm@vger.kernel.org + pbonzini@redhat.com + qemu-devel@nongnu.org + emil.s.tantilov@intel.com + intel-wired-lan@lists.osuosl.org + jeffrey.t.kirsher@intel.com + jesse.brandeburg@intel.com + john.ronciak@intel.com + linux-kernel@vger.kernel.org + linux-pci@vger.kernel.org + matthew.vick@intel.com + mitch.a.williams@intel.com + netdev@vger.kernel.org + " shannon.nelson@intel.com\0" "\00:1\0" "b\0" "On 10/25/2015 10:36 PM, Lan Tianyu wrote:\n" - "> On 2015?10?24? 02:36, Alexander Duyck wrote:\n" + "> On 2015\345\271\26410\346\234\21024\346\227\245 02:36, Alexander Duyck wrote:\n" ">> I was thinking about it and I am pretty sure the dummy write approach is\n" ">> problematic at best. Specifically the issue is that while you are\n" ">> performing a dummy write you risk pulling in descriptors for data that\n" @@ -41,4 +62,4 @@ "\n" - Alex -a084a7d14d81bfba33ce639158b6d5a2aba0d57961177c80775c6ad5a07be75c +b73c18f3cb4ba3fb4bf93f6faac5a4380eb82b3b07f72a2609fc80bcdd91eabe
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.