public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Chuck Ebbert <cebbert@redhat.com>
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: Mon, 14 Jan 2008 11:33:05 +0100	[thread overview]
Message-ID: <20080114103305.GA27977@elte.hu> (raw)
In-Reply-To: <478670BA.6010600@redhat.com>


* Chuck Ebbert <cebbert@redhat.com> 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.
> 
> Using the same logic, why not put it in 2.6.24 and then remove it in 
> 2.6.24.1 if it's broken?

hm, did you understood my .25 reference to mean 2.6.25-final? I meant 
2.6.25-rc1. Or if there's a 2.6.24-rc8 planned then we could put it in 
right now [with the bisectability fixes, i.e. not the original series]. 
I.e. IMO what we shouldnt do is to put in these fixes without having had 
_some_ -rc release inbetween.

	Ingo

      reply	other threads:[~2008-01-14 10:33 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
2008-01-10 19:23   ` Chuck Ebbert
2008-01-14 10:33     ` 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=20080114103305.GA27977@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@infradead.org \
    --cc=cebbert@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --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