Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: YijieYang <yijie.yang@oss.qualcomm.com>,
	andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
	devicetree@vger.kernel.org, krzysztof.kozlowski@oss.qualcomm.com
Subject: Re: [PATCH v2 0/4] Initial patch set for PURWA-IOT-EVK
Date: Fri, 9 Jan 2026 09:06:57 +0100	[thread overview]
Message-ID: <2e8e6436-96a3-40d2-86ce-a716326f79bf@kernel.org> (raw)
In-Reply-To: <20260109-purwa-v2-0-f39ee10684cb@oss.qualcomm.com>

On 09/01/2026 08:59, YijieYang wrote:
> 
> Signed-off-by: Yijie Yang <yijie.yang@oss.qualcomm.com>
> ---
> Changes since V1:
> - Update the GPU firmware path.
> - Update the description in the cover letter.
> - Reorder the patches.
> - Use separate DTS files for Purwa and Hamoa.
> - Update base commit.

That's a b4 patchset, so where are the links?

> 
> ---
> Yijie Yang (4):
>       dt-bindings: arm: qcom: Document PURWA-IOT-EVK board
>       firmware: qcom: scm: Allow QSEECOM on PURWA-IOT-EVK
>       arm64: dts: qcom: Add PURWA-IOT-SOM platform
>       arm64: dts: qcom: Add base PURWA-IOT-EVK board
> 
>  Documentation/devicetree/bindings/arm/qcom.yaml |    6 +
>  arch/arm64/boot/dts/qcom/Makefile               |    1 +
>  arch/arm64/boot/dts/qcom/purwa-iot-evk.dts      | 1313 +++++++++++++++++++++++
>  arch/arm64/boot/dts/qcom/purwa-iot-som.dtsi     |  614 +++++++++++
>  drivers/firmware/qcom/qcom_scm.c                |    1 +
>  5 files changed, 1935 insertions(+)
> ---
> base-commit: beff4beeeb2760405ad49de2a6a1bdab8fb1aec3
> change-id: 20251113-purwa-907ec75b4959
> 


Best regards,
Krzysztof

  parent reply	other threads:[~2026-01-09  8:07 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-09  7:59 [PATCH v2 0/4] Initial patch set for PURWA-IOT-EVK YijieYang
2026-01-09  7:59 ` [PATCH v2 1/4] dt-bindings: arm: qcom: Document PURWA-IOT-EVK board YijieYang
2026-01-09  7:59 ` [PATCH v2 2/4] firmware: qcom: scm: Allow QSEECOM on PURWA-IOT-EVK YijieYang
2026-01-09 12:48   ` Dmitry Baryshkov
2026-01-09  7:59 ` [PATCH v2 3/4] arm64: dts: qcom: Add PURWA-IOT-SOM platform YijieYang
2026-01-09 12:10   ` Dmitry Baryshkov
2026-01-12  3:02     ` Yijie Yang
2026-01-09  7:59 ` [PATCH v2 4/4] arm64: dts: qcom: Add base PURWA-IOT-EVK board YijieYang
2026-01-09 11:29   ` Konrad Dybcio
2026-01-12  3:12     ` Yijie Yang
2026-01-12  5:00       ` Dmitry Baryshkov
2026-01-12  5:51         ` Yijie Yang
2026-01-12  6:01           ` Dmitry Baryshkov
2026-01-12 10:54             ` Konrad Dybcio
2026-01-13  1:45             ` Yijie Yang
2026-01-12  7:14           ` Krzysztof Kozlowski
2026-01-09  8:06 ` Krzysztof Kozlowski [this message]
2026-01-09  8:26   ` [PATCH v2 0/4] Initial patch set for PURWA-IOT-EVK Yijie Yang
2026-01-09  9:04     ` Krzysztof Kozlowski
2026-01-09  9:28     ` Konrad Dybcio
2026-01-12  3:13       ` Yijie Yang

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=2e8e6436-96a3-40d2-86ce-a716326f79bf@kernel.org \
    --to=krzk@kernel.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzysztof.kozlowski@oss.qualcomm.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=yijie.yang@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