diff for duplicates of <1369870365.18630.48@snotra> diff --git a/a/1.txt b/N1/1.txt index 7c7b0dc..bff8b61 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -2,32 +2,32 @@ On 05/29/2013 06:29:13 PM, Alexey Kardashevskiy wrote: > On 05/30/2013 09:14 AM, Scott Wood wrote: > > On 05/29/2013 06:10:33 PM, Alexey Kardashevskiy wrote: > >> On 05/30/2013 06:05 AM, Scott Wood wrote: -> >> > But you didn't put it in the same section as +> >> > But you didn't put it in the same section as =20 > KVM_CREATE_SPAPR_TCE. 0xe0 > >> > begins a different section. > >> -> >> It is not really obvious that there are sections as no comment +> >> It is not really obvious that there are sections as no comment =20 > defines > >> those :) > > -> > There is a comment /* ioctls for fds returned by KVM_CREATE_DEVICE +> > There is a comment /* ioctls for fds returned by KVM_CREATE_DEVICE =20 > */ > > -> > Putting KVM_CREATE_DEVICE in there was mainly to avoid dealing with +> > Putting KVM_CREATE_DEVICE in there was mainly to avoid dealing with =20 > the -> > ioctl number conflict mess in the vm-ioctl section, but at least +> > ioctl number conflict mess in the vm-ioctl section, but at least =20 > that one > > is related to the device control API. :-) > > -> >> But yes, makes sense to move it up a bit and change the code to +> >> But yes, makes sense to move it up a bit and change the code to =20 > 0xad. > > > > 0xad is KVM_KVMCLOCK_CTRL -> +>=20 > That's it. I am _completely_ confused now. No system whatsoever :( -> What rule should I use in order to choose the number for my new +> What rule should I use in order to choose the number for my new =20 > ioctl? :) Yeah, it's a mess. 0xaf seems to be free. :-) --Scott +-Scott= diff --git a/a/content_digest b/N1/content_digest index 043b667..5789b49 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -8,49 +8,49 @@ "ref\051A68F49.6020908@ozlabs.ru\0" "From\0Scott Wood <scottwood@freescale.com>\0" "Subject\0Re: [PATCH 3/4] KVM: PPC: Add support for IOMMU in-kernel handling\0" - "Date\0Wed, 29 May 2013 23:32:45 +0000\0" + "Date\0Wed, 29 May 2013 18:32:45 -0500\0" "To\0Alexey Kardashevskiy <aik@ozlabs.ru>\0" - "Cc\0David Gibson <david@gibson.dropbear.id.au>" - kvm@vger.kernel.org - linux-kernel@vger.kernel.org - kvm-ppc@vger.kernel.org + "Cc\0kvm@vger.kernel.org" Alexander Graf <agraf@suse.de> + kvm-ppc@vger.kernel.org + linux-kernel@vger.kernel.org Paul Mackerras <paulus@samba.org> - " linuxppc-dev@lists.ozlabs.org\0" + linuxppc-dev@lists.ozlabs.org + " David Gibson <david@gibson.dropbear.id.au>\0" "\00:1\0" "b\0" "On 05/29/2013 06:29:13 PM, Alexey Kardashevskiy wrote:\n" "> On 05/30/2013 09:14 AM, Scott Wood wrote:\n" "> > On 05/29/2013 06:10:33 PM, Alexey Kardashevskiy wrote:\n" "> >> On 05/30/2013 06:05 AM, Scott Wood wrote:\n" - "> >> > But you didn't put it in the same section as \n" + "> >> > But you didn't put it in the same section as =20\n" "> KVM_CREATE_SPAPR_TCE. 0xe0\n" "> >> > begins a different section.\n" "> >>\n" - "> >> It is not really obvious that there are sections as no comment \n" + "> >> It is not really obvious that there are sections as no comment =20\n" "> defines\n" "> >> those :)\n" "> >\n" - "> > There is a comment /* ioctls for fds returned by KVM_CREATE_DEVICE \n" + "> > There is a comment /* ioctls for fds returned by KVM_CREATE_DEVICE =20\n" "> */\n" "> >\n" - "> > Putting KVM_CREATE_DEVICE in there was mainly to avoid dealing with \n" + "> > Putting KVM_CREATE_DEVICE in there was mainly to avoid dealing with =20\n" "> the\n" - "> > ioctl number conflict mess in the vm-ioctl section, but at least \n" + "> > ioctl number conflict mess in the vm-ioctl section, but at least =20\n" "> that one\n" "> > is related to the device control API. :-)\n" "> >\n" - "> >> But yes, makes sense to move it up a bit and change the code to \n" + "> >> But yes, makes sense to move it up a bit and change the code to =20\n" "> 0xad.\n" "> >\n" "> > 0xad is KVM_KVMCLOCK_CTRL\n" - "> \n" + ">=20\n" "> That's it. I am _completely_ confused now. No system whatsoever :(\n" - "> What rule should I use in order to choose the number for my new \n" + "> What rule should I use in order to choose the number for my new =20\n" "> ioctl? :)\n" "\n" "Yeah, it's a mess. 0xaf seems to be free. :-)\n" "\n" - -Scott + -Scott= -eae867d43d96c12025ea75357637ecd3305469587a6606d2981af811cd5a76b4 +7a46edb016bf952812d39e83d61ef83497fa9ab09326e85e88acf9a14d56eca2
diff --git a/a/content_digest b/N2/content_digest index 043b667..dfdb2d4 100644 --- a/a/content_digest +++ b/N2/content_digest @@ -8,15 +8,15 @@ "ref\051A68F49.6020908@ozlabs.ru\0" "From\0Scott Wood <scottwood@freescale.com>\0" "Subject\0Re: [PATCH 3/4] KVM: PPC: Add support for IOMMU in-kernel handling\0" - "Date\0Wed, 29 May 2013 23:32:45 +0000\0" + "Date\0Wed, 29 May 2013 18:32:45 -0500\0" "To\0Alexey Kardashevskiy <aik@ozlabs.ru>\0" "Cc\0David Gibson <david@gibson.dropbear.id.au>" - kvm@vger.kernel.org - linux-kernel@vger.kernel.org - kvm-ppc@vger.kernel.org + <kvm@vger.kernel.org> + <linux-kernel@vger.kernel.org> + <kvm-ppc@vger.kernel.org> Alexander Graf <agraf@suse.de> Paul Mackerras <paulus@samba.org> - " linuxppc-dev@lists.ozlabs.org\0" + " <linuxppc-dev@lists.ozlabs.org>\0" "\00:1\0" "b\0" "On 05/29/2013 06:29:13 PM, Alexey Kardashevskiy wrote:\n" @@ -53,4 +53,4 @@ "\n" -Scott -eae867d43d96c12025ea75357637ecd3305469587a6606d2981af811cd5a76b4 +530ebc1dfac8b367e4df4a9125bf03c5cb38a988e3564715a2c955b6dcda7b83
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.