[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6AE080B68D46FC4BA2D2769E68D765B7080FA9F8@039-SN2MPN1-023.039d.mgd.msft.net>
Date: Thu, 11 Oct 2012 03:32:46 +0000
From: Tabi Timur-B04825 <B04825@...escale.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>
CC: Alexander Graf <agraf@...e.de>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Yoder Stuart-B08248 <B08248@...escale.com>,
David Howells <dhowells@...hat.com>,
"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
Paul Mackerras <paulus@...ba.org>,
"linuxppc-dev@...ts.ozlabs.org" <linuxppc-dev@...ts.ozlabs.org>
Subject: Re: linux-next: manual merge of the kvm-ppc tree with the
powerpc-merge tree
On Wed, Oct 10, 2012 at 9:47 PM, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Commit 549d62d889b4 ("KVM: PPC: use definitions in epapr header
> for hcalls") from the kvm-ppc tree added an include of asm/epapr_hcall.h
> to the user visible part of asm/kvm_para.h so asm/epapr_hcall.h became a
> user visible header file.
Any real user-space code that tries to call any of the functions in
epapr_hcall.h will cause an exception.
Claiming that kernel header files that KVM needs are suddenly
user-space header files doesn't make much sense to me, but I guess
it's not my decision.
--
Timur Tabi
Linux kernel developer at Freescale
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists