LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Yinghai Lu <yinghai@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <peterz@infradead.org>,
Mukesh Rathor <mukesh.rathor@oracle.com>
Subject: linux-next: build failure after merge of the xen-two tree
Date: Mon, 4 Feb 2013 15:14:56 +1100 [thread overview]
Message-ID: <20130204151456.ea053895a487a19013e4991f@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1543 bytes --]
Hi Konrad,
After merging the xen-two tree, today's linux-next build (x86_64
allmodconfig) failed like this:
arch/x86/xen/mmu.c: In function 'xen_init_mmu_ops':
arch/x86/xen/mmu.c:2213:10: error: 'struct x86_init_ops' has no member named 'mapping'
arch/x86/xen/mmu.c:2213:39: error: 'xen_mapping_pagetable_reserve' undeclared (first use in this function)
Caused by commit 8154d7a6b9b9 ("xen/pvh: Implement MMU changes for PVH")
from the xen-two tree interacting with commit 6f80b68e9e51 ("x86, mm,
Xen: Remove mapping_pagetable_reserve()") from the tip tree. The
automatic merge left the moved version of the above line intact while it
should have been removed (I assume).
I have added the following merge fix patch and can carry the fix as
necessary.
From: Stephen Rothwell <sfr@canb.auug.org.au>
Date: Mon, 4 Feb 2013 15:08:33 +1100
Subject: [PATCH] xen: fix bad merge of arch/x86/xen/mmu.c
Signed-off-by: Stephen Rothwell <sfr@canb.auug.org.au>
---
arch/x86/xen/mmu.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/arch/x86/xen/mmu.c b/arch/x86/xen/mmu.c
index 824706a..3228600 100644
--- a/arch/x86/xen/mmu.c
+++ b/arch/x86/xen/mmu.c
@@ -2210,7 +2210,6 @@ void __init xen_init_mmu_ops(void)
pv_mmu_ops.flush_tlb_others = xen_flush_tlb_others;
return;
}
- x86_init.mapping.pagetable_reserve = xen_mapping_pagetable_reserve;
pv_mmu_ops = xen_mmu_ops;
memset(dummy_mapping, 0xff, PAGE_SIZE);
--
1.8.1
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2013-02-04 4:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-04 4:14 Stephen Rothwell [this message]
2013-02-05 18:30 ` Konrad Rzeszutek Wilk
2013-03-02 15:39 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2013-02-15 4:45 Stephen Rothwell
2013-02-15 13:26 ` Konrad Rzeszutek Wilk
2013-02-15 13:50 ` Stephen Rothwell
2013-02-15 14:53 ` Rafael J. Wysocki
2013-02-15 14:52 ` Stephen Rothwell
2013-02-15 17:46 ` Liu, Jinsong
2013-02-16 20:11 ` Rafael J. Wysocki
2013-02-17 7:31 ` Liu, Jinsong
2013-02-17 14:08 ` Rafael J. Wysocki
2013-02-20 20:49 ` Konrad Rzeszutek Wilk
2013-02-20 21:24 ` Rafael J. Wysocki
2013-02-21 6:40 ` Liu, Jinsong
2013-02-15 17:20 ` Liu, Jinsong
2013-02-15 17:08 ` Liu, Jinsong
2012-10-02 4:33 Stephen Rothwell
2011-02-10 4:46 Stephen Rothwell
2011-02-10 12:24 ` Thomas Gleixner
2011-02-10 15:22 ` Konrad Rzeszutek Wilk
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130204151456.ea053895a487a19013e4991f@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=hpa@zytor.com \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mukesh.rathor@oracle.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=yinghai@kernel.org \
--subject='Re: linux-next: build failure after merge of the xen-two tree' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).