From: Grzegorz Jaskiewicz <gj@pointblue.com.pl>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Guy Therien <guy.therien@intel.com>,
Len Brown <len.brown@intel.com>,
Sunil Saxena <sunil.saxena@intel.com>,
Andrew Grover <andrew.grover@intel.com>
Subject: Re: 2.4.22 timeline was RE: 2.4.21-rc7 ACPI broken
Date: Mon, 9 Jun 2003 22:24:20 +0100 [thread overview]
Message-ID: <200306092224.32663@gjs> (raw)
In-Reply-To: <F760B14C9561B941B89469F59BA3A84725A2DF@orsmsx401.jf.intel.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Monday 09 of June 2003 22:21, you wrote:
> > From: Marcelo Tosatti [mailto:marcelo@conectiva.com.br]
> >
> > > > Any chance to get patch against latest -rc7 ?
> > >
> > > It's big, and deemed too risky. We are shooting for 2.4.22-pre1.
> >
> > Just had a few thoughts about that and I want to have a fast 2.4.22
> > release (maximum two months). 2.4.21's development time was
> > unnaceptable.
In this world there should be no rush :-)
> > Lets do the ACPI merge in 2.4.23.
>
> I wouldn't have a problem with this, except that you've been deferring
> the ACPI merge for over a year. We've been maintaining this patch
> outside the mainline tree for EIGHTEEN MONTHS. Please stop leading me
> along. Will you EVER merge it?
>
> 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.
Well, Marcelo - i am happy with new ACPI, Alan does (otherwise it wouldn't be
included into ac tree). We will welcome it in 2.4.22-pre1 :]
Anyway, still ACPI does not work fully in my PCG-C1VE Sony Vaio. I don't know
if due to incompatibilities of this equipment ?
All other servers/desktops works perfectly fine for me :D
Thanks guys.
- --
Grzegorz Jaskiewicz
K4 Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE+5PsLqu082fCQYIgRAuaFAJ0RxLG8gj2/Lk2B+bxS7bxwcve4zgCghgzO
d7hfwJa81RyJ+ltxmBd+KIs=
=JkND
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-06-09 21:31 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 [this message]
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
-- 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=200306092224.32663@gjs \
--to=gj@pointblue.com.pl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andrew.grover@intel.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.