From: "Sérgio Monteiro Basto" <sergiomb-hHo3WeeoaswVhHzd4jOs4w@public.gmane.org>
To: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Sergey Vlasov <vsu-u2l5PoMzF/Uox3rIn2DAYQ@public.gmane.org>,
acpi-devel
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: RE: Re: ACPI for 2.4
Date: Fri, 26 Mar 2004 15:30:38 +0000 [thread overview]
Message-ID: <1080315038.2479.21.camel@darkstar> (raw)
In-Reply-To: <BF1FE1855350A0479097B3A0D2A80EE002D31BC7-N2PTB0HCzHJF3Yvz3xaN/VDQ4js95KgL@public.gmane.org>
Brown, Len also wrote:
> So I'd like to delete 2.4.22 and 2.4.24 support. When 2.4.26
> closes,I'll delete 2.4.25 too.
well 2.4.24 and 2.4.25 just have been released because one security
issue, so doesn't have much differences in concerning of acpi and (I
think) that can be delete it.
On Thu, 2004-03-25 at 23:28, Brown, Len wrote:
> >ftp://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/patches/
> >release/2.4.26/acpi-20040311-2.4.26.diff.gz
> Yes, on each release I update the ACPI patch for every release that I
> support.
In fact, you overwrite the patch and can't be applied against 2.26.pre6
isn't it ? I think one
acpi-20040311-2.4.26-pre6.diff.gz could be useful for testing, before
been released into kernel tree.
>
> >Patch for 2.4.25 seems to be updated too; however, it gives several
> >rejects when applied to a fresh 2.4.25 tree:
> I just tested it on a clean 2.4.25 tree and got no rejects.
> (I tested the .gz edition)
>
> Either there was a patch in your tree already, or the
> patch got corrupted. Note that kernel.org signs their files
> and you can verify their valididity per instructions in here:
>
> http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/patches/README.ACPI
>
> Cheers,
> -Len
>
--
Sérgio M. B.
-------------------------------------------------------
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\x1470&alloc_id638&op=click
prev parent reply other threads:[~2004-03-26 15:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-25 23:28 [ACPI] Re: ACPI for 2.4 Brown, Len
[not found] ` <BF1FE1855350A0479097B3A0D2A80EE002D31BC7-N2PTB0HCzHJF3Yvz3xaN/VDQ4js95KgL@public.gmane.org>
2004-03-26 15:30 ` Sérgio Monteiro Basto [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=1080315038.2479.21.camel@darkstar \
--to=sergiomb-hho3weeoaswvhhzd4jos4w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=vsu-u2l5PoMzF/Uox3rIn2DAYQ@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