From: Heiko Stuebner <heiko@sntech.de>
To: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Brian Norris <briannorris@chromium.org>
Cc: Heiko Stuebner <heiko@sntech.de>,
linux-kernel@vger.kernel.org, Chen-Yu Tsai <wenst@chromium.org>,
linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: arm: rockchip: Add gru-scarlet sku{2,4} variants
Date: Thu, 15 Sep 2022 15:49:06 +0200 [thread overview]
Message-ID: <166324955276.172936.10946174997908284073.b4-ty@sntech.de> (raw)
In-Reply-To: <20220817123350.1.Ibb15bab32dbfa0d89f86321c4eae7adbc8d7ad4a@changeid>
On Wed, 17 Aug 2022 12:33:55 -0700, Brian Norris wrote:
> The Gru-Scarlet family includes a variety of SKU identifiers, using
> parts of a 3-bit space {0..7}. SKU2 and SKU4 devices (under a few
> different manufacturer names) also use the Innolux display.
>
> For reference, the original vendor tree source:
>
> CHROMIUM: arm64: dts: rockchip: add sku{0,2,4} compatibility
> https://chromium.googlesource.com/chromiumos/third_party/kernel/+/f6ed665c9e2eb37fb2680debbb36ec9fb0e8fb97
>
> [...]
I cornored Krzysztof at ELCE today and he had no objections, so
Applied, thanks!
[1/2] dt-bindings: arm: rockchip: Add gru-scarlet sku{2,4} variants
commit: b360cfbf86a918b835e673b9da5faf972a9bf146
[2/2] arm64: dts: rockchip: Support gru-scarlet sku{2,4} variants
commit: 578980728868fcd99bbb5af12e50b38d2e66f5aa
Best regards,
--
Heiko Stuebner <heiko@sntech.de>
prev parent reply other threads:[~2022-09-15 13:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 19:33 Brian Norris
2022-08-17 19:33 ` [PATCH 2/2] arm64: dts: rockchip: Support " Brian Norris
2022-08-18 10:01 ` [PATCH 1/2] dt-bindings: arm: rockchip: Add " Krzysztof Kozlowski
2022-08-22 18:57 ` Brian Norris
2022-09-14 22:44 ` Brian Norris
2022-09-15 13:49 ` 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=166324955276.172936.10946174997908284073.b4-ty@sntech.de \
--to=heiko@sntech.de \
--cc=briannorris@chromium.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-rockchip@lists.infradead.org \
--cc=robh+dt@kernel.org \
--cc=wenst@chromium.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
all inboxes | Powered by JetHome®