public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephan von Krawczynski <skraw@ithnet.com>
To: marcelo@conectiva.com.br
Cc: andrew.grover@intel.com, gj@pointblue.com.pl,
	linux-kernel@vger.kernel.org, sunil.saxena@intel.com,
	len.brown@intel.com, guy.therien@intel.com,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: 2.4.22 timeline was RE: 2.4.21-rc7 ACPI broken
Date: Tue, 10 Jun 2003 17:14:44 +0200	[thread overview]
Message-ID: <20030610171444.1aff1d3c.skraw@ithnet.com> (raw)
In-Reply-To: <1055205899.31139.15.camel@dhcp22.swansea.linux.org.uk>

On 10 Jun 2003 01:44:59 +0100
Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:

> On Llu, 2003-06-09 at 23:03, Marcelo Tosatti wrote:
> > Yes, I want to, and will merge it. In 2.4.23-pre.
> > 
> > > I am confident it will merge cleanly.
> > > I am confident it will cause no problems when CONFIG_ACPI=off.
> > > I am confident the total number of working machines will go up.
> > > I am willing to bet $500 of MY OWN MONEY on this.
> > >
> > > Talk to me, man. What would make you happy? A lot is riding on this.
> > 
> > Yes, we're fine. 2.4.23-pre.
> > 
> > 2.4.22 will be a fast enough release to not piss you off on this, trust
> > me.
> 
> Its been in 2.4.21-ac for a while. I have exactly zero reports of it
> causing problems in the acpi=n case, and a whole raft of "the first
> Linux that runs on my toshiba/compaq/hp laptop"
> 
> Works well enough for me to have faith in it now. 

I can back that. In fact I have some SIS-based motherboards that do not run
without the acpi patch.

My personal opinion on the topic "what to put in 2.4.22-pre1?" is:
1) aic (because you can kick Justins' a** if it does not work out, and get rid
of any complaints for what you do yourself to the aic code)
2) acpi (because the code has already gone through some significant testing and
looks promising).

So I guess I would just do the opposite of your current statement. Remember, you
have a chance to win 500 bucks, don't let it go ;-)

Regards,
Stephan


  parent reply	other threads:[~2003-06-10 15:01 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-09 21:21 2.4.22 timeline was RE: 2.4.21-rc7 ACPI broken Grover, Andrew
2003-06-09 21:24 ` Grzegorz Jaskiewicz
2003-06-09 22:03 ` Marcelo Tosatti
2003-06-10  0:44   ` Alan Cox
2003-06-10 11:05     ` Torben Mathiasen
2003-06-10 15:14     ` Stephan von Krawczynski [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-06-10 23:40 Eric Valette
2003-06-11 21:15 ` Adrian Bunk
2003-06-12 11:47   ` Eric Valette
2003-06-12 14:05   ` Stephan von Krawczynski
2003-06-12 16:32     ` Eric Valette
2003-06-17 23:25 ` Marcelo Tosatti
2003-06-17 23:58   ` J.A. Magallon
2003-06-18 20:27     ` Marcelo Tosatti
2003-06-18  5:15   ` Anders Karlsson
2003-06-18 16:55     ` Bill Nottingham
2003-06-18  9:04   ` Eric Valette
2003-06-09 23:27 Grover, Andrew
2003-06-09 22:38 Margit Schubert-While
2003-06-10  0:08 ` Marcelo Tosatti
2003-06-09 21:47 Margit Schubert-While
2003-06-09 21:07 Margit Schubert-While
2003-06-04 20:49 Grover, Andrew
2003-06-09 20:32 ` 2.4.22 timeline was " Marcelo Tosatti
2003-06-10  0:47   ` Alan Cox

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=20030610171444.1aff1d3c.skraw@ithnet.com \
    --to=skraw@ithnet.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=andrew.grover@intel.com \
    --cc=gj@pointblue.com.pl \
    --cc=guy.therien@intel.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=sunil.saxena@intel.com \
    /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