All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tomasz Figa <tfiga@google.com>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: mchehab+samsung@kernel.org,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: [ANN] Meeting to discuss improvements to support MC-based cameras on generic apps
Date: Thu, 31 May 2018 23:18:38 +0900	[thread overview]
Message-ID: <CAAFQd5AiqUA97=Aksmf9WAoMd0npxpEGJuRh6+vC+Fg4B7CZYQ@mail.gmail.com> (raw)
In-Reply-To: <f2b70cc5-d7b8-1462-969c-a0557c778801@xs4all.nl>

Hi Hans and everyone,

On Thu, May 31, 2018 at 10:58 PM Hans Verkuil <hverkuil@xs4all.nl> wrote:
>
> On 05/31/18 15:22, Mauro Carvalho Chehab wrote:
> > Em Mon, 28 May 2018 10:43:51 -0300
> > Mauro Carvalho Chehab <mchehab+samsung@kernel.org> escreveu:
> >
> >> Em Thu, 17 May 2018 16:07:08 -0300
> >> Mauro Carvalho Chehab <mchehab+samsung@kernel.org> escreveu:
> >>
> >>> Hi all,
> >>>
> >>> The goal of this e-mail is to schedule a meeting in order to discuss
> >>> improvements at the media subsystem in order to support complex camera
> >>> hardware by usual apps.
> >>>
> >>> The main focus here is to allow supporting devices with MC-based
> >>> hardware connected to a camera.
> >>>
> >>> In short, my proposal is to meet with the interested parties on solving
> >>> this issue during the Open Source Summit in Japan, e. g. between
> >>> June, 19-22, in Tokyo.
> >>
> >> Let's schedule the meeting to happen in Tokyo, Japan at June, 19.
> >>
> >> Location yet to be defined, but it will either be together with
> >> OSS Japan or at Google. I'll confirm the address tomorrow.
> >
> > More details about the meeting:
> >
> > Date: June, 19
> > Site: Google
> > Address: 〒106-6126 Tokyo, Minato, Roppongi, 6 Chome−10−1 Roppongi Hills Mori Tower 44F
> >
> > Please confirm who will be attending the meeting.
>
> I plan to attend the meeting via Google Hangouts.

I'll be there as an organizer and participant. We will also have Ricky
from our camera team in Taipei join via Hangouts.

To avoid wasting time on the day of the event, I'd like to have a full
list of participants with emails, so that I can arrange building
access. Replying "Yes, I'll be there" will work for me. ;)

Please let me know if you need any further details or help.

Best regards,
Tomasz

  reply	other threads:[~2018-05-31 14:18 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-17 19:07 [ANN] Meeting to discuss improvements to support MC-based cameras on generic apps Mauro Carvalho Chehab
2018-05-17 21:38 ` Nicolas Dufresne
2018-05-18  8:15   ` Laurent Pinchart
2018-05-18 11:24     ` Mauro Carvalho Chehab
2018-05-18 12:38       ` Laurent Pinchart
2018-05-18 15:15         ` Nicolas Dufresne
2018-05-18 15:41           ` Tomasz Figa
2018-05-19  5:17           ` Laurent Pinchart
2018-05-23 16:19       ` Hans Verkuil
2018-05-23 19:35         ` Laurent Pinchart
2018-05-18 14:22     ` Nicolas Dufresne
2018-05-18 15:19       ` Laurent Pinchart
2018-05-18 12:27 ` Laurent Pinchart
2018-05-18 15:05   ` Mauro Carvalho Chehab
2018-05-18 15:31     ` Laurent Pinchart
2018-05-18 15:37     ` Dave Stevenson
2018-05-18 18:23       ` Nicolas Dufresne
2018-05-19  7:04       ` Laurent Pinchart
2018-05-21 12:16         ` Dave Stevenson
2018-05-21 13:04           ` Laurent Pinchart
2018-05-18 15:37 ` Tomasz Figa
2018-05-25  2:40   ` Zheng, Jian Xu
2018-06-13 14:36   ` Sakari Ailus
2018-06-14  1:06     ` Tomasz Figa
2018-05-28 13:43 ` Mauro Carvalho Chehab
2018-05-28 14:21   ` Niklas Söderlund
2018-05-31 13:22   ` Mauro Carvalho Chehab
2018-05-31 13:46     ` Kieran Bingham
2018-05-31 13:54     ` Laurent Pinchart
2018-05-31 13:58     ` Hans Verkuil
2018-05-31 14:18       ` Tomasz Figa [this message]
2018-05-31 15:15         ` Mauro Carvalho Chehab
2018-05-31 14:19       ` Hans Verkuil
2018-06-01  7:31         ` Javier Martinez Canillas

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='CAAFQd5AiqUA97=Aksmf9WAoMd0npxpEGJuRh6+vC+Fg4B7CZYQ@mail.gmail.com' \
    --to=tfiga@google.com \
    --cc=hverkuil@xs4all.nl \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab+samsung@kernel.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.