From: Paul Bolle <pebolle@tiscali.nl>
To: Mauro Carvalho Chehab <m.chehab@samsung.com>
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [media] dib0090: remove manual configuration system
Date: Thu, 04 Sep 2014 21:56:45 +0200 [thread overview]
Message-ID: <1409860605.5546.114.camel@x220> (raw)
In-Reply-To: <20140904123613.6fa4d818.m.chehab@samsung.com>
Hi Mauro,
On Thu, 2014-09-04 at 12:36 -0300, Mauro Carvalho Chehab wrote:
> Em Thu, 22 May 2014 14:48:07 +0200
> Paul Bolle <pebolle@tiscali.nl> escreveu:
>
> > dib0900.c has always shipped with its own, manual, configuration
> > system. There a three problems with it.
> >
> > 1) macros that are defined, but not used:
> > CONFIG_SYS_DVBT
> > CONFIG_DIB0090_USE_PWM_AGC
> >
> > 2) checks for macros that are always true:
> > CONFIG_SYS_ISDBT
> > CONFIG_BAND_CBAND
> > CONFIG_BAND_VHF
> > CONFIG_BAND_UHF
> >
> > 3) checks for macros that are never defined and are always false:
> > CONFIG_BAND_SBAND
> > CONFIG_STANDARD_DAB
> > CONFIG_STANDARD_DVBT
> > CONFIG_TUNER_DIB0090_P1B_SUPPORT
> > CONFIG_BAND_LBAND
> >
> > Remove all references to these macros, and, of course, remove the code
> > hidden behind the macros that are never defined too.
>
> IMHO, it is OK to remove the macros that are always true and
> the ones that aren't used.
I see. I hope to send a v2 that does that one of these days.
> However, I don't like the idea of
> removing the other macros. This is a tuner driver that can be used
> on other bands, and some day we might end implementing analog support
> for the Dibcom driver or to add something that will require the code
> there. So, IMHO, better to keep the code there.
But would you consider a patch that at least moves those macros out of
the CONFIG_* namespace (ie, a patch that prefixes those macros with,
say, DIB0090_)?
Paul Bolle
prev parent reply other threads:[~2014-09-04 19:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 12:48 [PATCH] [media] dib0090: remove manual configuration system Paul Bolle
2014-09-04 15:36 ` Mauro Carvalho Chehab
2014-09-04 19:56 ` Paul Bolle [this message]
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=1409860605.5546.114.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=m.chehab@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