From: Glauber Costa <gcosta@redhat.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: tglx@linutronix.de, hpa@zytor.com, linux-kernel@vger.kernel.org,
x86@kernel.org
Subject: Re: [GIT PULL] new shot at time.c integration
Date: Mon, 18 Aug 2008 10:16:56 -0300 [thread overview]
Message-ID: <20080818131656.GA13914@poweredge.glommer> (raw)
In-Reply-To: <20080816151900.GA27040@elte.hu>
On Sat, Aug 16, 2008 at 05:19:00PM +0200, Ingo Molnar wrote:
>
> * Ingo Molnar <mingo@elte.hu> wrote:
>
> > > Ingo, please pull the latest master git tree from:
> > >
> > > git://git.kernel.org/pub/scm/linux/kernel/git/glommer/linux-2.6-x86-integration.git master
> > >
> > > into your tree
> > >
> > > It is based on your tip/master branch.
> >
> > thanks, i've pulled it and rebased it to -git - as that's the best
> > base this early in the cycle. I've pushed out the result into
> > tip/x86/time - havent integrated it into tip/master yet.
>
> have just tried a test-merge, and got a few crashes during -tip testing.
> One is a hard lockup during bootup, with this config:
>
> http://redhat.com/~mingo/misc/config-Sat_Aug_16_16_49_05_CEST_2008.bad
>
> no console output. I've pushed out this integrated tree into
> tip/x86/time.broken: note that i had to do a few manual merges due to
> the io_apic.c unification - maybe that interacted.
>
> there's a 32-bit failure as well:
>
> http://redhat.com/~mingo/misc/config-Sat_Aug_16_15_51_57_CEST_2008.bad
>
> i dont know anything about that, other that it didnt boot up after
> x86/time integration.
>
ok ingo. Will look at that ASAP.
> Ingo
prev parent reply other threads:[~2008-08-18 13:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-15 16:25 [GIT PULL] new shot at time.c integration Glauber Costa
2008-08-15 16:51 ` Ingo Molnar
2008-08-16 15:19 ` Ingo Molnar
2008-08-18 13:16 ` Glauber Costa [this message]
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=20080818131656.GA13914@poweredge.glommer \
--to=gcosta@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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
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;
as well as URLs for NNTP newsgroup(s).