From: AngeloGioacchino Del Regno <angelogioacchino.delregno@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Matthias Brugger <matthias.bgg@gmail.com>
Cc: "AngeloGioacchino Del Regno"
<angelogioacchino.delregno@collabora.com>,
"Nícolas F. R. A. Prado" <nfraprado@collabora.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux Next Mailing List" <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the mediatek tree
Date: Tue, 15 Apr 2025 09:27:40 +0200 [thread overview]
Message-ID: <7f27c33d-e473-4179-8c1e-a4b1d58fd051@kernel.org> (raw)
In-Reply-To: <20250415163029.4714116b@canb.auug.org.au>
Il 15/04/25 08:30, Stephen Rothwell ha scritto:
> Hi all,
>
> After merging the mediatek tree, today's linux-next build (arm64
> defconfig) failed like this:
>
> arch/arm64/boot/dts/mediatek/mt8188.dtsi:465.15-468.4: ERROR (phandle_references): /sound: Reference to non-existent node or label "accdet"
>
> also defined at arch/arm64/boot/dts/mediatek/mt8390-genio-common.dtsi:1063.8-1094.3
> ERROR: Input tree has errors, aborting (use -f to force output)
>
> Caused by commit
>
> 691712b065d3 ("arm64: dts: mediatek: mt8390-genio-common: Add jack detection with accdet")
>
> I have reverted that commit for today.
>
Sorry about that. I have dropped that commit from the tree.
Thanks,
Angelo
next prev parent reply other threads:[~2025-04-15 7:27 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-15 6:30 linux-next: build failure after merge of the mediatek tree Stephen Rothwell
2025-04-15 7:27 ` AngeloGioacchino Del Regno [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-17 16:44 Mark Brown
2024-06-18 7:49 ` Julien Panis
2024-06-18 10:03 ` AngeloGioacchino Del Regno
2024-06-18 10:20 ` AngeloGioacchino Del Regno
2024-06-18 16:45 ` Julien Panis
2024-06-18 17:42 ` Mark Brown
2024-06-18 18:03 ` Daniel Lezcano
2024-06-19 7:40 ` AngeloGioacchino Del Regno
2024-07-15 17:11 ` Julien Panis
2024-06-18 17:07 ` Kevin Hilman
2024-06-18 11:51 ` Mark Brown
2023-04-03 8:15 Stephen Rothwell
2023-04-03 8:45 ` AngeloGioacchino Del Regno
2023-04-03 9:41 ` AngeloGioacchino Del Regno
2023-04-10 23:25 ` Stephen Rothwell
2023-04-11 16:53 ` Matthias Brugger
2023-04-03 7:52 Stephen Rothwell
2023-04-03 8:43 ` AngeloGioacchino Del Regno
2023-04-03 10:14 ` Krzysztof Kozlowski
2023-04-10 23:24 ` Stephen Rothwell
2023-04-11 16:52 ` Matthias Brugger
2022-08-29 23:42 Stephen Rothwell
2022-08-30 11:10 ` Matthias Brugger
2019-12-15 22:03 Stephen Rothwell
2019-12-16 8:49 ` Matthias Brugger
2019-12-16 9:19 ` Macpaul Lin
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=7f27c33d-e473-4179-8c1e-a4b1d58fd051@kernel.org \
--to=angelogioacchino.delregno@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=nfraprado@collabora.com \
--cc=sfr@canb.auug.org.au \
/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