diff for duplicates of <1349973438.6903.4@snotra> diff --git a/a/1.txt b/N1/1.txt index cfcb414..3fa75f2 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1,17 +1,17 @@ On 10/11/2012 10:55:42 AM, Timur Tabi wrote: > Alexander Graf wrote: -> -> +>=20 +>=20 > > This is about kvm_host.h, which is the part that is exported to user -> > space. It usually contains constants and structs that are required +> > space. It usually contains constants and structs that are required =20 > for > > the API. -> +>=20 > Which API? I'm not familiar with KVM internals. -> -> My concern is that when I think of a user-space header file, I think +>=20 +> My concern is that when I think of a user-space header file, I think =20 > of a -> user-space application that calls ioctls. I know that KVM guest +> user-space application that calls ioctls. I know that KVM guest =20 > kernels > run as user-space processes, but that does not seem like a reason to > combine all of the header files that the KVM guest kernel needs with @@ -19,4 +19,4 @@ On 10/11/2012 10:55:42 AM, Timur Tabi wrote: So where should guest headers go? --Scott +-Scott= diff --git a/a/content_digest b/N1/content_digest index e3c8f9c..060b2a8 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -8,8 +8,8 @@ "Subject\0Re: linux-next: manual merge of the kvm-ppc tree with the powerpc-merge tree\0" "Date\0Thu, 11 Oct 2012 11:37:18 -0500\0" "To\0Timur Tabi <B04825@freescale.com>\0" - "Cc\0Alexander Graf <agraf@suse.de>" - Stephen Rothwell <sfr@canb.auug.org.au> + "Cc\0Stephen Rothwell <sfr@canb.auug.org.au>" + Alexander Graf <agraf@suse.de> linux-kernel@vger.kernel.org <linux-kernel@vger.kernel.org> David Howells <dhowells@redhat.com> linux-next@vger.kernel.org <linux-next@vger.kernel.org> @@ -19,18 +19,18 @@ "b\0" "On 10/11/2012 10:55:42 AM, Timur Tabi wrote:\n" "> Alexander Graf wrote:\n" - "> \n" - "> \n" + ">=20\n" + ">=20\n" "> > This is about kvm_host.h, which is the part that is exported to user\n" - "> > space. It usually contains constants and structs that are required \n" + "> > space. It usually contains constants and structs that are required =20\n" "> for\n" "> > the API.\n" - "> \n" + ">=20\n" "> Which API? I'm not familiar with KVM internals.\n" - "> \n" - "> My concern is that when I think of a user-space header file, I think \n" + ">=20\n" + "> My concern is that when I think of a user-space header file, I think =20\n" "> of a\n" - "> user-space application that calls ioctls. I know that KVM guest \n" + "> user-space application that calls ioctls. I know that KVM guest =20\n" "> kernels\n" "> run as user-space processes, but that does not seem like a reason to\n" "> combine all of the header files that the KVM guest kernel needs with\n" @@ -38,6 +38,6 @@ "\n" "So where should guest headers go?\n" "\n" - -Scott + -Scott= -6ab89207864282c29c8ed97e84cb2bf40d57fa8c1fb63a1890360a9b1a369b07 +54bde5878a62bb1141e9c3efeeaa38e701222edde6240dcb514e80ef72be8c4a
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.