From: "Grover, Andrew" <andrew.grover@intel.com>
To: "'Pavel Machek'" <pavel@ucw.cz>
Cc: "'Arjan van de Ven'" <arjanv@redhat.com>,
marcelo@conectiva.com.br, linux-kernel@vger.kernel.org,
acpi-devel@sourceforge.net
Subject: RE: [BK PATCH] ACPI updates
Date: Thu, 5 Dec 2002 17:36:02 -0800 [thread overview]
Message-ID: <EDC461A30AC4D511ADE10002A5072CAD04C7A576@orsmsx119.jf.intel.com> (raw)
> From: Pavel Machek [mailto:pavel@ucw.cz]
I (Andy) said:
> > Well maybe that's what we should do - use the UnitedLinux
> ACPI patch (which
> > iirc is based on fairly recent ACPI code, and presumably minimizes
> > ACPI-related breakage) and then proceed incrementally from there?
> >
> > Sound OK? Marcelo? UL folks?
> I guess it will be better if you push acpi patch without killing those
> backup solutions. Extractign blacklist from UL might be worth it,
> through.
Well after communicating with Marcelo it sounds like he'd like to hold off
taking it in 2.4.21 because IDE changes take priority, and two big changes
at once is too many for a stable kernel revision.
Fair enough. I'm just worried that 2.4.22 is a long ways away.
Maybe one way to address Marcelo's stability concerns and Arjan's "keep
acpitable.[ch] around" preference is for me to submit a patch that I *know*
don't affect anything besides ACPI -- i.e. only the changes that have been
made under drivers/acpi, and then go from there, submitting UL-derived and
other improvements incrementally after that.
Thoughts?
Regards -- Andy
next reply other threads:[~2002-12-06 1:28 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-06 1:36 Grover, Andrew [this message]
2002-12-06 11:59 ` [ACPI] " Hanno Böck
2002-12-06 12:29 ` Arjan van de Ven
2002-12-06 13:17 ` Matthew Wilcox
2002-12-06 15:06 ` Alan Cox
2002-12-09 16:09 ` Marcelo Tosatti
2002-12-09 19:12 ` Matthew Wilcox
2002-12-09 19:17 ` Arjan van de Ven
2002-12-09 19:45 ` Bjorn Helgaas
2002-12-09 19:17 ` Jeff Garzik
2002-12-06 16:50 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2003-05-24 0:15 Grover, Andrew
2002-12-03 23:29 Grover, Andrew
2002-12-03 23:47 ` Arjan van de Ven
2002-12-04 12:58 ` Dave Jones
2002-12-05 17:06 ` Pavel Machek
2002-12-03 18:39 Grover, Andrew
2002-12-03 19:31 ` Alan Cox
2002-12-03 23:00 ` Arjan van de Ven
2002-12-02 19:29 Grover, Andrew
2002-12-03 9:31 ` Arjan van de Ven
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=EDC461A30AC4D511ADE10002A5072CAD04C7A576@orsmsx119.jf.intel.com \
--to=andrew.grover@intel.com \
--cc=acpi-devel@sourceforge.net \
--cc=arjanv@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=pavel@ucw.cz \
/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
all inboxes | Powered by JetHome®