public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed

From: Thomas Meyer <thomas@m3y3r•de>
To: Ingo Molnar <mingo@elte•hu>
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: Mon, 02 Jun 2008 19:40:04 +0200	[thread overview]
Message-ID: <1212428404.484430742e07d@213.133.104.17> (raw)
In-Reply-To: <20080601150710.GB27843@elte.hu>

Zitat von Ingo Molnar <mingo@elte•hu>:

> 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.

I just booted next-20080602 successfully, and the latest commit on file
arch/x86/kernel/setup_32.c is:

4efc5450e19128e0c77fbfdf4a14804f5a4a1d95 (Merge branch 'x86/numa' into
auto-x86-next).

So yes, the original commit causing the error for me is gone.

Thanks and greets.
thomas

next prev parent reply	other threads:[~2008-06-02 17:40 UTC|newest]

Thread overview: 19+ 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
2008-06-02 17:40     ` Thomas Meyer [this message]
2008-06-02 18:57       ` Ingo Molnar
  -- strict thread matches above, loose matches on Subject: below --
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
2025-05-30  3:24 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=1212428404.484430742e07d@213.133.104.17 \
    --to=thomas@m3y3r$(echo .)de \
    --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 \
    --cc=yhlu.kernel@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox