dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Peres <martin.peres@free.fr>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Linaro MM SIG <linaro-mm-sig@lists.linaro.org>,
	Daniel Vetter <daniel.vetter@ffwll.ch>,
	dri-devel@lists.freedesktop.org
Subject: Re: CDF discussions at FOSDEM
Date: Sun, 03 Feb 2013 09:03:18 +0100	[thread overview]
Message-ID: <510E19C6.6080200@free.fr> (raw)
In-Reply-To: <1646498.hdCvE5WiAs@avalon>

On 31/01/2013 11:53, Laurent Pinchart wrote:
> On Friday 11 January 2013 21:27:03 Laurent Pinchart wrote:
>> Hi everybody,
>>
>> Would anyone be interested in meeting at the FOSDEM to discuss the Common
>> Display Framework ? There will be a CDF meeting at the ELC at the end of
>> February, the FOSDEM would be a good venue for European developers.
> A quick follow-up on this.
>
> Given the late notice getting a room from the FOSDEM staff wasn't possible.
> There will be two meeting rooms available that can be reserved on-site only.
> They can accomodate aroudn 30 people but there will deliberately be no
> projector. They will be given on a first-come, first-serve basis for one hour
> time slots at most (see https://fosdem.org/2013/news/2013-01-31-bof-
> announce/).
>
> As room availability isn't guaranteed, and as one hour might be a bit short,
> I've secured an off-site but very close
> (http://www.openstreetmap.org/?lat=50.812924&lon=4.384506&zoom=18&layers=M -
> UrLab) room that can accomodate 12 people around a meeting table (more is
> possible, but it might get a bit tight then). I propose having the CDF
> discussion there on Sunday morning from 9am to 11am (please let me know ASAP
> if you can't make it at that time).
>
> Daniel Vetter
> Jani Nikula
> Marcus Lorentzon
> Laurent Pinchart
> Michael (from Pengutronix, not sure about the last name, sorry)
> Philipp Zabel
> Rob Clark
> Robert Schwebel
> Sascha Hauer
> Ville Syrjälä
>
> That's already 10 people. If someone else would like to attend the meeting
> please let me know.
Hi,

I am interested in the CDF. Where and when are you meeting?

Martin

      parent reply	other threads:[~2013-02-03  8:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-11 20:27 CDF discussions at FOSDEM Laurent Pinchart
2013-01-11 22:27 ` Rob Clark
2013-01-17  8:42 ` Jani Nikula
2013-01-17 12:29   ` Daniel Vetter
2013-01-21 12:43     ` Laurent Pinchart
2013-01-29 11:27       ` Laurent Pinchart
2013-01-29 11:47         ` [Linaro-mm-sig] " Luc Verhaegen
2013-01-29 12:11           ` Laurent Pinchart
2013-01-29 14:19             ` Daniel Vetter
2013-01-29 15:50               ` Daniel Vetter
2013-01-29 19:35                 ` Marcus Lorentzon
2013-01-29 21:46                   ` Daniel Vetter
2013-01-29 16:15               ` Ville Syrjälä
2013-01-17 20:20 ` Robert Schwebel
2013-01-31 10:53 ` Laurent Pinchart
2013-01-31 11:02   ` Sascha Hauer
2013-01-31 11:40   ` Lars-Peter Clausen
2013-02-03  8:03   ` Martin Peres [this message]

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=510E19C6.6080200@free.fr \
    --to=martin.peres@free.fr \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linaro-mm-sig@lists.linaro.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