public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Fenzi <kevin-+bl/7iUgRMUAvxtiuMwx3w@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: redhat comment about intel not taking patches?
Date: Mon, 10 Feb 2003 11:16:05 -0700	[thread overview]
Message-ID: <20030210181607.2876.qmail@scrye.com> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


RedHat is playing with enabling ACPI in their next release. (At least
in the beta for the next release: phoebe). 

Noticed this changelog comment in the phoebe kernel: 

* Thu Nov 07 2002 Arjan van de Ven <arjanv-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
- - remove ACPI again because Intel is unwilling to take patches

What patches are they talking about? 

Is there any way we could fix up the communication breakdown between
RedHat/Intel?

It would be great if ACPI would work out of the box on my laptop with
a RedHat kernel. At a minimum I guess it would require acpi to be able
to detect the compaq *PNP stuff and remove the * so the table works. 

Any comments/thoughts?

kevin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>

iD8DBQE+R+xn3imCezTjY0ERAle1AJ0WGVKSRzTTXYU+Y5R3Ie+VszaKaQCeNFDY
9gfOUY3HK9arInbqQcBlZiQ=
=kDHa
-----END PGP SIGNATURE-----


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com

             reply	other threads:[~2003-02-10 18:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-10 18:16 Kevin Fenzi [this message]
     [not found] ` <20030210181607.2876.qmail-+bl/7iUgRMUAvxtiuMwx3w@public.gmane.org>
2003-02-10 21:43   ` redhat comment about intel not taking patches? Alan Cox
  -- strict thread matches above, loose matches on Subject: below --
2003-02-12 21:24 Grover, Andrew
     [not found] ` <F760B14C9561B941B89469F59BA3A84725A175-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
2003-02-13  2:55   ` Darren Benham
2003-02-13  4:11 Cagle, John (ISS-Houston)
     [not found] ` <C50AB9511EE59B49B2A503CB7AE1ABD10440E3DB-Iar2LzuD2f6P0FQRY6S+e9kSKC0Mw0DFJ8am2ALHCgk@public.gmane.org>
2003-02-13  7:58   ` Darren Benham
2003-02-13 11:11   ` Dave Jones
2003-02-14 14:21 Cagle, John (ISS-Houston)

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=20030210181607.2876.qmail@scrye.com \
    --to=kevin-+bl/7iugrmuavxtiumwx3w@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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