From: Bjorn Andersson <andersson@kernel.org>
To: Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>
Cc: Abel Vesa <abelvesa@kernel.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: (subset) [PATCH 1/4] arm64: dts: qcom: hawi: Sort IPCC client IDs
Date: Fri, 25 Sep 2026 11:43:30 -0500 [thread overview]
Message-ID: <179035461218.1296652.8764249187439190973.b4-ty@b4> (raw)
In-Reply-To: <20260925101309.3826038-1-mukesh.ojha@oss.qualcomm.com>
On Fri, 25 Sep 2026 15:43:05 +0530, Mukesh Ojha wrote:
> The IPCC client ID macros within each group in hawi-ipcc.h are not
> ordered by their numeric values, making it harder to cross-check
> against hardware documentation and spot missing IDs at a glance.
>
> Sort the defines in the IPCC_MPROC, IPCC_COMPUTE_L0, IPCC_COMPUTE_L1,
> and IPCC_FENCE groups by ascending value.
>
> [...]
Applied, thanks!
[1/4] arm64: dts: qcom: hawi: Sort IPCC client IDs
commit: e8493dd1265294c999cb5badbc26c6b42ea5c499
[2/4] arm64: dts: qcom: hawi: Fix PCIe IOMMU maps
commit: 5105107939b082a98446018e5679d16724fcc75f
[3/4] arm64: dts: qcom: hawi: Enable SoCCP by default
commit: 2b5d5dea36d4d45246cef89611c8e7a6002aa6a3
[4/4] arm64: dts: qcom: hawi: Trivial fix
commit: 7ce6844c0d6ade683fc741c9409a406eb754ed11
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2026-09-25 16:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 10:13 Mukesh Ojha
2026-09-25 10:13 ` [PATCH 2/4] arm64: dts: qcom: hawi: Fix PCIe IOMMU maps Mukesh Ojha
2026-09-25 10:23 ` Konrad Dybcio
2026-09-25 10:13 ` [PATCH 3/4] arm64: dts: qcom: hawi: Enable SoCCP by default Mukesh Ojha
2026-09-25 10:19 ` Konrad Dybcio
2026-09-25 10:13 ` [PATCH 4/4] arm64: dts: qcom: hawi: Trivial fix Mukesh Ojha
2026-09-25 16:43 ` Bjorn Andersson [this message]
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=179035461218.1296652.8764249187439190973.b4-ty@b4 \
--to=andersson@kernel.org \
--cc=abelvesa@kernel.org \
--cc=conor+dt@kernel.org \
--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=mukesh.ojha@oss.qualcomm.com \
--cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®