From: Ingo Molnar <mingo@elte.hu>
To: Thomas Meyer <thomas@m3y3r.de>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Yinghai Lu <yhlu.kernel@gmail.com>
Subject: Re: linux-next: Tree for May 30
Date: Sun, 1 Jun 2008 17:07:10 +0200 [thread overview]
Message-ID: <20080601150710.GB27843@elte.hu> (raw)
In-Reply-To: <1212316424.3253.8.camel@dhcppc1>
* Thomas Meyer <thomas@m3y3r.de> wrote:
> Am Freitag, den 30.05.2008, 18:19 +1000 schrieb Stephen Rothwell:
> > Hi all,
> >
> > Changes since next-20080529:
>
> Last next kernel booting for me is next-20080527. I didn't try
> next-20080528, but next-20080529 and next-20080530 fail to boot.
>
> Git told me to revert a63ef28f149c113740c7e429072351078a8821c6 (x86:
> fix bootmem crash).
>
> After reverting above commit, next-20080530 boots again.
>
> Basicly I'm running Fedora 9 with the linux-next kernel.
>
> See attached screenshot of boot error.
hm, that commit is gone in latest tip - does tip/master boot fine for
you? It's:
http://people.redhat.com/mingo/tip.git/README
that commit was an interim fix that got removed meanwhile and replaced
with the real fixes.
Ingo
next prev parent reply other threads:[~2008-06-01 15:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-30 8:19 linux-next: Tree for May 30 Stephen Rothwell
2008-06-01 10:33 ` Thomas Meyer
2008-06-01 15:07 ` Ingo Molnar [this message]
2008-06-02 17:40 ` Thomas Meyer
2008-06-02 18:57 ` Ingo Molnar
2011-05-30 3:35 Stephen Rothwell
2013-05-30 6:33 Stephen Rothwell
2013-05-30 8:07 ` Geert Uytterhoeven
2013-06-03 6:36 ` Stephen Rothwell
2013-06-03 8:45 ` Nicolas Ferre
2013-06-04 8:04 ` Stephen Rothwell
2014-05-30 7:34 Stephen Rothwell
2016-05-30 3:22 Stephen Rothwell
2016-05-30 14:04 ` Sudip Mukherjee
2017-05-30 5:16 Stephen Rothwell
2018-05-30 11:45 Stephen Rothwell
2019-05-30 6:21 Stephen Rothwell
2023-05-30 5:29 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=20080601150710.GB27843@elte.hu \
--to=mingo@elte.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=thomas@m3y3r.de \
--cc=yhlu.kernel@gmail.com \
/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).