public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: "Grover, Andrew" <andrew.grover@intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: must-fix list, v5
Date: Thu, 22 May 2003 01:31:01 -0700	[thread overview]
Message-ID: <20030522013101.7181cdb0.akpm@digeo.com> (raw)
In-Reply-To: <F760B14C9561B941B89469F59BA3A84725A2B5@orsmsx401.jf.intel.com>

"Grover, Andrew" <andrew.grover@intel.com> wrote:
>
> 
> > From: Andrew Morton [mailto:akpm@digeo.com] 
> 
> Hi just wanted to add some comments below:

Appreciated, thanks.

> >  drivers/acpi/
> >  ~~~~~~~~~~~~~
> >  
> >  o davej: ACPI has a number of failures right now.  There are 
> ...
> 
> Working on these (they're all in bugzilla), more help needed of course
> :)

OK, well if they're safely bugzilla'd I shall remove them from here. 
Unless you think they're drop-dead stop-ship material.

> > +o mochel: it seems the acpi irq routing code could use a 
> > serious rewrite.
> 
> No the problem is the ACPI irq routing code is trying to piggyback on
> the existing MPS-specific data structures, and it's generally a hack. So
> yes mochel is right, but it is also purging MPS-ities from common code
> as well. I've done some preliminary work in this area and it doesn't
> seem to break anything (yet) but a rewrite in this area imho should not
> be rushed out the door. And, I think the above bugs can be fixed w/o the
> rewrite.

Where do you think this work sits on the seriousness scale?  Is it
affecting a lot of people?  Is it a large-scale restructure?

It sounds to me like it's a non-trivial piece of ACPI brain surgery and
that I should continue to track it, yes?


  reply	other threads:[~2003-05-22  8:15 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-22  8:16 must-fix list, v5 Grover, Andrew
2003-05-22  8:31 ` Andrew Morton [this message]
2003-05-22 14:23   ` Jos Hulzink
     [not found] <20030521152255.4aa32fba.akpm@digeo.com.suse.lists.linux.kernel>
     [not found] ` <20030521152334.4b04c5c9.akpm@digeo.com.suse.lists.linux.kernel>
     [not found]   ` <20030526093717.GC642@zaurus.ucw.cz.suse.lists.linux.kernel>
     [not found]     ` <20030528144839.47efdc4f.akpm@digeo.com.suse.lists.linux.kernel>
     [not found]       ` <20030528215551.GB255@elf.ucw.cz.suse.lists.linux.kernel>
2003-05-29  9:17         ` Andi Kleen
2003-05-29  9:32           ` David S. Miller
2003-05-29  9:46             ` Pavel Machek
2003-05-29 10:01               ` David S. Miller
2003-05-29 10:03                 ` Pavel Machek
2003-05-29  9:46             ` Andi Kleen
2003-05-29 10:01               ` David S. Miller
2003-05-29 11:25             ` Pavel Machek
2003-05-29 11:26               ` David S. Miller
2003-05-29 11:39                 ` Arjan van de Ven
2003-05-29 20:10                   ` Pavel Machek
2003-05-29 20:06             ` Pavel Machek
2003-05-29 21:15               ` David S. Miller
  -- strict thread matches above, loose matches on Subject: below --
2003-05-21 23:59 Arnd Bergmann
2003-05-21 22:22 Andrew Morton
2003-05-21 22:23 ` Andrew Morton
2003-05-21 22:49   ` Tom Rini
2003-05-21 22:55     ` Andrew Morton
2003-05-26  9:37   ` Pavel Machek
2003-05-28 21:48     ` Andrew Morton
2003-05-28 21:55       ` Pavel Machek
2003-05-28 22:06         ` Andrew Morton
     [not found]           ` <20030528221812.GC255@elf.ucw.cz>
2003-05-28 22:46             ` Andrew Morton
2003-05-28 23:03               ` Pavel Machek
2003-05-29 11:13               ` Pavel Machek
2003-05-21 22:41 ` Andrew Morton
2003-05-22  1:03 ` Carl-Daniel Hailfinger
2003-05-22  3:08   ` oxymoron
2003-05-22  1:25 ` Andrew Theurer
2003-05-22  6:24 ` Jens Axboe
2003-05-25 21:05 ` Daniel Jacobowitz

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=20030522013101.7181cdb0.akpm@digeo.com \
    --to=akpm@digeo.com \
    --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