linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Bolle <pebolle@tiscali.nl>
To: Richard Fitzgerald <rf@opensource.wolfsonmicro.com>
Cc: lee.jones@linaro.org, broonie@kernel.org,
	linus.walleij@linaro.org, gnurou@gmail.com,
	cw00.choi@samsung.com, myungjoo.ham@samsung.com,
	devicetree@vger.kernel.org, alsa-devel@alsa-project.org,
	patches@opensource.wolfsonmicro.com,
	linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
	ckeepax@opensource.wolfsonmicro.com
Subject: Re: [PATCH v3 3/8] mfd: arizona: Add support for WM8998 and WM1814
Date: Sat, 02 May 2015 11:58:51 +0200	[thread overview]
Message-ID: <1430560731.2187.70.camel@x220> (raw)
In-Reply-To: <1430493319-23808-4-git-send-email-rf@opensource.wolfsonmicro.com>

Something I didn't notice when v2 came along.

On Fri, 2015-05-01 at 16:15 +0100, Richard Fitzgerald wrote:
> --- a/drivers/mfd/Kconfig
> +++ b/drivers/mfd/Kconfig

> +config MFD_WM8998
> +	bool "Wolfson Microelectronics WM8998"
> +	depends on MFD_ARIZONA
> +	help
> +	  Support for Wolfson Microelectronics WM8998 low power audio SoC
> +
>  config MFD_WM8400
>  	bool "Wolfson Microelectronics WM8400"
>  	select MFD_CORE

> --- a/drivers/mfd/Makefile
> +++ b/drivers/mfd/Makefile

>  ifneq ($(CONFIG_MFD_WM8997),n)
>  obj-$(CONFIG_MFD_ARIZONA)	+= wm8997-tables.o
>  endif
> +ifneq ($(CONFIG_MFD_WM8998),n)
> +obj-$(CONFIG_MFD_ARIZONA)	+= wm8998-tables.o
> +endif

Playing a bit with the current version of drivers/mfd/Makefile it seems
these
    ifneq ($(CONFIG_MFD_WM[...]),n)

tests will always be true. Because, as far as I know, the Kconfig macros
used in those tests will either be "y" or the empty string, but never
"n". (I don't speak Makefilese fluent enough to know how to add simple
debugging prints for the values of the CONFIG_MFD_WM[...] macros to
actually test this, so correct me if I'm wrong here.)

So I think that, effectively, these wm[...]-tables.o objects will always
be built if CONFIG_MFD_ARIZONA is set. Is that the intention? If not,
perhaps these test should read
    ifeq ($(CONFIG_MFD_WM[...]),y)

Thanks,


Paul Bolle


  reply	other threads:[~2015-05-02  9:59 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-01 15:15 [PATCH v3 0/8] Add support for Wolfson WM8998 and WM1814 codecs Richard Fitzgerald
2015-05-01 15:15 ` [PATCH v3 1/8] mfd: arizona: Split INx_MODE into two fields Richard Fitzgerald
2015-05-13 12:28   ` Lee Jones
2015-05-01 15:15 ` [PATCH v3 2/8] ASoC: arizona: add defines for single-input gain control Richard Fitzgerald
2015-05-01 15:15 ` [PATCH v3 3/8] mfd: arizona: Add support for WM8998 and WM1814 Richard Fitzgerald
2015-05-02  9:58   ` Paul Bolle [this message]
2015-05-04  9:11     ` Richard Fitzgerald
2015-05-04 10:44       ` Paul Bolle
2015-05-07  8:52   ` Lee Jones
2015-05-08  9:11     ` Richard Fitzgerald
2015-05-01 15:15 ` [PATCH v3 4/8] gpio: arizona: add " Richard Fitzgerald
2015-05-01 15:15 ` [PATCH v3 5/8] regulator: " Richard Fitzgerald
2015-05-01 15:15 ` [PATCH v3 6/8] extcon: arizona: Add " Richard Fitzgerald
2015-05-01 15:15 ` [PATCH v3 7/8] ASoC: wm8998: Initial WM8998 codec driver Richard Fitzgerald
2015-05-04 11:39   ` Mark Brown
2015-05-05  9:24     ` Richard Fitzgerald
2015-05-05 10:53       ` Mark Brown
2015-05-05 13:31         ` Richard Fitzgerald
2015-05-05 21:59           ` Mark Brown
2015-05-06  9:24             ` Richard Fitzgerald
2015-05-06 11:48               ` Mark Brown
2015-05-06 12:21                 ` Richard Fitzgerald
2015-05-06 12:34                   ` Mark Brown
2015-05-01 15:15 ` [PATCH v3 8/8] Documentation: Add WM8998/WM1814 device tree bindings Richard Fitzgerald
2015-05-13 12:29   ` Lee Jones

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=1430560731.2187.70.camel@x220 \
    --to=pebolle@tiscali.nl \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=ckeepax@opensource.wolfsonmicro.com \
    --cc=cw00.choi@samsung.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gnurou@gmail.com \
    --cc=lee.jones@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=myungjoo.ham@samsung.com \
    --cc=patches@opensource.wolfsonmicro.com \
    --cc=rf@opensource.wolfsonmicro.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;
as well as URLs for NNTP newsgroup(s).