Linux USB
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Stanislav Aleksandrov" <lightofmysoul@gmail.com>
Cc: mfd@lists.linux.dev, linux-usb@vger.kernel.org, lee@kernel.org
Subject: Re: [PATCH v2 11/16] dt-bindings: firmware: qcom,scm: Document Halliday SCM
Date: Mon, 16 Nov 2026 21:31:00 +0000	[thread overview]
Message-ID: <sashiko-outbox-217723@kernel.org> (raw)
In-Reply-To: <20261116-halliday-dts-v2-11-2c92438c6c46@gmail.com>

> Document the SCM on the Qualcomm Halliday SoC.
> 
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
> Signed-off-by: Stanislav Aleksandrov <lightofmysoul@gmail.com>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261116-halliday-dts-v2-0-2c92438c6c46@gmail.com?part=11


  reply	other threads:[~2026-11-16 21:31 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-16 21:26 [PATCH v2 00/16] Add initial support for Qualcomm Halliday and Samsung Galaxy XR Stanislav Aleksandrov
2026-11-16 21:26 ` [PATCH v2 01/16] dt-bindings: interrupt-controller: qcom,pdc: Document Halliday PDC Stanislav Aleksandrov
2026-11-16 21:29   ` sashiko-bot
2026-11-16 21:26 ` [PATCH v2 02/16] dt-bindings: power: qcom,rpmpd: document the Halliday RPMh Power Domains Stanislav Aleksandrov
2026-11-16 21:30   ` sashiko-bot
2026-11-16 21:26 ` [PATCH v2 03/16] dt-bindings: mfd: qcom,tcsr: Add Halliday TCSR Stanislav Aleksandrov
2026-11-16 21:29   ` sashiko-bot
2026-11-16 21:26 ` [PATCH v2 04/16] dt-bindings: arm-smmu: Add Halliday SMMU Stanislav Aleksandrov
2026-11-16 21:30   ` sashiko-bot
2026-11-16 21:26 ` [PATCH v2 05/16] dt-bindings: usb: qcom,snps-dwc3: Add Halliday Stanislav Aleksandrov
2026-11-16 21:26 ` [PATCH v2 06/16] dt-bindings: phy: qcom,usb-snps-femto-v2: Add Halliday HS PHY Stanislav Aleksandrov
2026-11-16 21:26 ` [PATCH v2 07/16] dt-bindings: phy: qcom,sc8280xp-qmp-ufs-phy: Add Halliday Stanislav Aleksandrov
2026-11-16 21:26 ` [PATCH v2 08/16] dt-bindings: ufs: qcom,sc7180-ufshc: Add Halliday UFS Stanislav Aleksandrov
2026-11-16 21:26 ` [PATCH v2 09/16] dt-bindings: crypto: qcom,inline-crypto-engine: Add Halliday Stanislav Aleksandrov
2026-11-16 21:31   ` sashiko-bot
2026-11-16 21:26 ` [PATCH v2 10/16] dt-bindings: thermal: qcom-tsens: Document the Halliday Temperature Sensor Stanislav Aleksandrov
2026-11-16 21:29   ` sashiko-bot
2026-11-16 21:26 ` [PATCH v2 11/16] dt-bindings: firmware: qcom,scm: Document Halliday SCM Stanislav Aleksandrov
2026-11-16 21:31   ` sashiko-bot [this message]
2026-11-16 21:26 ` [PATCH v2 12/16] dt-bindings: arm: qcom: Add Samsung Galaxy XR Stanislav Aleksandrov
2026-11-16 21:31   ` sashiko-bot
2026-11-16 21:26 ` [PATCH v2 13/16] dt-bindings: arm: qcom,ids: Add SoC ID for SXR2250P Stanislav Aleksandrov
2026-11-16 21:31   ` sashiko-bot
2026-11-16 21:26 ` [PATCH v2 14/16] soc: qcom: socinfo: Add SXR2250P SoC ID Stanislav Aleksandrov
2026-11-16 21:31   ` sashiko-bot
2026-11-16 21:26 ` [PATCH v2 15/16] arm64: dts: qcom: Add initial Halliday dtsi Stanislav Aleksandrov
2026-11-16 21:26 ` [PATCH v2 16/16] arm64: dts: qcom: Add Samsung Galaxy XR Stanislav Aleksandrov

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=sashiko-outbox-217723@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=lee@kernel.org \
    --cc=lightofmysoul@gmail.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=mfd@lists.linux.dev \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox