All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Hilman <khilman@kernel.org>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@kernel.org>,
	Mark Brown <broonie@kernel.org>,
	Matthias Brugger <matthias.bgg@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>,
	Julien Panis <jpanis@baylibre.com>,
	Nicolas Pitre <npitre@baylibre.com>
Subject: Re: linux-next: build failure after merge of the mediatek tree
Date: Tue, 18 Jun 2024 10:07:28 -0700	[thread overview]
Message-ID: <7hcyoekwmn.fsf@baylibre.com> (raw)
In-Reply-To: <be5a8b12-b042-48cc-9508-759a2a285a8b@kernel.org>

AngeloGioacchino Del Regno <angelogioacchino.delregno@kernel.org>
writes:

> Il 18/06/24 12:03, AngeloGioacchino Del Regno ha scritto:
>> Il 18/06/24 09:49, Julien Panis ha scritto:
>>> On 6/17/24 18:44, Mark Brown wrote:
>>>> Hi all,
>>>>
>>>> After merging the mediatek tree, today's linux-next build (arm64
>>>> defconfig) failed like this:
>>>>
>>>> /tmp/next/build/arch/arm64/boot/dts/rockchip/rk3568-wolfvision-pf5-display.dtsi:113.6-121.3: Warning (graph_port): /fragment@4/__overlay__: graph port node name should be 'port'
>>>> Error: /tmp/next/build/arch/arm64/boot/dts/mediatek/mt8186.dtsi:2399.29-30 
>>>> syntax error
>>>> FATAL ERROR: Unable to parse input tree
>>>> make[4]: *** [/tmp/next/build/scripts/Makefile.lib:431: 
>>>> arch/arm64/boot/dts/mediatek/mt8186-corsola-magneton-sku393216.dtb] Error 1
>>>>
>>>> Caused by commit
>>>>
>>>>    d7c1bde38bf37a5 ("arm64: dts: mediatek: mt8186: add default thermal zones")
>>>>
>>>> I have used the last version of the mediatek tree from 20240613 instead.
>>>
>>> Hello Mark,
>>>
>>> Here is the explanation:
>>> https://lore.kernel.org/all/71d53ff6-fdae-440d-b60d-3ae6f0c881d9@baylibre.com/
>>> https://lore.kernel.org/all/6d9e0f19-9851-4f23-a8b8-6acc82ae7a3d@baylibre.com/
>>>
>>> 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.
>>>
>>> Julien
>> 
>> I'm not sure how should I proceed here.
>> 
>
> Reiterating, I'm sure how should I proceed.

You applied the dts patches but not the bindings, resulting in something
that doesn't build because of changes to #defines in the bindings.

Both of the bindings patches have already been acked by a DT maintainer
(Connor), so you should just apply the bindings along with the DT patches.

> I'm removing those patches from mediatek for-next until further notice.

Rather than remove the DT patches, you should just apply the bindings
patches.

Kevin

  parent reply	other threads:[~2024-06-18 17:07 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-17 16:44 linux-next: build failure after merge of the mediatek tree 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 [this message]
2024-06-18 11:51     ` Mark Brown
  -- strict thread matches above, loose matches on Subject: below --
2025-04-15  6:30 Stephen Rothwell
2025-04-15  7:27 ` AngeloGioacchino Del Regno
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=7hcyoekwmn.fsf@baylibre.com \
    --to=khilman@kernel.org \
    --cc=angelogioacchino.delregno@kernel.org \
    --cc=broonie@kernel.org \
    --cc=jpanis@baylibre.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=matthias.bgg@gmail.com \
    --cc=npitre@baylibre.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.