public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Travis <travis@sgi.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Thomas Gleixner <tglx@linutronix.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	"H. Peter Anvin" <hpa@zytor.com>, Jack Steiner <steiner@sgi.com>
Subject: Re: [git pull] core/percpu for v2.6.27
Date: Fri, 25 Jul 2008 08:18:51 -0700	[thread overview]
Message-ID: <4889EEDB.3070501@sgi.com> (raw)
In-Reply-To: <20080718221730.GB31073@elte.hu>

Ingo Molnar wrote:
> * Mike Travis <travis@sgi.com> wrote:
> 
>> Ingo Molnar wrote:
>>
>> ...
>>> in hindsight core/percpu indeed looks unfinished and direction-less 
>>> without core/percpu-zerobased - but the latter is not stable yet.
>>>
>>> 	Ingo
>> Well it's very stable using gcc-4.2.4.  The earlier problems came 
>> about using gcc-4.2.0 and has yet to be determined what exactly went 
>> wrong. (And I need to install gcc-3.2 to complete the build/test QA.)
> 
> well, the crash report i gave you was with gcc-4.2.3. Or is that one 
> resolved?
> 
> 	Ingo

YES!  Patcheset to follow... ;-)

Thanks,
Mike

      parent reply	other threads:[~2008-07-25 15:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-14 14:34 [git pull] core/percpu for v2.6.27 Ingo Molnar
2008-07-14 22:27 ` Linus Torvalds
2008-07-15 15:46   ` Jeremy Fitzhardinge
2008-07-15 21:00     ` Ingo Molnar
2008-07-15 21:26       ` Mike Travis
2008-07-15 21:46         ` H. Peter Anvin
2008-07-18 22:17         ` Ingo Molnar
2008-07-18 22:54           ` Mike Travis
2008-07-25 15:18           ` Mike Travis [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=4889EEDB.3070501@sgi.com \
    --to=travis@sgi.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=steiner@sgi.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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