From: sashiko-bot@kernel.org
To: "Peter Griffin" <peter.griffin@linaro.org>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org,
linux-serial@vger.kernel.org
Subject: Re: [PATCH v4 2/4] arm64: dts: google: Add dts directory for Google-designed silicon
Date: Fri, 18 Sep 2026 19:08:57 +0000 [thread overview]
Message-ID: <20260918190858.682B11F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20260918-contrib-pg-pixel10-initial-dts-v4-2-745eaca28b1a@linaro.org>
> From: Douglas Anderson <dianders@chromium.org>
>
> The first four Google Tensor SoCs were offshoots of Samsung Exynos
> SoCs and their device trees were organized under the "exynos/google"
> directory. Starting with the Google Tensor G5 SoC in Pixel 10 phones,
> Google Tensor SoCs are now of Google's own design. Add a location in
> the tree to store these device tree files.
>
> Changes by Peter Griffin
> * update config symbol help with at least 4 lines to avoid checkpatch
> warning
>
> Signed-off-by: Douglas Anderson <dianders@chromium.org>
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
> Tested-by: Brian Norris <briannorris@chromium.org>
> Reviewed-by: Brian Norris <briannorris@chromium.org>
> Signed-off-by: Peter Griffin <peter.griffin@linaro.org>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260918-contrib-pg-pixel10-initial-dts-v4-0-745eaca28b1a@linaro.org?part=2
next prev parent reply other threads:[~2026-09-18 19:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 19:05 [PATCH v4 0/4] Add Laguna/Tensor G5 SoC and Frankel, Blazer & Mustang boards Peter Griffin
2026-09-18 19:05 ` [PATCH v4 1/4] dt-bindings: arm: google: Add dt bindings for frankel/blazer/mustang Peter Griffin
2026-09-18 19:07 ` sashiko-bot
2026-09-18 19:05 ` [PATCH v4 2/4] arm64: dts: google: Add dts directory for Google-designed silicon Peter Griffin
2026-09-18 19:08 ` sashiko-bot [this message]
2026-09-30 21:47 ` Linus Walleij
2026-09-18 19:05 ` [PATCH v4 3/4] arm64: dts: google: Add initial dts for frankel/blazer/mustang Peter Griffin
2026-09-18 19:10 ` sashiko-bot
2026-09-20 15:16 ` Krzysztof Kozlowski
2026-09-29 8:56 ` Peter Griffin
2026-10-01 20:26 ` Linus Walleij
2026-09-18 19:05 ` [PATCH v4 4/4] arm64: defconfig: enable Tensor G5 SoC family Peter Griffin
2026-09-18 19:07 ` sashiko-bot
2026-09-20 15:27 ` Krzysztof Kozlowski
2026-09-29 9:41 ` [PATCH v4 0/4] Add Laguna/Tensor G5 SoC and Frankel, Blazer & Mustang boards Krzysztof Kozlowski
2026-09-29 9:56 ` Krzysztof Kozlowski
2026-09-29 10:09 ` Peter Griffin
2026-09-29 10:16 ` Peter Griffin
2026-09-29 10:17 ` Krzysztof Kozlowski
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=20260918190858.682B11F000FF@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=peter.griffin@linaro.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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.