From: Hans Verkuil <hverkuil@xs4all.nl>
To: Bryan Wu <cooloney@gmail.com>
Cc: Oliver Schinagl <oliver+list@schinagl.nl>,
Milo Kim <milo.kim@ti.com>, Paul Walmsley <paul@pwsan.com>,
Andy Walls <awalls@md.metrocast.net>,
linux-pwm@vger.kernel.org,
"media-workshop@linuxtv.org" <media-workshop@linuxtv.org>,
Hans Verkuil <hansverk@cisco.com>,
Thierry Reding <thierry.reding@gmail.com>,
Sakari Ailus <sakari.ailus@iki.fi>,
Bryan Wu <bryan.wu@canonical.com>,
Sylwester Nawrocki <sylvester.nawrocki@gmail.com>,
Richard Purdie <rpurdie@rpsys.net>,
Linux LED Subsystem <linux-leds@vger.kernel.org>,
"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: [media-workshop] V2: Agenda for the Edinburgh mini-summit
Date: Tue, 22 Oct 2013 09:50:11 +0000 [thread overview]
Message-ID: <52664A53.7090807@xs4all.nl> (raw)
In-Reply-To: <526577FA.7070602@xs4all.nl>
On 10/21/2013 06:52 PM, Hans Verkuil wrote:
> On 10/21/2013 06:40 PM, Bryan Wu wrote:
>> Is the time and location of media mini-summit fixed? My colleague
>> might show up if it's not conflicted with ARM mini-summit.
>
> It's in the Glamis room on Wednesday. We start at 9 am and the LED topic
> is currently scheduled as the second topic so I expect that it will be
> discussed between 9 and 10 am.
I just posted the final (at least, I really hope it will be the final) version of
the agenda to linux-media and media-workshop. The LED topic moved to a somewhat
later slot and is currently scheduled for 10:50. All these times are tentative so
for this topic you should probably be there at 10:30 to be safe.
Regards,
Hans
prev parent reply other threads:[~2013-10-22 9:50 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-10 9:34 V2: Agenda for the Edinburgh mini-summit Hans Verkuil
[not found] ` <4425595.0oKxXFxdQl@avalon>
[not found] ` <201309241324.25660.hansverk@cisco.com>
[not found] ` <3968462.BF6ckOWXxj@avalon>
2013-09-27 22:07 ` [media-workshop] " Sakari Ailus
2013-09-27 22:30 ` Sakari Ailus
[not found] ` <52405427.6000002@samsung.com>
[not found] ` <52406E5C.2020709@schinagl.nl>
[not found] ` <5240A41A.6050207@gmail.com>
[not found] ` <20130924092053.GB13971@ulmo>
2013-10-07 21:06 ` Sakari Ailus
2013-10-07 22:24 ` [media-workshop] " Laurent Pinchart
2013-10-11 0:02 ` Bryan Wu
2013-10-11 7:38 ` Laurent Pinchart
2013-10-15 18:37 ` Bryan Wu
2013-10-15 18:50 ` Laurent Pinchart
2013-10-15 20:55 ` Bryan Wu
2013-10-15 19:03 ` Sylwester Nawrocki
2013-10-16 1:49 ` Milo Kim
2013-10-16 10:24 ` Sylwester Nawrocki
2013-10-16 17:17 ` Bryan Wu
2013-10-16 23:36 ` Milo Kim
2013-10-16 23:54 ` Bryan Wu
2013-10-16 23:56 ` Bryan Wu
2013-10-17 0:12 ` Andy Walls
2013-10-19 0:17 ` Bryan Wu
[not found] ` <CAPybu_2KRF_VHkjCEV8d7YOaZo27QJ=TxGTsUOeWO5X_tp8Ozw@mail.gmail.com>
2013-10-21 18:40 ` Bryan Wu
2013-10-21 18:52 ` Hans Verkuil
[not found] ` <CAPybu_1NZ-CfNkMt_stev5L9oL1MqSAhV03jQW7QoF=q4c2JzQ@mail.gmail.com>
2013-10-21 19:39 ` Hans Verkuil
2013-10-22 9:50 ` Hans Verkuil [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=52664A53.7090807@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=awalls@md.metrocast.net \
--cc=bryan.wu@canonical.com \
--cc=cooloney@gmail.com \
--cc=hansverk@cisco.com \
--cc=linux-leds@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=media-workshop@linuxtv.org \
--cc=milo.kim@ti.com \
--cc=oliver+list@schinagl.nl \
--cc=paul@pwsan.com \
--cc=rpurdie@rpsys.net \
--cc=sakari.ailus@iki.fi \
--cc=sylvester.nawrocki@gmail.com \
--cc=thierry.reding@gmail.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