From: Len Brown <len.brown-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Andi Kleen <ak-l3A5Bk7waGM@public.gmane.org>
Cc: ACPI Developers
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: ACPI @ Ottawa Linux Symposium
Date: 30 Jul 2004 17:33:44 -0400 [thread overview]
Message-ID: <1091223224.9636.27.camel@dhcppc4> (raw)
In-Reply-To: <20040730105954.GB14945-B4tOwbsTzaBolqkO4TVVkw@public.gmane.org>
On Fri, 2004-07-30 at 06:59, Andi Kleen wrote:
> On Thu, Jul 29, 2004 at 11:34:18PM -0400, Brown, Len wrote:
> > FYI,
> >
> > Here are the slides I used to discuss ACPI at OLS last week:
> >
> http://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/doc/ACPI_OLS_2004.sxi
> > (Open Office Format)
> >
> > Here is the paper from the proceedings:
> > http://www.finux.org/Reprints/Reprint-Brown-OLS2004.pdf
>
> Will we see the promised ACPI 3.0 paper eventually too?
When ACPI 3.0 is officially public, I expect to discuss
what it means to Linux here on this list. But I don't think
I'll wrestle with TeX again until next OLS;-)
cheers,
-Len
-------------------------------------------------------
This SF.Net email is sponsored by OSTG. Have you noticed the changes on
Linux.com, ITManagersJournal and NewsForge in the past few weeks? Now,
one more big change to announce. We are now OSTG- Open Source Technology
Group. Come see the changes on the new OSTG site. www.ostg.com
next prev parent reply other threads:[~2004-07-30 21:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-30 3:34 ACPI @ Ottawa Linux Symposium Len Brown
[not found] ` <1091158458.9636.17.camel-D2Zvc0uNKG8@public.gmane.org>
2004-07-30 10:59 ` Andi Kleen
[not found] ` <20040730105954.GB14945-B4tOwbsTzaBolqkO4TVVkw@public.gmane.org>
2004-07-30 21:33 ` Len Brown [this message]
2004-07-31 14:25 ` Hiroshi Miura
[not found] ` <87brhwxni6.wl%miura-yiisDzvROlQdnm+yROfE0A@public.gmane.org>
2004-08-18 4:35 ` Len Brown
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=1091223224.9636.27.camel@dhcppc4 \
--to=len.brown-ral2jqcrhueavxtiumwx3w@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=ak-l3A5Bk7waGM@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