From: Andreas Regel <andreas.regel@gmx.de>
To: Luis Alves <ljalvs@gmail.com>, linux-media <linux-media@vger.kernel.org>
Cc: updatelee@gmail.com, abraham.manu@gmail.com, crazycat69@narod.ru,
Mauro Carvalho Chehab <m.chehab@samsung.com>,
Antti Palosaari <crope@iki.fi>
Subject: Re: Upstreaming SAA716x driver to the media_tree
Date: Tue, 07 Jan 2014 17:12:11 +0100 [thread overview]
Message-ID: <52CC275B.5030907@gmx.de> (raw)
In-Reply-To: <CAGj5WxCajB0ORTQ_rz9wv+ec9bXE1A9tM_MGP3qb0eyaxhC5ew@mail.gmail.com>
Hi Luis,
Am 07.01.2014 12:58, schrieb Luis Alves:
> Hi,
>
> I'm finishing a new frontend driver for one of my dvb cards, but the
> pcie bridge uses the (cursed) saa716x.
> As far as I know the progress to upstream Manu's driver to the
> media_tree has stalled.
>
> In CC I've placed some of the people that I found working on it
> lately, supporting a few dvb cards.
>
> It would be good if we could gather everything in one place and send a
> few patchs to get this upstreamed for once...
>
> Manu, do you see any inconvenience in sending your driver to the
> linux_media tree?
> I'm available to place some effort on this task.
which repository of the saa761x is your work based on?
Regards,
Andreas
next prev parent reply other threads:[~2014-01-07 16:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-07 11:58 Upstreaming SAA716x driver to the media_tree Luis Alves
2014-01-07 13:10 ` Manu Abraham
2014-01-07 15:59 ` Luis Alves
[not found] ` <CALzAhNW=uCLsu4sdrGyycxRoOdaRTFNM8yVj=Y+ahSZrWqrABg@mail.gmail.com>
2014-01-14 3:35 ` Manu Abraham
2014-01-21 21:59 ` Steven Toth
2014-01-22 15:26 ` Manu Abraham
2014-02-11 13:44 ` Luis Alves
2014-02-11 19:47 ` Manu Abraham
2014-02-25 22:27 ` Luis Alves
2014-02-26 17:27 ` Manu Abraham
2014-01-07 16:12 ` Andreas Regel [this message]
2014-01-07 16:33 ` Luis Alves
2014-01-07 17:31 ` Konstantin Dimitrov
2014-01-07 20:23 ` Luis Alves
2014-01-08 21:21 ` Konstantin Dimitrov
2014-01-07 23:42 ` CrazyCat
2014-01-08 20:52 ` Konstantin Dimitrov
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=52CC275B.5030907@gmx.de \
--to=andreas.regel@gmx.de \
--cc=abraham.manu@gmail.com \
--cc=crazycat69@narod.ru \
--cc=crope@iki.fi \
--cc=linux-media@vger.kernel.org \
--cc=ljalvs@gmail.com \
--cc=m.chehab@samsung.com \
--cc=updatelee@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 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.