From: Ingo Molnar <mingo@elte.hu>
To: Jack Steiner <steiner@sgi.com>
Cc: tglx@linutronix.de, linux-kernel@vger.kernel.org,
Mike Travis <travis@sgi.com>,
the arch/x86 maintainers <x86@kernel.org>
Subject: Re: [PATCH] - Increase MAX_APICS for very large x86_64 configs
Date: Thu, 19 Jun 2008 17:19:40 +0200 [thread overview]
Message-ID: <20080619151940.GA14899@elte.hu> (raw)
In-Reply-To: <20080619151732.GA12964@elte.hu>
* Ingo Molnar <mingo@elte.hu> wrote:
> * Jack Steiner <steiner@sgi.com> wrote:
>
> > > unfortunately it didnt last long, -tip randconfig auto-testing found
> > > that your patch causes a bootup crash:
> >
> > I built a "git-checkout -b tip-latest tip/auto-latest" tree but get
> > compile errors. Is this the right tree??
>
> no, you should check out tip/master.
ah, i see - the readme was suggesting auto-latest - my bad. I've updated
the readme.
Ingo
prev parent reply other threads:[~2008-06-19 15:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-16 17:09 [PATCH] - Increase MAX_APICS for very large x86_64 configs Jack Steiner
2008-06-19 10:10 ` Ingo Molnar
2008-06-19 10:32 ` Ingo Molnar
2008-06-19 15:02 ` Jack Steiner
2008-06-19 15:17 ` Ingo Molnar
2008-06-19 15:19 ` Ingo Molnar [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=20080619151940.GA14899@elte.hu \
--to=mingo@elte.hu \
--cc=linux-kernel@vger.kernel.org \
--cc=steiner@sgi.com \
--cc=tglx@linutronix.de \
--cc=travis@sgi.com \
--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