From: Arnd Bergmann <arnd@arndb.de>
To: Mark Brown <broonie@kernel.org>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
Daniel Mack <daniel@zonque.org>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Robert Jarzmik <robert.jarzmik@free.fr>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
alsa-devel@alsa-project.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] ASoC: pxa: don't select SSP for COMPILE_TESTing
Date: Mon, 7 Aug 2017 13:36:09 +0200 [thread overview]
Message-ID: <CAK8P3a3Zuu7HE4CphQR_wpbGvnupYRSdy3xFZu5UgsuvoOjnLQ@mail.gmail.com> (raw)
In-Reply-To: <20170807112030.zvz3flujilsixdj4@sirena.org.uk>
On Mon, Aug 7, 2017 at 1:20 PM, Mark Brown <broonie@kernel.org> wrote:
> On Mon, Aug 07, 2017 at 12:40:44PM +0200, Arnd Bergmann wrote:
>> When the audio driver selects CONFIG_PXA_SSP to be a loadable
>> module on a platform other than PXA, and the PXA SPI driver
>> is built-in, we get a link error in the SPI driver:
>
> Why doesn't this cause problems on PXA?
On PXA, we 'make' descends into arch/arm/plat-pxa/, where ssp.o
is located. On other ARM platforms (I guess except for MMP),
PLAT_PXA is not set, and on non-ARM architectures, we can't
get there anyway.
Arnd
next prev parent reply other threads:[~2017-08-07 11:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-07 10:40 [PATCH] ASoC: pxa: don't select SSP for COMPILE_TESTing Arnd Bergmann
2017-08-07 11:20 ` Mark Brown
2017-08-07 11:36 ` Arnd Bergmann [this message]
2017-08-07 11:48 ` Mark Brown
2017-08-07 11:58 ` Arnd Bergmann
2017-08-07 12:00 ` Mark Brown
2017-08-07 15:39 ` Arnd Bergmann
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=CAK8P3a3Zuu7HE4CphQR_wpbGvnupYRSdy3xFZu5UgsuvoOjnLQ@mail.gmail.com \
--to=arnd@arndb.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=daniel@zonque.org \
--cc=haojian.zhuang@gmail.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=robert.jarzmik@free.fr \
--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).