From: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Niko Ehrenfeuchter
<ehrenfeu-jNDFPZUTrfROceuj71AUlABBhMqQ4zRThC4ANOJQIlc@public.gmane.org>
Cc: ACPI Developers
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: latest acpi-patch on vanilla 2.4.25
Date: 27 Mar 2004 00:28:36 -0500 [thread overview]
Message-ID: <1080365315.16211.74.camel@dhcppc4> (raw)
In-Reply-To: <1080326120.757.227.camel-D2Zvc0uNKG8@public.gmane.org>
I've replaced the 2.4.25 ACPI patches on kernel.org
and the 2.4.25 ACPI trees on bkbits.net
Thanks Niko and others for pointing out that my 2.4.25 ACPI
patch didn't apply cleanly to a fresh kernel.org 2.4.25 tree.
The reason was because I'd apparently leaked some 2.4.26 back
into my 2.5.25 tree and so the patch was effectively based on
too-new a tree.
Let me know if you see any future problems.
thanks,
-Len
ps. I've deleted the 2.4.24 trees (where do you think I got
the new 2.4.25 trees so quickly;-) and will no longer
issue new patches against 2.4.24. So we're down to
2.4.22 (mainly for backporting to old distro releases)
2.4.25 (latest released 2.4)
2.4.26 (in development 2.4)
2.6.4 (latest released 2.6)
2.6.5 (in development 2.6)
-------------------------------------------------------
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 parent reply other threads:[~2004-03-27 5:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20040326131004.GG17527@informatik.uni-freiburg.de>
[not found] ` <1080326120.757.227.camel@dhcppc4>
[not found] ` <1080326120.757.227.camel-D2Zvc0uNKG8@public.gmane.org>
2004-03-27 5:28 ` Len Brown [this message]
[not found] ` <1080365315.16211.74.camel-D2Zvc0uNKG8@public.gmane.org>
2004-03-27 9:18 ` Re: latest acpi-patch on vanilla 2.4.25 Marcel Meckel
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=1080365315.16211.74.camel@dhcppc4 \
--to=len.brown-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=ehrenfeu-jNDFPZUTrfROceuj71AUlABBhMqQ4zRThC4ANOJQIlc@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