From: wwp <subscript-GANU6spQydw@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: ACPI status in 2.4 tree
Date: Wed, 19 Nov 2003 15:43:24 +0100 [thread overview]
Message-ID: <20031119154324.6bbc067f.subscript@free.fr> (raw)
In-Reply-To: <20031119142918.GF32464-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
Hi Ducrot Bruno,
On Wed, 19 Nov 2003 15:29:18 +0100 Ducrot Bruno <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org> wrote:
> On Wed, Nov 19, 2003 at 01:52:03PM +0100, wwp wrote:
> > Hi ACPI guyz,
> >
> >
> > are 2.4's release candidates sync'ed w/ ACPI?
> > IOW, if I get 2.4.23-rc2, will it include the latest ACPI code from acpi.sf.net
> > (except the test patches) or will I have to get'n'apply a patch?
> >
>
> Why not just looking in the log? at ?
> From ftp.kernel.org:/pub/linux/kernel/v2.4/testing/patch-2.4.23.log
That's exactly what I did (and I use to), but I did't know if the [ACPI]
prefix implies that it's a sync' between acpi.sf.net project and Linux kernel
or a simple ACPI stuff merged to Linux. That's why I was asking :-\.
Regards,
--
wwp
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
next prev parent reply other threads:[~2003-11-19 14:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-19 12:52 ACPI status in 2.4 tree wwp
[not found] ` <20031119135203.373043b0.subscript-GANU6spQydw@public.gmane.org>
2003-11-19 14:29 ` Ducrot Bruno
[not found] ` <20031119142918.GF32464-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2003-11-19 14:43 ` wwp [this message]
2003-11-19 15:12 ` Luca Capello
[not found] ` <3FBB8840.1090306-wlebWZzHoyE@public.gmane.org>
2003-11-19 15:46 ` wwp
[not found] ` <20031119164638.628287da.subscript-GANU6spQydw@public.gmane.org>
2003-11-19 17:05 ` Matthew Wilcox
[not found] ` <20031119170515.GY30485-+pPCBgu9SkPzIGdyhVEDUDl5KyyQGfY2kSSpQ9I8OhVaa/9Udqfwiw@public.gmane.org>
2003-11-19 18:31 ` wwp
[not found] ` <20031119193105.02361704.subscript-GANU6spQydw@public.gmane.org>
2003-11-20 15:18 ` Ducrot Bruno
[not found] ` <20031120151828.GJ32464-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2003-11-20 15:43 ` wwp
2003-11-19 17:24 ` Micha Feigin
-- strict thread matches above, loose matches on Subject: below --
2003-11-19 18:09 Brown, Len
[not found] ` <BF1FE1855350A0479097B3A0D2A80EE00147D1FD-N2PTB0HCzHJF3Yvz3xaN/VDQ4js95KgL@public.gmane.org>
2003-11-19 19:50 ` wwp
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=20031119154324.6bbc067f.subscript@free.fr \
--to=subscript-ganu6spqydw@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@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