linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jose Abreu <Jose.Abreu@synopsys.com>
To: Hans Verkuil <hverkuil@xs4all.nl>,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	Angelo Ribeiro <Angelo.Ribeiro@synopsys.com>,
	"Joao Pinto" <Joao.Pinto@synopsys.com>
Cc: Alexandre Courbot <acourbot@chromium.org>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Jacopo Mondi <jacopo+renesas@jmondi.org>,
	Tomasz Figa <tfiga@chromium.org>
Subject: RE: [ANN] Topics for a media summit in Lyon in October
Date: Mon, 16 Sep 2019 08:40:25 +0000	[thread overview]
Message-ID: <BN8PR12MB3266963E3EAA25AC2644942DD38C0@BN8PR12MB3266.namprd12.prod.outlook.com> (raw)
In-Reply-To: <010ba9ce-bac9-6f0c-f128-4f163a7d8ea7@xs4all.nl>

From: Hans Verkuil <hverkuil@xs4all.nl>
Date: Aug/16/2019, 09:06:30 (UTC+00:00)

> Rather then discussing topics for a meeting under the subject 'Lisbon'
> let's start a new thread referring to the right place :-)
> 
> I will try to organize a room, either during the ELCE or (if that doesn't
> work) perhaps on the Thursday afterwards. If that's going to be a problem
> for someone, please let me know.
> 
> I do need to know how many people I can expect. I have the following
> confirmed attendees (and please reply if you are not listed!):

Hi Hans,

It's been a while, hope you are doing well :)

I'm no longer working in media subsystem but my colleagues Angelo and 
Joao would like to attend.

We currently have HDMI and CSI support for our IPs using V4L2 and we 
would like to interact with the community in order to get this 
up-streamed so that we have as many features supported as possible.

Is it possible ?

---
Thanks,
Jose Miguel Abreu

  parent reply	other threads:[~2019-09-16  8:40 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-16  8:06 [ANN] Topics for a media summit in Lyon in October Hans Verkuil
2019-08-16  8:10 ` Hans Verkuil
2019-08-16  8:22   ` Tomasz Figa
2019-08-16  8:31     ` Hans Verkuil
2019-08-16  9:37 ` Mauro Carvalho Chehab
2019-08-19  7:44 ` Hans Verkuil
2019-08-19 14:43   ` Ezequiel Garcia
2019-08-19 15:04     ` Laurent Pinchart
2019-08-19 15:24       ` Eugen.Hristev
2019-08-19 15:51         ` Laurent Pinchart
2019-08-28 10:55 ` Hans Verkuil
2019-08-29  0:56   ` Nicolas Dufresne
2019-08-30  7:53   ` Tomasz Figa
2019-09-03  7:21   ` Hans Verkuil
2019-09-03  7:46     ` Alexandre Courbot
2019-09-03  8:02     ` Tomasz Figa
2019-09-03  9:15     ` Niklas Söderlund
2019-09-03  9:35     ` Laurent Pinchart
2019-09-03 10:03       ` Hans Verkuil
2019-09-12  7:28     ` Michael Tretter
2019-09-13 11:27     ` Hans Verkuil
2019-09-13 12:24       ` Daniel Gomez
2019-09-16  8:40 ` Jose Abreu [this message]
2019-09-16  8:48   ` Hans Verkuil
2019-09-16  9:54     ` Laurent Pinchart
2019-09-16 10:39       ` Angelo Ribeiro
2019-09-16 10:51         ` Laurent Pinchart
2019-09-16 12:51           ` Angelo Ribeiro

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=BN8PR12MB3266963E3EAA25AC2644942DD38C0@BN8PR12MB3266.namprd12.prod.outlook.com \
    --to=jose.abreu@synopsys.com \
    --cc=Angelo.Ribeiro@synopsys.com \
    --cc=Joao.Pinto@synopsys.com \
    --cc=acourbot@chromium.org \
    --cc=hverkuil@xs4all.nl \
    --cc=jacopo+renesas@jmondi.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=tfiga@chromium.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;
as well as URLs for NNTP newsgroup(s).