The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Len Brown <len.brown@intel.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux 2.6.0 (ACPI)
Date: 18 Dec 2003 02:55:23 -0500	[thread overview]
Message-ID: <1071734123.2497.66.camel@dhcppc4> (raw)
In-Reply-To: <BF1FE1855350A0479097B3A0D2A80EE001B57534@hdsmsx402.hd.intel.com>

> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/must-fix/should-fix-7.txt

We have 88 open bugs against ACPI (out of 216 total).  They fall into
two broad categories -- boot/configuration (eg. interrupt issues); and
run-time features (eg. acpi events -- power-down, fan control etc). 
#1038 mentioned here has sort of grown out of control into "anything at
all wrong with anybody's IBM T40", so I'm not sure it will ever be
completely closed;-)

I agree with Andy Grover's comments in this file that fixing the bugs
one by one in the current design is the highest priority; and I think
that strategy is showing positive results.

>   fixes appear in Andrew Morton's "-mm" tree, at
> 
>         ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/
> 

Now that you're back, we should probably pull the current 2.6.0 ACPI
patch into the mm tree, since 2.6 without it is now somewhat behind
2.4.23.

I understand that consolidated plain patches are preferred for the mm
tree.  I assume that the actual pull into the release tree can still be
done using bk so that we can preserve the individual csets and their
comments?

> Some active subsystem mailing lists
>   are:

>         linux-acpi@intel.com

acpi-devel@lists.sourceforge.net is preferred -- it includes the Intel
alias above plus the rest of planet ACPI.

thanks,
-Len



       reply	other threads:[~2003-12-18  7:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BF1FE1855350A0479097B3A0D2A80EE001B57534@hdsmsx402.hd.intel.com>
2003-12-18  7:55 ` Len Brown [this message]
2003-12-18  8:05   ` Linux 2.6.0 (ACPI) Jeff Garzik
2003-12-18  8:12   ` Andrew Morton

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=1071734123.2497.66.camel@dhcppc4 \
    --to=len.brown@intel.com \
    --cc=akpm@osdl.org \
    --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