From: Grzegorz Jaskiewicz <gj@pointblue.com.pl>
To: "Grover, Andrew" <andrew.grover@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.21-rc7 ACPI broken
Date: Wed, 4 Jun 2003 21:37:57 +0100 [thread overview]
Message-ID: <200306042138.00895@gjs> (raw)
In-Reply-To: <F760B14C9561B941B89469F59BA3A847E96F25@orsmsx401.jf.intel.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wednesday 04 of June 2003 21:49, you wrote:
> > From: Grzegorz Jaskiewicz [mailto:gj@pointblue.com.pl]
> >
> > > > ACPI: Core Subsystem version [20011018]
> > >
> > > Old ACPI code, get patch from http://sf.net/projects/acpi
> >
> > and report back
> >
> > > if problems persist.
> >
> > Any chance to get patch against latest -rc7 ?
>
> It's big, and deemed too risky. We are shooting for 2.4.22-pre1.
I am just recompliling at the moment :D
Anyway, ACPI is a one of projects that is not well synchronized in kernel.
Latest version 2001.... .. hmm 2 years :]
It will be good to have always newest one in kernel (at least in stable
release version)
- --
Grzegorz Jaskiewicz
K4 Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
iD8DBQE+3lioqu082fCQYIgRAi0BAJ4tp4J1z90xDTTwHD89ZmcwxGNydACfehuB
6ccFu+5ngcwxHxICUUtVpOo=
=X2fo
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2003-06-04 20:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-04 20:49 2.4.21-rc7 ACPI broken Grover, Andrew
2003-06-04 20:37 ` Grzegorz Jaskiewicz [this message]
2003-06-04 21:16 ` Grzegorz Jaskiewicz
2003-06-09 20:32 ` 2.4.22 timeline was " Marcelo Tosatti
2003-06-10 0:47 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2003-06-04 21:42 Grover, Andrew
2003-06-04 20:58 Grover, Andrew
2003-06-04 18:01 Grover, Andrew
2003-06-04 20:27 ` Grzegorz Jaskiewicz
2003-06-04 21:31 ` Alan Cox
2003-06-12 16:32 ` Martin MOKREJŠ
2003-06-12 16:42 ` iain d broadfoot
2003-06-12 17:54 ` Martin MOKREJŠ
2003-06-04 17:49 Martin MOKREJŠ
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=200306042138.00895@gjs \
--to=gj@pointblue.com.pl \
--cc=andrew.grover@intel.com \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).