From: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Justin Karneges <justin-psi-A4HSxAr4s6pBDgjK7y7TUQ@public.gmane.org>
Cc: ACPI Developers
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: why is a patch still needed?
Date: 24 Mar 2004 00:46:04 -0500 [thread overview]
Message-ID: <1080107163.18509.11.camel@dhcppc4> (raw)
In-Reply-To: <200403231548.43785.justin-psi-A4HSxAr4s6pBDgjK7y7TUQ@public.gmane.org>
On Tue, 2004-03-23 at 18:48, Justin Karneges wrote:
> Thanks for the answer. Apologies for not searching the archives, I've found
> the SF interface doesn't easily allow for that...
try this one:
http://marc.theaimsgroup.com/?l=acpi4linux
> About how far behind is the actual kernel vs the patches here?
Lately it has been under 10 days -- but this varies with the phase of
the release cycle.
> For instance,
> if 2.4.26-pre5 with today's ACPI patch functions properly for me, would it be
> safe to say that I would not need a patch with 2.4.27?
yes, unless something breaks, or you discover that what you think is
working properly isn't really working properly...
-Len
-------------------------------------------------------
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
prev parent reply other threads:[~2004-03-24 5:46 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
[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 [this message]
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=1080107163.18509.11.camel@dhcppc4 \
--to=len.brown-ral2jqcrhueavxtiumwx3w@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.