From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: "Rafał Miłecki" <zajec5@gmail.com>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
"Rafał Miłecki" <rafal@milecki.pl>
Subject: Re: [PATCH 3/4] arm64: dts: mediatek: mt7622: fix ethernet controller "compatible"
Date: Mon, 4 Mar 2024 11:12:59 +0100 [thread overview]
Message-ID: <fcba424c-eb0b-4a43-b657-eeef811809c4@collabora.com> (raw)
In-Reply-To: <20240301113506.22944-4-zajec5@gmail.com>
Il 01/03/24 12:35, Rafał Miłecki ha scritto:
> From: Rafał Miłecki <rafal@milecki.pl>
>
> Fix following validation error:
> arch/arm64/boot/dts/mediatek/mt7622-rfb1.dtb: ethernet@1b100000: compatible: ['mediatek,mt7622-eth', 'mediatek,mt2701-eth', 'syscon'] is too long
> from schema $id: http://devicetree.org/schemas/net/mediatek,net.yaml#
> (and other complains about wrong clocks).
>
> Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
Fixes tag?
Thanks,
Angelo
next prev parent reply other threads:[~2024-03-04 10:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 11:35 [PATCH 0/4] arm64: dts: mediatek: mt7622: fix some validation errors Rafał Miłecki
2024-03-01 11:35 ` [PATCH 1/4] arm64: dts: mediatek: mt7622: fix clock controllers Rafał Miłecki
2024-03-04 10:12 ` AngeloGioacchino Del Regno
2024-03-01 11:35 ` [PATCH 2/4] arm64: dts: mediatek: mt7622: fix IR nodename Rafał Miłecki
2024-03-04 10:12 ` AngeloGioacchino Del Regno
2024-03-01 11:35 ` [PATCH 3/4] arm64: dts: mediatek: mt7622: fix ethernet controller "compatible" Rafał Miłecki
2024-03-04 10:12 ` AngeloGioacchino Del Regno [this message]
2024-03-01 11:35 ` [PATCH 4/4] arm64: dts: mediatek: mt7622: drop "reset-names" from thermal block Rafał Miłecki
2024-03-04 10:13 ` AngeloGioacchino Del Regno
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=fcba424c-eb0b-4a43-b657-eeef811809c4@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.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=rafal@milecki.pl \
--cc=robh@kernel.org \
--cc=zajec5@gmail.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 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).