From: Len Brown <len.brown@intel.com>
To: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
Cc: Matthew Wilcox <willy@debian.org>, Greg KH <greg@kroah.com>,
Arjan van de Ven <arjanv@redhat.com>,
linux-kernel@vger.kernel.org,
"linux-pci@atrey.karlin.mff.cuni.cz"
<linux-pci@atrey.karlin.mff.cuni.cz>
Subject: ACPI & 2.4 (Re: [BK PATCH] PCI Express patches for 2.4.27-pre3)
Date: 26 May 2004 03:35:34 -0400 [thread overview]
Message-ID: <1085556934.26254.132.camel@dhcppc4> (raw)
In-Reply-To: <A6974D8E5F98D511BB910002A50A6647615FC676@hdsmsx403.hd.intel.com>
Yes, the ACPI part to enable MMconfig was pretty small.
We parse a table in the standard way and set a global variable --
that's about it.
I submitted it to 2.4 for the sole purpose
to enable Greg to enable native PCIExpress.
I expect demand for this in 2.4 as the major distros'
enterprise releases are still 2.4 based and the hardware has
arrived... Your call, Marcelo, if this is something to
solve in upstream 2.4 or something the distros need
to solve for themselves. I recommend leaving the
small ACPI piece of the puzzle intact in either case.
On Tue, 2004-05-25 at 08:54, Marcelo Tosatti wrote:
> I've humbly asked Len to stop doing big updates
> whenever possible on the
> v2.4 ACPI code, and do bugfixes only instead. Is that a pain in the
> ass for you, Len?
>
> I asked that because it is common to see new bugs introduced by an
> ACPI update, and you know that more than I do.
At one point I released to 2.4 first because that is where
the useful testing feedback was; and then released to 2.5
to make sure it didn't fall behind.
Then I released to 2.4 and 2.6 simultaneously b/c
I got quick feeback from both camps.
Now we're into the era where the release-early
release-often matra applies to 26 only (or maybe more 2.6-mm)
and 2.4 is in maintenance mode.
I would still like to send some significant ACPI patches to 24.
Yes, they're 100% bugfixes -- sometimes bugfixes touch
lots of files too... But I'll do so only after the same
fix has been proven in 2.6 for a spell.
With some parts of ACPI, such as the ACPICA core interpreter
this is actually pretty low risk, because that part of
the kernel is identical between 2.4 and 2.6. So if 2.6 works,
so will 2.4.
Of course this also depends on if 2.4 will be accepting anything.
I recall talk back about 2.4.25 about the end of the 2.4 line.
I generally only have time to read LKML messages directed to me
or if the word "ACPI" appears in the message, so I may have missed
the word 2.4. What is the word?
thanks,
-Len
next parent reply other threads:[~2004-05-26 7:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A6974D8E5F98D511BB910002A50A6647615FC676@hdsmsx403.hd.intel.com>
2004-05-26 7:35 ` Len Brown [this message]
2004-05-26 7:37 ` ACPI & 2.4 (Re: [BK PATCH] PCI Express patches for 2.4.27-pre3) Arjan van de Ven
2004-05-26 14:45 ` Jeff Garzik
2004-05-28 12:09 ` Marcelo Tosatti
2004-05-28 14:56 ` Len Brown
2004-05-28 15:38 ` Marcelo Tosatti
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=1085556934.26254.132.camel@dhcppc4 \
--to=len.brown@intel.com \
--cc=arjanv@redhat.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=marcelo.tosatti@cyclades.com \
--cc=willy@debian.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