From: Len Brown <lenb@kernel.org>
To: Linux Power Management List <linux-pm@lists.osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org
Subject: Linux Power Management Mini-Summit -- Ottawa -- July 22, 2008
Date: Thu, 17 Jul 2008 17:27:32 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0807171724070.16742@localhost.localdomain> (raw)
We'll be in The Rideau Suite in Les-Suites
Tuesday July 22nd 8:30-18:30.
Thanks to HP for sponsoring
lunch at 12:30 as well as snacks at 10:00 and 15:30.
We'll wing it for dinner.
On linux-pm (sorry, on sabbatical I've been
bad about keeping up on email) I've seen
intent to attend from:
Len Brown <len.brown@intel.com>
Alan Stern <stern@rowland.harvard.edu>
Dipankar Sarma <dipankar@in.ibm.com>
Rafael J. Wysocki <rjw@sisk.pl>
"Woodruff, Richard" <r-woodruff2@ti.com>
Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>
Matt Domsch <Matt_Domsch@dell.com>
Jarod Wilson <jwilson@redhat.com>
Tim Bird <tim.bird@am.sony.com>
Paul Mundt <lethal@linux-sh.org>
Hiroyuki Machida <Hiroyuki.Mach@gmail.com>
Several send their regrets:
Dave Jones
Pavel Machek
Arjan van de Ven
If you plan to attend, please let me know,
because the folks at OLS want to know,
to simplify OLS registration.
thanks,
-Len
---
We are again planning a Linux Power Management Mini-Summit preceding OLS.
This year we are looking at a single day, Tuesday July 22nd.
OLS is generously supporting mini-summits by providing the room
and projector: http://www.linuxsymposium.org/2008/minisummits.php
If you are interested in sponsoring the food or
other forum needs, please let me know.
Minutes from last year's meeting can be found here:
http://lwn.net/Articles/249019
If you have feedback on last year's meeting that
we can use to improve this year's, please speak up.
The feedback at the time was pretty positive, so I'm thinking
that unless there are new best-known-methods, that we'll stick
with the same open method of self-nominated attendees,
an agenda provoked by discussion on linux-pm ahead of time
and consensus of attendees, and a forum small enough to support
a single focused discussion.
(yes, one improvement I plan on this year is to publish minutes immediately.
OLS was sort of hectic for me last year and that caused a delay)
thanks,
-Len
next reply other threads:[~2008-07-17 21:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-17 21:27 Len Brown [this message]
2008-07-18 0:00 ` [linux-pm] Linux Power Management Mini-Summit -- Ottawa -- July 22, 2008 Nigel Cunningham
2008-07-18 3:00 ` Vaidyanathan Srinivasan
2008-07-18 9:50 ` Gautham R Shenoy
2008-08-09 11:09 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2008-07-18 7:52 Kai Svahn
2008-06-25 18:44 Len Brown
2008-06-25 19:42 ` Dipankar Sarma
2008-06-26 22:52 ` Len Brown
2008-07-01 3:23 ` Paul Mundt
2008-07-11 7:08 ` Hiroyuki Machida
2008-07-01 13:43 ` Vaidyanathan Srinivasan
2008-06-25 20:15 ` Rafael J. Wysocki
2008-06-26 22:45 ` Len Brown
2008-07-01 20:39 ` Matt Domsch
2008-06-26 12:37 ` Nigel Cunningham
2008-07-08 14:21 ` Pavel Machek
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=alpine.LFD.1.10.0807171724070.16742@localhost.localdomain \
--to=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.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