Devicetree
 help / color / mirror / Atom feed
From: Yadu M G <yadu.mg@oss.qualcomm.com>
To: andersson@kernel.org
Cc: konradybcio@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, brgl@kernel.org,
	deepti.jaggi@oss.qualcomm.com, shengchao.guo@oss.qualcomm.com,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v8 5/6] arm64: dts: qcom: Add device tree for Nord Ride board
Date: Wed,  5 Aug 2026 12:30:11 +0530	[thread overview]
Message-ID: <20260805070011.2921900-1-yadu.mg@oss.qualcomm.com> (raw)
In-Reply-To: <20260729010022.875799-6-shengchao.guo@oss.qualcomm.com>

Tested-by: Yadu M G <yadu.mg@oss.qualcomm.com>

Tested boot on Nord Ride SX platform.

  reply	other threads:[~2026-08-05  7:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-29  1:00 [PATCH v8 0/6] Add initial device trees for Nord platform Shawn Guo
2026-07-29  1:00 ` [PATCH v8 1/6] arm64: dts: qcom: Add device tree for Nord SoC series Shawn Guo
2026-07-29  1:14   ` sashiko-bot
2026-07-29  1:00 ` [PATCH v8 2/6] arm64: dts: qcom: Add device tree for Nord GearVM variant Shawn Guo
2026-07-29  1:00 ` [PATCH v8 3/6] arm64: dts: qcom: Add device tree for Nord Embedded variant Shawn Guo
2026-07-29  1:10   ` sashiko-bot
2026-08-05  6:08   ` Mukesh Savaliya
2026-08-06  4:03     ` Shawn Guo
2026-07-29  1:00 ` [PATCH v8 4/6] dt-bindings: arm: qcom: Document Nord reference boards Shawn Guo
2026-07-29  1:08   ` sashiko-bot
2026-07-29  1:00 ` [PATCH v8 5/6] arm64: dts: qcom: Add device tree for Nord Ride board Shawn Guo
2026-08-05  7:00   ` Yadu M G [this message]
2026-07-29  1:00 ` [PATCH v8 6/6] arm64: dts: qcom: Add device tree for Nord RRD board Shawn Guo
2026-07-29  1:13   ` sashiko-bot
2026-07-29  7:20 ` [PATCH v8 0/6] Add initial device trees for Nord platform Shawn Guo

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=20260805070011.2921900-1-yadu.mg@oss.qualcomm.com \
    --to=yadu.mg@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=brgl@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=deepti.jaggi@oss.qualcomm.com \
    --cc=devicetree@vger.kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=shengchao.guo@oss.qualcomm.com \
    /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