From: Tom Rini <trini@konsulko.com>
To: Sumit Garg <sumit.garg@linaro.org>
Cc: u-boot@lists.denx.de, rfried.dev@gmail.com, peng.fan@nxp.com,
jh80.chung@samsung.com, sjg@chromium.org, dsankouski@gmail.com,
stephan@gerhold.net, vinod.koul@linaro.org,
nicolas.dechesne@linaro.org, mworsfold@impinj.com,
daniel.thompson@linaro.org, pbrobinson@gmail.com
Subject: Re: [PATCH v3 2/9] arm64: dts: sdm845: Remove redundant u-boot DT properties
Date: Mon, 25 Jul 2022 17:21:13 -0400 [thread overview]
Message-ID: <20220725212113.GI1146598@bill-the-cat> (raw)
In-Reply-To: <20220712071212.2188390-3-sumit.garg@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 513 bytes --]
On Tue, Jul 12, 2022 at 12:42:05PM +0530, Sumit Garg wrote:
> According to u-boot DT recomendation, u-boot specific DT properties belong
> to *-uboot.dtsi. Also for starqltechn board (which is the only current
> consumer of sdm845.dtsi), the properties are already included in
> starqltechn-uboot.dtsi, so remove corresponding redundant properties.
>
> Signed-off-by: Sumit Garg <sumit.garg@linaro.org>
> Reviewed-by: Ramon Fried <rfried.dev@gmail.com>
Applied to u-boot/master, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2022-07-25 21:22 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 7:12 [PATCH v3 0/9] New boards support: db845c and qcs404-evb Sumit Garg
2022-07-12 7:12 ` [PATCH v3 1/9] board: starqltechn: Align DT node overrides with sdm845.dtsi Sumit Garg
2022-07-25 21:21 ` Tom Rini
2022-07-12 7:12 ` [PATCH v3 2/9] arm64: dts: sdm845: Remove redundant u-boot DT properties Sumit Garg
2022-07-25 21:21 ` Tom Rini [this message]
2022-07-12 7:12 ` [PATCH v3 3/9] clocks: sdm845: Import qcom,gcc-sdm845.h Sumit Garg
2022-07-25 21:21 ` Tom Rini
2022-07-12 7:12 ` [PATCH v3 4/9] uart: sdm845: Fix debug UART pinmux Sumit Garg
2022-07-25 21:21 ` Tom Rini
2022-07-12 7:12 ` [PATCH v3 5/9] board: qualcomm: Add support for dragonboard845c Sumit Garg
2022-07-25 21:21 ` Tom Rini
2023-08-23 23:57 ` Simon Glass
2023-08-24 10:43 ` Sumit Garg
2023-08-28 17:54 ` Simon Glass
2023-08-28 20:23 ` Peter Robinson
2023-08-28 22:09 ` Simon Glass
2023-08-29 10:24 ` Sumit Garg
2023-09-10 23:14 ` Simon Glass
2022-07-12 7:12 ` [PATCH v3 6/9] mmc: msm_sdhci: Add SDCC version 5.0.0 support Sumit Garg
2022-07-25 21:21 ` Tom Rini
2022-07-12 7:12 ` [PATCH v3 7/9] pinctrl: qcom: Add pinctrl driver for QCS404 SoC Sumit Garg
2022-07-25 21:21 ` Tom Rini
2022-07-12 7:12 ` [PATCH v3 8/9] clocks: qcom: Add clock " Sumit Garg
2022-07-25 21:21 ` Tom Rini
2022-07-12 7:12 ` [PATCH v3 9/9] board: qualcomm: Add support for QCS404 EVB Sumit Garg
2022-07-13 19:31 ` Stephan Gerhold
2022-07-14 7:40 ` Sumit Garg
2022-07-14 18:27 ` Stephan Gerhold
2022-07-15 10:24 ` Sumit Garg
2022-07-25 21:21 ` Tom Rini
2022-07-19 5:31 ` [PATCH v3 0/9] New boards support: db845c and qcs404-evb Sumit Garg
2022-07-19 11:01 ` Tom Rini
2022-07-19 11:09 ` Sumit Garg
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=20220725212113.GI1146598@bill-the-cat \
--to=trini@konsulko.com \
--cc=daniel.thompson@linaro.org \
--cc=dsankouski@gmail.com \
--cc=jh80.chung@samsung.com \
--cc=mworsfold@impinj.com \
--cc=nicolas.dechesne@linaro.org \
--cc=pbrobinson@gmail.com \
--cc=peng.fan@nxp.com \
--cc=rfried.dev@gmail.com \
--cc=sjg@chromium.org \
--cc=stephan@gerhold.net \
--cc=sumit.garg@linaro.org \
--cc=u-boot@lists.denx.de \
--cc=vinod.koul@linaro.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