From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Linus Walleij <linusw@kernel.org>,
Igor Belwon <igor.belwon@mentallysanemainliners.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 0/2] arm64: dts: mediatek: Fix pinfunc headers of two SoCs
Date: Tue, 08 Sep 2026 09:13:33 +0200 [thread overview]
Message-ID: <178885161378.9958.4593363688774333553.b4-ty@b4> (raw)
In-Reply-To: <20260828-mt6878-header-fix-v1-0-b70dc9b2479c@mentallysanemainliners.org>
On Fri, 28 Aug 2026 15:52:45 +0200, Igor Belwon wrote:
> these pinfunc headers were including a header ('mt65xx.h') which is
> outside of the search path (it's in dt-bindings), thus causing a
> build failure (CI couldn't catch this since 6878/6893 don't have DTs
> merged in yet). Use the correct path, following other SoC pinfunc
> headers.
>
> Best regards,
> Igor
>
> [...]
Applied to v7.3-next/dts64, thanks!
[1/2] arm64: dts: mediatek: mt6878-pinfunc: Fix pinctrl header path
commit: 9b9c33336d2c25b6ef8758af3ce3c1802d26ca25
[2/2] arm64: dts: mediatek: mt6893-pinfunc: Fix pinctrl header path
commit: 863d48714194bfcdb917b2ec35531e40df40cb87
Cheers,
Angelo
prev parent reply other threads:[~2026-09-08 7:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 13:52 [PATCH 0/2] arm64: dts: mediatek: Fix pinfunc headers of two SoCs Igor Belwon
2026-08-28 13:52 ` [PATCH 1/2] arm64: dts: mediatek: mt6878-pinfunc: Fix pinctrl header path Igor Belwon
2026-08-28 13:52 ` [PATCH 2/2] arm64: dts: mediatek: mt6893-pinfunc: " Igor Belwon
2026-09-08 7:13 ` AngeloGioacchino Del Regno [this message]
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=178885161378.9958.4593363688774333553.b4-ty@b4 \
--to=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=igor.belwon@mentallysanemainliners.org \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).