From: Heiko Stuebner <heiko@sntech.de>
To: Brian Norris <briannorris@chromium.org>,
Peter Geis <pgwipeout@gmail.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Chris Morgan <macromorgan@hotmail.com>,
Jagan Teki <jagan@amarulasolutions.com>,
Sebastian Reichel <sebastian.reichel@collabora.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Shawn Guo <shawnguo@kernel.org>, Tianling Shen <cnsztl@gmail.com>,
Andrew Lunn <andrew@lunn.ch>,
Maya Matuszczyk <maccraft123mc@gmail.com>,
Michael Riesch <michael.riesch@wolfvision.net>,
Vasily Khoruzhick <anarsoul@gmail.com>,
Bjorn Andersson <andersson@kernel.org>,
Rob Herring <robh+dt@kernel.org>, Andy Yan <andyshrk@163.com>
Cc: Heiko Stuebner <heiko@sntech.de>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
devicetree@vger.kernel.org, linux-rockchip@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/3] dt-bindings: Add doc for Fastrhino R66S / R68S
Date: Sun, 7 May 2023 12:54:24 +0200 [thread overview]
Message-ID: <168345676639.21260.15276266069370023718.b4-ty@sntech.de> (raw)
In-Reply-To: <20230506061108.17658-1-cnsztl@gmail.com>
On Sat, 6 May 2023 14:11:06 +0800, Tianling Shen wrote:
> Add devicetree binding documentation for the
> Lunzn Fastrhino R66S and R68S boards.
>
>
Applied, thanks!
[1/3] dt-bindings: Add doc for Fastrhino R66S / R68S
commit: b985ca5261171e559f4d9754481b5f6c6e15ad93
[2/3] arm64: dts: rockchip: Add Lunzn Fastrhino R66S
commit: ddb6cde1cf59eb57820a6c277b8b5cff45e68d68
[3/3] arm64: dts: rockchip: Add Lunzn Fastrhino R68S
commit: 5a9447fd17668c34449052e4f77eebc7a98eccf3
[v6.5-armsoc/dts64 branch, will be rebased once more after 6.4-rc1,
resorted some properties to be more alphabetically sorted
dropped one empty line at the end of the pmic node]
Best regards,
--
Heiko Stuebner <heiko@sntech.de>
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
prev parent reply other threads:[~2023-05-07 10:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-06 6:11 [PATCH v2 1/3] dt-bindings: Add doc for Fastrhino R66S / R68S Tianling Shen
2023-05-06 6:11 ` [PATCH v2 2/3] arm64: dts: rockchip: Add Lunzn Fastrhino R66S Tianling Shen
2023-05-06 6:11 ` [PATCH v2 3/3] arm64: dts: rockchip: Add Lunzn Fastrhino R68S Tianling Shen
2023-05-07 10:54 ` Heiko Stuebner [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=168345676639.21260.15276266069370023718.b4-ty@sntech.de \
--to=heiko@sntech.de \
--cc=anarsoul@gmail.com \
--cc=andersson@kernel.org \
--cc=andrew@lunn.ch \
--cc=andyshrk@163.com \
--cc=briannorris@chromium.org \
--cc=cnsztl@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jagan@amarulasolutions.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=maccraft123mc@gmail.com \
--cc=macromorgan@hotmail.com \
--cc=michael.riesch@wolfvision.net \
--cc=pgwipeout@gmail.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sebastian.reichel@collabora.com \
--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).