From: Matthew Wilcox <willy-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>
To: Justin Karneges <justin-psi-A4HSxAr4s6pBDgjK7y7TUQ@public.gmane.org>
Cc: Matthew Wilcox <willy-8fiUuRrzOP0dnm+yROfE0A@public.gmane.org>,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: why is a patch still needed?
Date: Tue, 23 Mar 2004 19:39:49 +0000 [thread overview]
Message-ID: <20040323193949.GZ25059@parcelfarce.linux.theplanet.co.uk> (raw)
In-Reply-To: <200403231134.13910.justin-psi-A4HSxAr4s6pBDgjK7y7TUQ@public.gmane.org>
On Tue, Mar 23, 2004 at 11:34:13AM -0800, Justin Karneges wrote:
> On Tuesday 23 March 2004 4:33 am, Matthew Wilcox wrote:
> > ACPI is constantly being developed. It's a large and complex
> > specification. As a result BIOS writers get things wrong, and the
> > ACPICA has missing bits and bugs. So there will probably always be an
> > ACPI patch, just like there's always a netdrivers patch and always a
> > scsi patch.
>
> Are these patches eventually integrated into the kernel? And their
> availability on a separate website is there for people who don't want to wait
> for the next kernel release? In other words, if I wait until kernel 2.6.5,
> do I get the ACPI stuff offered on your website today?
As you'd know if you looked in the archives of this mailing list,
the ACPI tree is merged into Linus' tree on a regular basis.
--
"Next the statesmen will invent cheap lies, putting the blame upon
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince
himself that the war is just, and will thank God for the better sleep
he enjoys after this process of grotesque self-deception." -- Mark Twain
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
next prev parent reply other threads:[~2004-03-23 19:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-23 8:44 why is a patch still needed? Justin Karneges
[not found] ` <200403230044.49403.justin-psi-A4HSxAr4s6pBDgjK7y7TUQ@public.gmane.org>
2004-03-23 12:33 ` Matthew Wilcox
[not found] ` <20040323123344.GS25059-+pPCBgu9SkPzIGdyhVEDUDl5KyyQGfY2kSSpQ9I8OhVaa/9Udqfwiw@public.gmane.org>
2004-03-23 19:34 ` Justin Karneges
[not found] ` <200403231134.13910.justin-psi-A4HSxAr4s6pBDgjK7y7TUQ@public.gmane.org>
2004-03-23 19:39 ` Matthew Wilcox [this message]
[not found] ` <20040323193949.GZ25059-+pPCBgu9SkPzIGdyhVEDUDl5KyyQGfY2kSSpQ9I8OhVaa/9Udqfwiw@public.gmane.org>
2004-03-23 23:48 ` Justin Karneges
[not found] ` <200403231548.43785.justin-psi-A4HSxAr4s6pBDgjK7y7TUQ@public.gmane.org>
2004-03-24 5:46 ` Len Brown
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=20040323193949.GZ25059@parcelfarce.linux.theplanet.co.uk \
--to=willy-8fiuurrzop0dnm+yrofe0a@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=justin-psi-A4HSxAr4s6pBDgjK7y7TUQ@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