From: Mark Brown <broonie@kernel.org>
To: Niklas Cassel <niklas.cassel@linaro.org>
Cc: andy.gross@linaro.org, Patrick Lai <plai@codeaurora.org>,
Banajit Goswami <bgoswami@codeaurora.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
linux-arm-msm@vger.kernel.org, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 5/7] ASoC: qdsp6: Add depends on OF
Date: Mon, 18 Jun 2018 12:06:42 +0100 [thread overview]
Message-ID: <20180618110642.GA6928@sirena.org.uk> (raw)
In-Reply-To: <20180614111138.8923-6-niklas.cassel@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 261 bytes --]
On Thu, Jun 14, 2018 at 01:11:36PM +0200, Niklas Cassel wrote:
> of_platform_device_destroy is only defined when building
> with CONFIG_OF=y. Add a depends on OF.
Is it sensible that of_platform_device_destroy() is only defined when
building with CONFIG_OF=y?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-06-18 11:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-14 11:11 [PATCH v2 0/7] soc: qcom: Allow COMPILE_TEST of all drivers Niklas Cassel
2018-06-14 11:11 ` [PATCH v2 1/7] rpmsg: smd: Add missing include of sizes.h Niklas Cassel
2018-06-14 11:11 ` [PATCH v2 2/7] soc: qcom: smem: " Niklas Cassel
2018-06-14 11:11 ` [PATCH v2 3/7] soc: qcom: smp2p: Add select IRQ_DOMAIN Niklas Cassel
2018-06-14 11:11 ` [PATCH v2 4/7] soc: qcom: smsm: " Niklas Cassel
2018-06-14 11:11 ` [PATCH v2 5/7] ASoC: qdsp6: Add depends on OF Niklas Cassel
2018-06-18 11:06 ` Mark Brown [this message]
2018-06-18 12:39 ` Niklas Cassel
2018-06-18 14:48 ` Rob Herring
2018-06-18 20:08 ` Niklas Cassel
2018-06-18 20:53 ` Rob Herring
2018-06-19 9:36 ` Srinivas Kandagatla
2018-06-14 11:11 ` [PATCH v2 6/7] soc: qcom: Remove bogus " Niklas Cassel
2018-06-14 11:11 ` [PATCH v2 7/7] soc: qcom: Allow COMPILE_TEST of all drivers Niklas Cassel
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=20180618110642.GA6928@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=andy.gross@linaro.org \
--cc=bgoswami@codeaurora.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=niklas.cassel@linaro.org \
--cc=perex@perex.cz \
--cc=plai@codeaurora.org \
--cc=tiwai@suse.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).