From: Oleksij Rempel <o.rempel@pengutronix.de>
To: "Rob Herring (Arm)" <robh@kernel.org>
Cc: linux-kernel@vger.kernel.org, Jakub Kicinski <kuba@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Woojung Huh <woojung.huh@microchip.com>,
Paolo Abeni <pabeni@redhat.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
devicetree@vger.kernel.org, Eric Dumazet <edumazet@google.com>,
linux-stm32@st-md-mailman.stormreply.com,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
kernel@pengutronix.de
Subject: Re: [PATCH v3 0/4] Add support for Priva E-Measuringbox board
Date: Wed, 5 Feb 2025 10:17:19 +0100 [thread overview]
Message-ID: <Z6Msn8AxgG_JTVNs@pengutronix.de> (raw)
In-Reply-To: <173859694746.2601652.11244969424431209545.robh@kernel.org>
Hi Alexandre,
On Mon, Feb 03, 2025 at 09:37:06AM -0600, Rob Herring (Arm) wrote:
>
> On Mon, 03 Feb 2025 09:58:16 +0100, Oleksij Rempel wrote:
> > This patch series introduces support for the Priva E-Measuringbox board
> > based on the ST STM32MP133 SoC. The set includes all the necessary
> > changes for device tree bindings, vendor prefixes, thermal support, and
> > board-specific devicetree to pass devicetree validation and checkpatch
> > tests.
> >
...
> arch/arm/boot/dts/st/stm32mp133c-prihmb.dtb: adc@48004000: adc@0:interrupts: 0 was expected
> from schema $id: http://devicetree.org/schemas/iio/adc/st,stm32-adc.yaml#
> arch/arm/boot/dts/st/stm32mp133c-prihmb.dtb: adc@48003000: adc@0:interrupts: 0 was expected
> from schema $id: http://devicetree.org/schemas/iio/adc/st,stm32-adc.yaml#
>
Can I please get your attention here. The reported issue is not related
to this patch set. adc@0:interrupts are set in the dtsi file.
Kind regards,
Oleksij
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2025-02-05 9:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 8:58 [PATCH v3 0/4] Add support for Priva E-Measuringbox board Oleksij Rempel
2025-02-03 8:58 ` [PATCH v3 1/4] dt-bindings: vendor-prefixes: Add prefix for Priva Oleksij Rempel
2025-02-03 8:58 ` [PATCH v3 2/4] dt-bindings: arm: stm32: Add Priva E-Measuringbox board Oleksij Rempel
2025-02-03 8:58 ` [PATCH v3 3/4] arm: dts: stm32: Add thermal support for STM32MP131 Oleksij Rempel
2025-02-03 8:58 ` [PATCH v3 4/4] arm: dts: stm32: Add Priva E-Measuringbox devicetree Oleksij Rempel
2025-02-03 15:37 ` [PATCH v3 0/4] Add support for Priva E-Measuringbox board Rob Herring (Arm)
2025-02-05 9:17 ` Oleksij Rempel [this message]
2025-02-05 16:02 ` Alexandre TORGUE
2025-02-26 6:59 ` Oleksij Rempel
2025-02-26 13:24 ` Alexandre TORGUE
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=Z6Msn8AxgG_JTVNs@pengutronix.de \
--to=o.rempel@pengutronix.de \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
--cc=woojung.huh@microchip.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.