From: Paul Mundt <lethal@linux-sh.org>
To: Len Brown <lenb@kernel.org>
Cc: Linux Power Management List <linux-pm@lists.osdl.org>,
linux-acpi@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [linux-pm] Montreal Linux Power Management Mini-Summit -- July 13, 2009
Date: Thu, 28 May 2009 18:32:50 +0900 [thread overview]
Message-ID: <20090528093250.GB27545@linux-sh.org> (raw)
In-Reply-To: <alpine.LFD.2.00.0905211430220.4390@localhost.localdomain>
On Thu, May 21, 2009 at 03:12:53PM -0400, Len Brown wrote:
> We will hold a Linux Power Management Mini-Summit in Montreal
> on Monday, July 13, 2009 -- concurrent with day-1 of the
> tutorials at the at the Linux Symposium.
>
> http://www.linuxsymposium.org/2009/schedule.php
>
> This is an opportunity for members of the Linux Power Management
> development community to meet face-to-face to discuss the future.
>
> Suggestions for agenda topics should be sent to:
> linux-pm@lists.linux-foundation.org
>
> The final agenda will be formed by consensus of the attendees.
>
> As in previous years, attendance is open to those
> registered as Linux Symposium attendees.
>
> However, we will try to cap attendance at 20 to support the single
> discussion. So requests to attend should be sent to: lenb@kernel.org
> cc: linux-pm@lists.linux-foundation.org -- please summarize
> what you bring to the meeting, and what you'd like to discuss.
>
I'd also like to attend. Areas of interest this year are run-time PM,
moving to clock framework notifiers, and tying in pm qos for transition
latencies.
next prev parent reply other threads:[~2009-05-28 9:33 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-21 19:12 Montreal Linux Power Management Mini-Summit -- July 13, 2009 Len Brown
2009-05-24 11:35 ` Rafael J. Wysocki
2009-05-24 11:35 ` Rafael J. Wysocki
2009-05-28 5:36 ` Magnus Damm
2009-05-28 9:32 ` Paul Mundt [this message]
2009-07-12 16:56 ` Len Brown
2009-07-30 22:04 ` Montreal Linux Power Management Mini-Summit, July 13, 2009 - Meeting Notes Len Brown
2009-09-01 22:22 ` Linus Walleij
2009-09-01 22:22 ` Linus Walleij
2009-09-01 22:22 ` Linus Walleij
2009-09-02 2:25 ` Bill Gatliff
2009-09-02 2:25 ` Bill Gatliff
2009-09-02 8:36 ` Francesco VIRLINZI
2009-09-02 8:36 ` [linux-pm] " Francesco VIRLINZI
2009-09-02 21:44 ` Linus Walleij
2009-09-02 21:44 ` Linus Walleij
2009-09-02 21:58 ` Russell King - ARM Linux
2009-09-02 21:58 ` Russell King - ARM Linux
2009-09-03 14:50 ` Francesco VIRLINZI
2009-09-03 14:50 ` Francesco VIRLINZI
2009-09-03 17:12 ` Russell King - ARM Linux
2009-09-03 17:12 ` [linux-pm] " Russell King - ARM Linux
2009-09-03 20:15 ` Linus Walleij
2009-09-03 20:15 ` Linus Walleij
2009-09-03 21:28 ` Woodruff, Richard
2009-09-03 21:28 ` [linux-pm] " Woodruff, Richard
2009-09-04 7:34 ` Francesco VIRLINZI
2009-09-04 7:34 ` [linux-pm] " Francesco VIRLINZI
2009-10-18 17:28 ` Linus Walleij
2009-10-18 17:28 ` Linus Walleij
2009-10-19 7:44 ` Francesco VIRLINZI
2009-10-19 7:44 ` Francesco VIRLINZI
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=20090528093250.GB27545@linux-sh.org \
--to=lethal@linux-sh.org \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.