From: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
To: Patrick Boettcher <patrick.boettcher@posteo.de>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
Jemma Denson <jdenson@gmail.com>
Subject: Re: [PULL] For 4.2 (or even 4.1?) add support for cx24120/Technisat SkyStar S2
Date: Wed, 29 Apr 2015 08:55:26 -0300 [thread overview]
Message-ID: <20150429085526.655677d8@recife.lan> (raw)
In-Reply-To: <20150429133501.38eacfa0@dibcom294.coe.adi.dibcom.com>
Em Wed, 29 Apr 2015 13:35:01 +0200
Patrick Boettcher <patrick.boettcher@posteo.de> escreveu:
> Hi Mauro,
>
> On Mon, 27 Apr 2015 21:40:22 -0300 Mauro Carvalho Chehab
> <mchehab@osg.samsung.com> wrote:
> > > Could we send an additional patch for coding-style or would you prefer
> > > a new patch which has everything inside? This would maintain the
> > > author-attribution of the initial commit.
> >
> > An additional patch is fine.
>
> I fixed the files cx24120.[ch] in a --strict manner.
Thanks
> Do you want me to
> send each of these patches to the list? They are not really
> interesting. But if it might help to review for any obvious mistakes...
Yes, please send to ML.
> I rebased my tree on the media-tree of this morning.
Ok.
> I checked the fe_stat-stuff and I saw that you need to keep the old
> unc, ber and snr functions anyway.
For now, yes.
> I doubt that the cx24120 in its current state reports anything useful
> for statistical uses. Do you think there is an added value adding
> it to a driver which is very simple in this regards?
The thing is that we'll need/want to remove the DVBv3 stats support
from the drivers, and add some code inside the core to keep backward
support.
So, it is more like avoiding the need of rework on it latter.
Now that the driver is fresh, people have the hardware in hands to
check if something doesn't break with the conversion. If this got
postponed, the one doing the conversion may not have the hardware
anymore, with could cause regressions.
> Regarding the wait for channel-lock I think it could be written
> differently using a state and checking in the get_status-function
> whether it is locked for the first time. This will need testing. I
> haven't done it yet.
Well, as this was not merged on 4.2 and we're at -rc1, we have some
time to address the needs. Just try to send me a new pull request
up to -rc5 (or, at most, at beginning of the -rc6 week), or otherwise
it could be postponed to 4.3.
Regards,
Mauro
next prev parent reply other threads:[~2015-04-29 11:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 7:27 [PULL] For 4.2 (or even 4.1?) add support for cx24120/Technisat SkyStar S2 Patrick Boettcher
2015-04-27 20:16 ` Mauro Carvalho Chehab
2015-04-27 21:25 ` Patrick Boettcher
2015-04-28 0:40 ` Mauro Carvalho Chehab
2015-04-29 11:35 ` Patrick Boettcher
2015-04-29 11:55 ` Mauro Carvalho Chehab [this message]
2015-05-14 21:40 ` Mauro Carvalho Chehab
2015-05-15 8:24 ` Patrick Boettcher
2015-05-15 14:24 ` Mauro Carvalho Chehab
2015-05-15 15:18 ` Jemma Denson
2015-05-19 10:57 ` Mauro Carvalho Chehab
2015-05-19 11:25 ` Jemma Denson
2015-05-19 12:09 ` Patrick Boettcher
2015-04-27 21:29 ` Jemma Denson
2015-05-18 10:11 ` [PULL v2] for 4.2: " Patrick Boettcher
2015-05-20 8:05 ` [PULL v3] " Patrick Boettcher
2015-05-20 11:46 ` Jemma Denson
2015-05-20 12:07 ` Mauro Carvalho Chehab
2015-05-20 12:34 ` Patrick Boettcher
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=20150429085526.655677d8@recife.lan \
--to=mchehab@osg.samsung.com \
--cc=jdenson@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=patrick.boettcher@posteo.de \
/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