linux-kernel - Re: linux-next: build failure after merge of the mediatek 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <b376b01d-45e0-40dd-be10-81ac154ead7c@sirena.org.uk>
Date: Tue, 18 Jun 2024 12:51:07 +0100
From: Mark Brown <broonie@...nel.org>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@...nel.org>
Cc: Matthias Brugger <matthias.bgg@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Linux Next Mailing List <linux-next@...r.kernel.org>,
	Julien Panis <jpanis@...libre.com>,
	Nicolas Pitre <npitre@...libre.com>
Subject: Re: linux-next: build failure after merge of the mediatek tree

On Tue, Jun 18, 2024 at 12:03:44PM +0200, AngeloGioacchino Del Regno wrote:
> Il 18/06/24 09:49, Julien Panis ha scritto:

> > For some reason, the 2 first commits of the series were not applied
> > with the dts. These commits are needed because they contain some
> > definitions used by the dts.

> I'm not sure how should I proceed here.

> Only the mediatek tree is broken, linux-next is ok... should I pick the
> commits from next or should I remove the dts commits from the mediatek trees?

> First time happening.... :-)

linux-next is only OK because I am merging an old version of the
mediatek tree rather than your current one.  The mediatek tree should be
fixed somehow so that it builds, either mechanism should be fine.

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