From: Jemma Denson <email@example.com> To: "Mauro Carvalho Chehab" <firstname.lastname@example.org>, "Tycho Lürsen" <email@example.com> Cc: Soeren Moch <firstname.lastname@example.org>, Mauro Carvalho Chehab <email@example.com>, firstname.lastname@example.org Subject: Re: [GIT PULL] SAA716x DVB driver Date: Sat, 2 Dec 2017 18:51:16 +0000 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> Hi Mauro, On 27/11/17 11:24, Mauro Carvalho Chehab wrote: > Em Fri, 24 Nov 2017 17:28:37 +0100 > Tycho Lürsen <email@example.com> escreveu: > >> Hi Mauro, >> >> afaik the last communication about submission of this driver was about >> two months ago. >> >> This driver is important to me, because I own several TurboSight cards >> that are saa716x based. I want to submit a patch that supports my cards. >> Of course I can only do so when you accept this driver in the first place. >> >> Any chance you and Sören agree about how to proceed about this driver >> anytime soon? > If we can reach an agreement about what should be done for the driver > to be promoted from staging some day, I'll merge it. Otherwise, > it can be kept maintained out of tree. This driver has been maintained > OOT for a very long time, and it seems that people were happy with > that, as only at the second half of this year someone is requesting > to merge it. > > So, while I agree that the best is to merge it upstream and > address the issues that made it OOT for a long time, we shouldn't > rush it with the risk of doing more harm than good. > > Thanks, > Mauro Would I be correct in thinking the main blocker to this is the *_ff features used by the S2-6400 card? There's plenty of other cards using this chipset that don't need that part. Would a solution for now to be a driver with the ff components stripped out, and then the ff API work can be done later when / if there's any interest? I guess a problem would be finding a maintainer, I'm happy to put together a stripped down driver just supporting the TBS card I use (I already have one I use with dkms), but I'm not sure I have the time or knowledge of this chipset to be a maintainer. Unfortunately my workplace is phasing out these cards otherwise I'd try and get them to sponsor me rather than do it on my own time! Jemma.
next prev parent reply other threads:[~2017-12-02 18:51 UTC|newest] Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-07-16 18:34 Soeren Moch 2017-07-20 10:49 ` Mauro Carvalho Chehab 2017-07-21 20:44 ` Soeren Moch 2017-08-27 10:30 ` Mauro Carvalho Chehab 2017-09-09 12:52 ` Soeren Moch 2017-09-09 21:20 ` Mauro Carvalho Chehab 2017-09-16 12:54 ` Soeren Moch 2017-09-16 17:49 ` Mauro Carvalho Chehab 2017-09-24 22:17 ` Soeren Moch 2017-11-24 16:28 ` Tycho Lürsen 2017-11-27 11:24 ` Mauro Carvalho Chehab 2017-12-02 18:51 ` Jemma Denson [this message] 2017-12-02 19:49 ` Mauro Carvalho Chehab 2017-12-02 23:59 ` Soeren Moch 2017-12-03 10:57 ` Jemma Denson 2017-12-03 14:11 ` Soeren Moch 2017-12-03 15:04 ` Jemma Denson 2017-12-04 10:07 ` Mauro Carvalho Chehab 2018-01-19 13:59 ` Tycho Lürsen 2018-01-19 15:11 ` Jemma Denson 2018-01-20 15:49 ` Tycho Lürsen 2018-01-25 17:08 ` Jemma Denson 2017-11-28 18:35 ` [GIT PULL] " Mauro Carvalho Chehab 2017-12-02 23:58 ` Soeren Moch 2017-08-23 9:56 ` [GIT PULL RESEND] " Soeren Moch 2018-03-07 15:14 ` Mauro Carvalho Chehab
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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [GIT PULL] SAA716x DVB driver' \ /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
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).