public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Patrick Boettcher <patrick.boettcher@posteo.de>
To: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
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 13:35:01 +0200	[thread overview]
Message-ID: <20150429133501.38eacfa0@dibcom294.coe.adi.dibcom.com> (raw)
In-Reply-To: <20150427214022.1ff9f61f@recife.lan>

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. 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...

I rebased my tree on the media-tree of this morning.

I checked the fe_stat-stuff and I saw that you need to keep the old
unc, ber and snr functions anyway.

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?

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.

regards,
--
Patrick.


  reply	other threads:[~2015-04-29 11:35 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 [this message]
2015-04-29 11:55         ` Mauro Carvalho Chehab
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=20150429133501.38eacfa0@dibcom294.coe.adi.dibcom.com \
    --to=patrick.boettcher@posteo.de \
    --cc=jdenson@gmail.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@osg.samsung.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox