From: Charles Keepax <ckeepax@opensource.wolfsonmicro.com>
Cc: Mark Brown <broonie@kernel.org>,
fengguang.wu@intel.com, alsa-devel@alsa-project.org
Subject: Re: [asoc:topic/arizona 1/7] sound/soc/codecs/arizona.h:122:2: note: in expansion of macro 'ARIZONA_MUX_ENUMS'
Date: Wed, 3 Jun 2015 10:09:42 +0100 [thread overview]
Message-ID: <20150603090942.GA3902@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <201506030445.WHoNgi04%fengguang.wu@intel.com>
On Wed, Jun 03, 2015 at 04:51:49AM +0800, kbuild test robot wrote:
> tree: git://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git topic/arizona
> head: 69a6582eeb17dc083b2510f1ca2eaa54ff679b49
> commit: 21a37e39e02d7f57691219fee88cf1d48a74e5bd [1/7] ASoC: arizona: Use auto disable muxes for routing
> config: xtensa-allyesconfig (attached as .config)
> reproduce:
> wget https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross -O ~/bin/make.cross
> chmod +x ~/bin/make.cross
> git checkout 21a37e39e02d7f57691219fee88cf1d48a74e5bd
> # save the attached .config to linux build tree
> make.cross ARCH=xtensa
>
> All error/warnings:
>
> In file included from sound/soc/codecs/wm5102.c:33:0:
> >> include/linux/mfd/arizona/registers.h:646:50: error: expected ')' before numeric constant
> #define ARIZONA_EQ1MIX_INPUT_1_SOURCE 0x880
Seems to just a false positive because the patch adding
SOC_VALUE_ENUM_SINGLE_AUTODISABLE_DECL isn't on the topic/arizona
branch. I assume this will sort itself out as the branches merge
through.
Thanks,
Charles
prev parent reply other threads:[~2015-06-03 9:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 20:51 [asoc:topic/arizona 1/7] sound/soc/codecs/arizona.h:122:2: note: in expansion of macro 'ARIZONA_MUX_ENUMS' kbuild test robot
2015-06-03 9:09 ` Charles Keepax [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=20150603090942.GA3902@opensource.wolfsonmicro.com \
--to=ckeepax@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=fengguang.wu@intel.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