From: Mark Brown <broonie@kernel.org>
To: Kenneth Westfield <kwestfie@codeaurora.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Jim Davis <jim.epost@gmail.com>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Banajit Goswami <bgoswami@codeaurora.org>,
Patrick Lai <plai@codeaurora.org>,
Kumar Gala <galak@codeaurora.org>,
Bryan Huntsman <bryanh@codeaurora.org>,
ALSA Mailing List <alsa-devel@alsa-project.org>,
MSM Mailing List <linux-arm-msm@vger.kernel.org>,
Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] ASoC: qcom: Remove QCOM dependency from LPASS variants
Date: Wed, 3 Jun 2015 12:06:20 +0100 [thread overview]
Message-ID: <20150603110620.GC14071@sirena.org.uk> (raw)
In-Reply-To: <1433305717-8691-1-git-send-email-kwestfie@codeaurora.org>
[-- Attachment #1: Type: text/plain, Size: 500 bytes --]
On Tue, Jun 02, 2015 at 09:28:37PM -0700, Kenneth Westfield wrote:
> Building with the following config options ...
> CONFIG_COMPILE_TEST=y
> # CONFIG_SND_SOC_QCOM is not set
> CONFIG_SND_SOC_LPASS_IPQ806X=m
> CONFIG_SND_SOC_STORM=m
> ... causes the following build warning:
It's not obvious to me that the above set of options should be allowed
in the first place - surely the machine drivers depend on SND_SOC_QCOM
so the fix should be to add the missing dependency to the machine
drivers?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
prev parent reply other threads:[~2015-06-03 11:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 4:28 [PATCH v2] ASoC: qcom: Remove QCOM dependency from LPASS variants Kenneth Westfield
2015-06-03 11:06 ` Mark Brown [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=20150603110620.GC14071@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bgoswami@codeaurora.org \
--cc=bryanh@codeaurora.org \
--cc=galak@codeaurora.org \
--cc=jim.epost@gmail.com \
--cc=kwestfie@codeaurora.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=plai@codeaurora.org \
--cc=srinivas.kandagatla@linaro.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