public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@kernel.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: Arjan van de Ven <arjan@infradead.org>,
	linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
	torvalds@linux-foundation.org
Subject: Re: Fix x86 32 bit FRAME_POINTER chasing code
Date: Thu, 10 Jan 2008 13:01:15 +0200	[thread overview]
Message-ID: <20080110110115.GD28740@does.not.exist> (raw)
In-Reply-To: <20080110065438.GA23022@elte.hu>

On Thu, Jan 10, 2008 at 07:54:38AM +0100, Ingo Molnar wrote:
>...
> it's a 2.6.24.1 candidate i believe. We trigger plenty of various 
> crashes during x86.git maintenance and others hit various crashes in 
> -mm, so by the time .1 is released we'll have it in .25 and can backport 
> it. Most folks/distros will update to 2.6.24.1 very quickly so there's 
> no risk of months loss of quality to kerneloops.org data either.
>...

-stable should not introduce additional regressions, and my personal 
impression is that it already introduces too many regressions.

Either this patch is considered both important and safe enough for 
getting into Linus' tree now or it's simply too late for 2.6.24*

> 	Ingo

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2008-01-10 11:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-10  6:04 Fix x86 32 bit FRAME_POINTER chasing code Arjan van de Ven
2008-01-10  6:54 ` Ingo Molnar
2008-01-10 11:01   ` Adrian Bunk [this message]
2008-01-10 19:23   ` Chuck Ebbert
2008-01-14 10:33     ` Ingo Molnar

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=20080110110115.GD28740@does.not.exist \
    --to=bunk@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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