From: Paul Bolle <pebolle@tiscali.nl>
To: Steven Miao <realmz6@gmail.com>
Cc: adi-buildroot-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] blackfin: bf537: fix typo "CONFIG_SND_SOC_ADV80X_MODULE"
Date: Thu, 13 Feb 2014 10:40:59 +0100 [thread overview]
Message-ID: <1392284459.30853.17.camel@x220> (raw)
In-Reply-To: <1362744373.5994.57.camel@x61.thuisdomein>
[Replaced previous maintainer and list with current maintainer and
list.]
On Fri, 2013-03-08 at 13:06 +0100, Paul Bolle wrote:
> There's a (rather subtle) typo in "CONFIG_SND_SOC_ADV80X_MODULE". Fix it
> once and for all by using IS_ENABLED(), which is designed to avoid
> issues like this.
>
> Signed-off-by: Paul Bolle <pebolle@tiscali.nl>
Has someone ever looked at this trivial patch? The typo is still not
fixed in v3.14-rc2.
> 0) Untested! And this needs build- and runtime testing, especially for
> the MODULE case!
>
> 1) There are many lines that might be converted to IS_ENABLED() in this
> file. I'm not sure if and how that should be done.
>
> arch/blackfin/mach-bf537/boards/stamp.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/blackfin/mach-bf537/boards/stamp.c b/arch/blackfin/mach-bf537/boards/stamp.c
> index 95114ed..1872d15 100644
> --- a/arch/blackfin/mach-bf537/boards/stamp.c
> +++ b/arch/blackfin/mach-bf537/boards/stamp.c
> @@ -985,7 +985,7 @@ static struct spi_board_info bfin_spi_board_info[] __initdata = {
> },
> #endif
>
> -#if defined(CONFIG_SND_SOC_ADAV80X) || defined(CONFIG_SND_SOC_ADV80X_MODULE)
> +#if IS_ENABLED(CONFIG_SND_SOC_ADAV80X)
> {
> .modalias = "adav801",
> .max_speed_hz = 3125000, /* max spi clock (SCK) speed in HZ */
Paul Bolle
next prev parent reply other threads:[~2014-02-13 9:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-08 12:06 [PATCH] blackfin: bf537: fix typo "CONFIG_SND_SOC_ADV80X_MODULE" Paul Bolle
2014-02-13 9:40 ` Paul Bolle [this message]
2014-02-26 10:35 ` Steven Miao
2014-02-28 21:13 ` Paul Bolle
2014-03-05 5:54 ` Steven Miao
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=1392284459.30853.17.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=adi-buildroot-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=realmz6@gmail.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.