From: Mike Krufky <mkrufky@linuxtv.org>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, linux-dvb-maintainer@linuxtv.org,
Kirk Lapray <kirk.lapray@gmail.com>
Subject: Re: [PATCH 30/37] dvb: add nxt200x frontend module
Date: Thu, 03 Nov 2005 17:56:29 -0500 [thread overview]
Message-ID: <436A959D.8090403@linuxtv.org> (raw)
In-Reply-To: <20051103141125.1463c1bd.akpm@osdl.org>
Andrew Morton wrote:
>Michael Krufky <mkrufky@m1k.net> wrote:
>
>>+
>>+static int nxt200x_writetuner (struct nxt200x_state* state, u8* data)
>>+{
>>+ u8 buf, count = 0;
>>+
>>+ dprintk("%s\n", __FUNCTION__);
>>+
>>+ dprintk("Tuner Bytes: %02X %02X %02X %02X\n", data[0], data[1], data[2], data[3]);
>>+
>>+ /* if pll is a Philips TUV1236D then write directly to tuner */
>>+ if (strcmp(state->config->pll_desc->name, "Philips TUV1236D") == 0) {
>>
>>
>Does DVB have a better way of identifying a device type than strcmp?
>
>
I said the same thing when I first saw this, but I wanted to send the
patches separately, because Kirk wrote the driver, and I corrected the
above issue in a separate patch:
dvb-determine-tuner-write-method-based-on-nxt-chip.patch
Feel free to fold them if you like... I was only trying to indicate separate authorship.
As for the other comments for the rest of the patch series, some of the fixes are trivial. Should I expect that you will correct these? or do you need me to send you more patches?
For now, I think the corrections should wait for Johannes' return,
unless you want to take care of them. I think he comes back JUST after
the end of the merge window... not quite sure.
I have 3 or 4 more patches coming.... I plan to send before the end of
tonight.
Regards,
Michael Krufky
next prev parent reply other threads:[~2005-11-03 22:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-01 8:15 [PATCH 30/37] dvb: add nxt200x frontend module Michael Krufky
2005-11-03 3:11 ` Andrew Morton
2005-11-03 22:56 ` Mike Krufky [this message]
2005-11-04 5:12 ` Andrew Morton
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=436A959D.8090403@linuxtv.org \
--to=mkrufky@linuxtv.org \
--cc=akpm@osdl.org \
--cc=kirk.lapray@gmail.com \
--cc=linux-dvb-maintainer@linuxtv.org \
--cc=linux-kernel@vger.kernel.org \
/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