From: "Rafael J. Wysocki" <rjw@sisk•pl>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
Ingo Molnar <mingo@elte•hu>,
Jeremy Fitzhardinge <jeremy@goop•org>,
kernel-testers@vger•kernel.org
Subject: Re: linux-next: Tree for July 3
Date: Sat, 5 Jul 2008 12:38:54 +0200 [thread overview]
Message-ID: <200807051238.55044.rjw@sisk.pl> (raw)
In-Reply-To: <200807040154.16200.rjw@sisk.pl>
On Friday, 4 of July 2008, Rafael J. Wysocki wrote:
> On Thursday, 3 of July 2008, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since next-20080702:
> >
> > New trees: kmemcheck and generic-ipi.
> >
> > The pci tree gained a conflict against the driver-core tree.
> >
> > The powerpc tree gained a conflict against the i2c tree.
> >
> > The net tree gained a couple of conflicts against Linus' tree and the
> > wireless-current tree.
> >
> > The wireless tree gained a couple of conflicts against the
> > wireless-current tree.
> >
> > The rr tree lost its two build fixup patches but gained another conflict
> > against the sched tree.
> >
> > The blk-removal tree lost its conflict with the s390 tree.
> >
> > The kmemcheck tree gained conflicts against the ftrace, sched, and x86
> > trees.
> >
> > The generic-ipi tree gained conflicts against the powerpc, kmemcheck and
> > net trees. And had two build failures requiring a patch and a revert.
> >
> > I have also applied the following patches for known problems (I assume
> > that these will be merged into their appropriate trees shortly):
> >
> > NFS: Fix the mount protocol defaults for binary mounts
> > fix "ftrace: store mcount address in rec->ip"
> >
> > There are several outstanding build failures due to structural changes in
> > the ttydev tree (see http://kisskb.ellerman.id.au/linux-next).
>
> This tree didn't compile for me on x86-64.
>
> After adding the appended patch it started to compile, but it doesn't boot
> (hangs very early, before any messages can get to the console).
>
> I'll bisect tomorrow if I have the time.
This problem is fixed by applying the appended patch.
Thanks,
Rafael
---
Author: Jeremy Fitzhardinge <jeremy@goop•org>
Date: Sun Jun 29 20:02:44 2008 -0700
x86: setup_arch() && early_ioremap_init()
Looks like the setup.c unification missed the early_ioremap init from
the early_ioremap unification. Unconditionally call early_ioremap_init().
needed for "x86/paravirt: groundwork for 64-bit Xen support".
Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix•com>
Cc: Nick Piggin <npiggin@suse•de>
Cc: Mark McLoughlin <markmc@redhat•com>
Cc: xen-devel <xen-devel@lists•xensource.com>
Cc: Eduardo Habkost <ehabkost@redhat•com>
Cc: Vegard Nossum <vegard.nossum@gmail•com>
Cc: Stephen Tweedie <sct@redhat•com>
Cc: Yinghai Lu <yhlu.kernel@gmail•com>
Signed-off-by: Ingo Molnar <mingo@elte•hu>
diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c
index fb318ed..caec79f 100644
--- a/arch/x86/kernel/setup.c
+++ b/arch/x86/kernel/setup.c
@@ -523,12 +523,13 @@ void __init setup_arch(char **cmdline_p)
memcpy(&boot_cpu_data, &new_cpu_data, sizeof(new_cpu_data));
pre_setup_arch_hook();
early_cpu_init();
- early_ioremap_init();
reserve_setup_data();
#else
printk(KERN_INFO "Command line: %s\n", boot_command_line);
#endif
+ early_ioremap_init();
+
ROOT_DEV = old_decode_dev(boot_params.hdr.root_dev);
screen_info = boot_params.screen_info;
edid_info = boot_params.edid_info;
--
next prev parent reply other threads:[~2008-07-05 10:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 9:09 linux-next: Tree for July 3 Stephen Rothwell
2008-07-03 23:54 ` Rafael J. Wysocki
2008-07-05 10:38 ` Rafael J. Wysocki [this message]
2008-07-04 18:29 ` linux-next-0703 -- more ppc serial fixes Joseph Fannin
2008-07-04 19:51 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2009-07-03 6:24 linux-next: Tree for July 3 Stephen Rothwell
2012-07-03 5:50 Stephen Rothwell
2012-07-03 5:54 ` Stephen Rothwell
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=200807051238.55044.rjw@sisk.pl \
--to=rjw@sisk$(echo .)pl \
--cc=jeremy@goop$(echo .)org \
--cc=kernel-testers@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@elte$(echo .)hu \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox