public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: mark gross <markgross@thegnar.org>
To: Antti P Miettinen <amiettinen@nvidia.com>
Cc: Kevin Hilman <khilman@ti.com>,
	"Agarwal, Ramesh" <ramesh.agarwal@intel.com>,
	markgross@thegnar.org, paulmck@vnet.ibm.com,
	pdeschrijver@nvidia.com, Praveen Chidambaram <pchidamb@gmail.com>,
	Amit Kucheria <amit.kucheria@linaro.org>,
	John Stultz <john.stultz@linaro.org>,
	linux-pm@lists.linux-foundation.org,
	jeen.pihet@G62.linuxfoundation.org
Subject: Re: Plumbers: PM constraints micro-conf RFP
Date: Mon, 14 May 2012 06:35:18 -0700	[thread overview]
Message-ID: <20120514133518.GA11747@G62> (raw)
In-Reply-To: <87vcjz6tli.fsf@amiettinen-lnx.nvidia.com>

On Mon, May 14, 2012 at 11:43:21AM +0300, Antti P Miettinen wrote:
> mark gross <markgross@thegnar.org> writes:
> > I forgot to make clear a few things specific to the Plumbers conference.
> > 1) they need proposals by mid may
> > 2) if you want financial assistance to be part of this micro-conf you
> > need to ask the conference committee and I think I need to recommend you
> > as an important participant.  --- Paul, can you clarify this?
> >
> > If we don't get a critical mass as determined by the conference
> > committee we can try again / do more stuff over email.  BTW we should be
> > doing more of anyway.
> >
> > --mark
> 
> Not being familiar with LPC format - does LPC expect just a presentation
> or should there be also a "paper"? I just registered a blueprint at
> 
> 	https://blueprints.launchpad.net/lpc/+spec/lpc2012-cf-tegra
> 
> Is the format OK for a proposal?

That looks good to me.  But, Paul would be right person to confirm.
Please be sure to give equal time to the problem statement as well as
your implementation in the presentation. Depending on time constraints,
TBD, you may need to trim back on the talk or not.

The time per talk depends on how much participation we get.

--mark

  reply	other threads:[~2012-05-14 13: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 [this message]
2012-05-09 18:35 ` Kevin Hilman
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=20120514133518.GA11747@G62 \
    --to=markgross@thegnar.org \
    --cc=amiettinen@nvidia.com \
    --cc=amit.kucheria@linaro.org \
    --cc=jeen.pihet@G62.linuxfoundation.org \
    --cc=john.stultz@linaro.org \
    --cc=khilman@ti.com \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=paulmck@vnet.ibm.com \
    --cc=pchidamb@gmail.com \
    --cc=pdeschrijver@nvidia.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