From: Neil Armstrong <neil.armstrong@linaro.org>
To: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org,
Neil Armstrong <neil.armstrong@linaro.org>
Subject: [PATCH v2 0/2] qcom: socinfo: Add SM8650 SoC ID table entry
Date: Mon, 30 Oct 2023 10:55:18 +0100 [thread overview]
Message-ID: <20231030-topic-sm8650-upstream-socinfo-v2-0-4751e7391dc9@linaro.org> (raw)
For convenience, a regularly refreshed linux-next based git tree containing
all the SM8650 related work is available at:
https://git.codelinaro.org/neil.armstrong/linux/-/tree/topic/sm8650/upstream/integ
Signed-off-by: Neil Armstrong <neil.armstrong@linaro.org>
---
Changes in v2:
- Splitted patch in 2, moved ID definition in bindings changes patch
- Link to v1: https://lore.kernel.org/r/20231025-topic-sm8650-upstream-socinfo-v1-1-6776a5183fa0@linaro.org
---
Neil Armstrong (2):
dt-bindings: arm: qcom,ids: Add SoC ID for SM8650
soc: qcom: socinfo: Add SM8650 SoC ID table entry
drivers/soc/qcom/socinfo.c | 1 +
include/dt-bindings/arm/qcom,ids.h | 1 +
2 files changed, 2 insertions(+)
---
base-commit: fe1998aa935b44ef873193c0772c43bce74f17dc
change-id: 20231016-topic-sm8650-upstream-socinfo-a4470a24cf91
Best regards,
--
Neil Armstrong <neil.armstrong@linaro.org>
next reply other threads:[~2023-10-30 9:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-30 9:55 Neil Armstrong [this message]
2023-10-30 9:55 ` [PATCH v2 1/2] dt-bindings: arm: qcom,ids: Add SoC ID for SM8650 Neil Armstrong
2023-10-30 12:17 ` Mukesh Ojha
2023-10-30 14:35 ` Krzysztof Kozlowski
2023-10-30 9:55 ` [PATCH v2 2/2] soc: qcom: socinfo: Add SM8650 SoC ID table entry Neil Armstrong
2023-10-30 12:22 ` Mukesh Ojha
2023-12-08 14:55 ` [PATCH v2 0/2] " Bjorn Andersson
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=20231030-topic-sm8650-upstream-socinfo-v2-0-4751e7391dc9@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.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 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.