linux-pm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@ti.com>
To: markgross@thegnar.org
Cc: "Agarwal, Ramesh" <ramesh.agarwal@intel.com>,
	paulmck@vnet.ibm.com, Praveen Chidambaram <pchidamb@gmail.com>,
	Amit Kucheria <amit.kucheria@linaro.org>,
	John Stultz <john.stultz@linaro.org>,
	linux-pm@lists.linux-foundation.org,
	Antti P Miettinen <amiettinen@nvidia.com>,
	jeen.pihet@G62.linuxfoundation.org
Subject: Re: Plumbers: PM constraints micro-conf RFP
Date: Wed, 09 May 2012 11:35:09 -0700	[thread overview]
Message-ID: <87bolxgq3m.fsf@ti.com> (raw)
In-Reply-To: <20120502143607.GA21640@G62> (mark gross's message of "Wed, 2 May 2012 07:36:10 -0700")

Hi Mark,

mark gross <markgross@thegnar.org> writes:

> This is a Request For Participation in a micro-conference at this years
> Linux plumbers event.  For this micro conference to happen we need to
> reach a certain critical mass WRT participants as measured by submitted
> talks associated to Power Management Constraints.
>
> The To: list is populated with folks that I've had interactions with
> over extending pm-qos or constraint based PM over the past year.
>
> If you are working on problems related to constraining the power /
> performance of devices I am inviting your participation and request you
> submit a proposal for presenting your problem space (preferred) and or
> solution to a group of developers looking for a good solution to push
> upstream.  The talks will be about 20 min long as I want to get into
> some design and implementation discussions after the requirements
> definition is mostly finished.

Thanks for organizing this.

I won't be at Plumbers this year (I'll be on vacation), but will
certainly participate by email as I have an interest in these topics.

I've added Jean Pihet to Cc as he is also working on QoS/constraints
related topics.

Kevin

  parent reply	other threads:[~2012-05-09 18:35 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-02 14:36 Plumbers: PM constraints micro-conf RFP mark gross
2012-05-04 14:16 ` mark gross
2012-05-14  8:43   ` Antti P Miettinen
2012-05-14 13:35     ` mark gross
2012-05-09 18:35 ` Kevin Hilman [this message]
2012-05-09 18:54 ` Kevin Hilman
2012-05-11  7:02 ` Jean Pihet
2012-05-11 14:10   ` mark gross
2012-05-11  7:17 ` Valentin, Eduardo
2012-05-11 14:14   ` mark gross
     [not found]   ` <CAORVsuU3YDGq713jtmPCpJT=3eXqrvx_qU=uPK86XvDdzHSGtg@mail.gmail.com>
     [not found]     ` <4FB13CD3.8000505@ti.com>
     [not found]       ` <CAGF5oy-xduO-BjM1NcNvJG1LV1d-1h78v6mdpq5noRFMsxmjkg@mail.gmail.com>
     [not found]         ` <CAGF5oy9kKPW5BF9FPXXm8-=9O5AM+NhKxjOysJbDiwDF=RvpKw@mail.gmail.com>
2012-05-15  9:40           ` Jean Pihet
2012-05-15 11:00             ` Valentin, Eduardo
2012-05-15 12:58             ` Amit Kucheria
2012-05-16  0:13               ` mark gross
2012-05-17 11:17                 ` Sundar
2012-05-17 11:30                   ` Sundar
2012-05-16  0:09             ` mark gross
2012-05-16  9:45 ` Mansoor, Illyas

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=87bolxgq3m.fsf@ti.com \
    --to=khilman@ti.com \
    --cc=amiettinen@nvidia.com \
    --cc=amit.kucheria@linaro.org \
    --cc=jeen.pihet@G62.linuxfoundation.org \
    --cc=john.stultz@linaro.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=markgross@thegnar.org \
    --cc=paulmck@vnet.ibm.com \
    --cc=pchidamb@gmail.com \
    --cc=ramesh.agarwal@intel.com \
    /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;
as well as URLs for NNTP newsgroup(s).