linux-kernel - Re: linux-next: build failure after merge of the sound-asoc tree

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] [day] [month] [year] [list]

Message-ID: <20200427111916.GA4272@sirena.org.uk>
Date:   Mon, 27 Apr 2020 12:19:16 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Michael Ellerman <mpe@...erman.id.au>
Cc:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Liam Girdwood <lgirdwood@...il.com>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        YueHaibing <yuehaibing@...wei.com>,
        Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>
Subject: Re: linux-next: build failure after merge of the sound-asoc tree

On Sun, Apr 26, 2020 at 09:30:57AM +1000, Michael Ellerman wrote:
> Mark Brown <broonie@...nel.org> writes:

> > I am doing that but that still doesn't mean that the architectures
> > shouldn't be updated - to me this is like the architectures that don't
> > implement standard APIs, we should fix the issues they bring up but it'd
> > be a lot less noisy to sidestep the issue.

> I don't think it's really like architectures that don't implement
> standard APIs.

> It's more like architectures not building code they don't need, AFAICS
> none of the drivers under there can ever be used on powerpc.

That's generally the reason people give for not doing the standard APIs
- there were a few architectures that didn't have DMA hardware so didn't
even have stubs for the DMA API for example, until those were added you
used to end up with build testing tripping over them constantly.  It's
much rarer to have an incompatible implementation of the same thing.

> Similarly we don't build drivers/acpi.

ACPI has stubs so doesn't cause issues here.

> But if there's a good reason that we should be building it then I'm
> happy to take a patch adding it.

The build coverage seems useful.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)