All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: LMML <linux-media@vger.kernel.org>
Cc: Steven Toth <stoth@kernellabs.com>
Subject: [PATCH 0/5] Clean-ups to the cx22702 frontend driver
Date: Fri, 10 Sep 2010 15:19:43 +0200	[thread overview]
Message-ID: <20100910151943.103f7423@hyperion.delvare> (raw)

Hi all, hi Steven,

I wrote these 5 patches cleaning up the cx22702 frontend driver a long
time ago, I've been using them for months, so it's probably about time
that I post them for review and, hopefully, upstream inclusion.

Note that I unfortunately do not have access to the CX22702 datasheet,
so my changes are based solely on analysis of the original code, and
testing with a real chip (on my WinFast DTV1000-T.)

[PATCH 1/5] cx22702: Clean up register access functions
[PATCH 2/5] cx22702: Drop useless initializations to 0
[PATCH 3/5] cx22702: Avoid duplicating code in branches
[PATCH 4/5] cx22702: Some things never change
[PATCH 5/5] cx22702: Simplify cx22702_set_tps()

Reviews/comments welcome, of course.

-- 
Jean Delvare

             reply	other threads:[~2010-09-10 13:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-10 13:19 Jean Delvare [this message]
2010-09-10 13:27 ` [PATCH 1/5] cx22702: Clean up register access functions Jean Delvare
2010-09-10 15:13   ` Mauro Carvalho Chehab
2010-09-10 17:03     ` [PATCH 1/5 v2] " Jean Delvare
2010-09-10 13:32 ` [PATCH 2/5] cx22702: Drop useless initializations to 0 Jean Delvare
2010-09-10 13:33 ` [PATCH 3/5] cx22702: Avoid duplicating code in branches Jean Delvare
2010-09-10 13:35 ` [PATCH 4/5] cx22702: Some things never change Jean Delvare
2010-09-10 13:36 ` [PATCH 5/5] cx22702: Simplify cx22702_set_tps() Jean Delvare

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=20100910151943.103f7423@hyperion.delvare \
    --to=khali@linux-fr.org \
    --cc=linux-media@vger.kernel.org \
    --cc=stoth@kernellabs.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.