From: Sebastian Henschel <acpi-1rjuZeEg9oEb1SvskN2V4Q@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: S3 sleep, resume hang - DSDT bad?? Averatec 3270-EE1
Date: Mon, 22 Aug 2005 09:20:21 +0200 [thread overview]
Message-ID: <20050822072021.GA3690@fuchi> (raw)
In-Reply-To: <20050822004140.26440.qmail-HoayJ7sz99KA/QwVtaZbd3CJp6faPEW9@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 936 bytes --]
hello Jeffrey...
* "Jeffrey Y. A. Perry" <jeffperry_2003-/E1597aS9LQAvxtiuMwx3w@public.gmane.org> [2005-08-22 08:55 +0200]:
> Question: Am I right to assume all ACPI4Linux patches
> are incorporated into the kernel releases frequently?
yes...
> I have not applied any of these to my 2.6.12 kernel
> figuring they were already present - which is weird
> since there is actually a patch on the acpi4linux site
> for kernel 2.6.12
but development continues and often patches introduced later are applicable
to older (current) kernels. so the patch against 2.6.12 contains fixes added
after the release of the kernel.
cheers,
Sebastian
--
Oo................................................................
Der naechste Satz ist eine Luege. Der vorhergehende Satz ist wahr.
OpenPGP key ID: 0x7A62F9B4 Geekcode: GCSd-s:a-C++ULB+++W++M+PS+++
................................................................oO
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-08-22 7:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-22 0:41 S3 sleep, resume hang - DSDT bad?? Averatec 3270-EE1 Jeffrey Y. A. Perry
[not found] ` <20050822004140.26440.qmail-HoayJ7sz99KA/QwVtaZbd3CJp6faPEW9@public.gmane.org>
2005-08-22 7:20 ` Sebastian Henschel [this message]
2005-08-22 8:14 ` Erik Slagter
2005-08-22 16:42 ` Oisín Mac Fhearaí
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=20050822072021.GA3690@fuchi \
--to=acpi-1rjuzeeg9oeb1svskn2v4q@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