From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Marco Felsch <m.felsch@pengutronix.de>,
robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
conor+dt@kernel.org, shawnguo@kernel.org, kernel@pengutronix.de,
festevam@gmail.com, linux-imx@nxp.com,
laurent.pinchart@ideasonboard.com, dan.scally@ideasonboard.com
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 2/4] dt-bindings: arm: fsl: fix DEBIX binding
Date: Tue, 8 Aug 2023 18:07:57 +0200 [thread overview]
Message-ID: <9a86a125-2eda-721b-8b17-c1cfe144adc9@linaro.org> (raw)
In-Reply-To: <20230807171513.156907-2-m.felsch@pengutronix.de>
On 07/08/2023 19:15, Marco Felsch wrote:
> The current imx8mp-debix-model-a.dts uses all three compatibles. Fix the
> corresponding bindings by adding an own entry for it. Mark
> polyhex,imx8mp-debix as deprecated but keep it within the dts file since
The deprecation did not happen anymore.
> we already have a user for it [1].
>
> [1] https://elixir.bootlin.com/barebox/v2023.07.1/source/arch/arm/ \
> boards/polyhex-debix/board.c#L38
>
> Signed-off-by: Marco Felsch <m.felsch@pengutronix.de>
> ---
> Changelog:
>
> v3:
> - drop 'deprecated' status and adapt comment instead
With adjustments in commit msg:
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-08-08 17:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 17:15 [PATCH v3 1/4] arm64: dts: imx8mp-debix: remove unused fec pinctrl node Marco Felsch
2023-08-07 17:15 ` [PATCH v3 2/4] dt-bindings: arm: fsl: fix DEBIX binding Marco Felsch
2023-08-08 16:07 ` Krzysztof Kozlowski [this message]
2023-08-08 17:25 ` Marco Felsch
2023-08-07 17:15 ` [PATCH v3 3/4] dt-bindings: arm: Add Polyhex DEBIX SOM A based boards Marco Felsch
2023-08-08 16:08 ` Krzysztof Kozlowski
2023-08-07 17:15 ` [PATCH v3 4/4] arm64: dts: freescale: Add DEBIX SOM A and SOM A I/O Board support Marco Felsch
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=9a86a125-2eda-721b-8b17-c1cfe144adc9@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=conor+dt@kernel.org \
--cc=dan.scally@ideasonboard.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.felsch@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=shawnguo@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).