linux-kernel - Re: [PATCH] ASoC: pxa: don't select SSP for COMPILE

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAK8P3a0tjwxq+P+Ww+Rxjt9Z4+AsJMgvn3z0bHiPgO+4EWQHZw@mail.gmail.com>
Date:   Mon, 7 Aug 2017 13:58:29 +0200
From:   Arnd Bergmann <arnd@...db.de>
To:     Mark Brown <broonie@...nel.org>
Cc:     Liam Girdwood <lgirdwood@...il.com>,
        Daniel Mack <daniel@...que.org>,
        Haojian Zhuang <haojian.zhuang@...il.com>,
        Robert Jarzmik <robert.jarzmik@...e.fr>,
        Jaroslav Kysela <perex@...ex.cz>,
        Takashi Iwai <tiwai@...e.com>,
        Kuninori Morimoto <kuninori.morimoto.gx@...esas.com>,
        Linux ARM <linux-arm-kernel@...ts.infradead.org>,
        alsa-devel@...a-project.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] ASoC: pxa: don't select SSP for COMPILE_TESTing

On Mon, Aug 7, 2017 at 1:48 PM, Mark Brown <broonie@...nel.org> wrote:
> On Mon, Aug 07, 2017 at 01:36:09PM +0200, Arnd Bergmann wrote:
>> On Mon, Aug 7, 2017 at 1:20 PM, Mark Brown <broonie@...nel.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.
>
> Still missing a few steps of reasoning here...

Sorry, I just realized that you were trying to point out the incomplete
changelog. I must have accidentally closed the editor while working on
it, and then sent it out today after getting no regressions.

I'll resend with a proper changelog.

        Arnd