From: Bjorn Andersson <andersson@kernel.org>
To: Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bjorn Andersson <quic_bjorande@quicinc.com>,
quic_tsoni@quicinc.com, Komal Bajaj <quic_kbajaj@quicinc.com>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] Enable various remoteprocs for qcm6490-idp and qcs6490-rb3gen2
Date: Sun, 21 Apr 2024 17:29:23 -0500 [thread overview]
Message-ID: <171373856754.1196479.8348340567259271476.b4-ty@kernel.org> (raw)
In-Reply-To: <20240417120928.32344-1-quic_kbajaj@quicinc.com>
On Wed, 17 Apr 2024 17:39:26 +0530, Komal Bajaj wrote:
> Enable various applicable remoteproc nodes for qcm6490-idp
> and qcs6490-rb3gen2.
>
> Firmwares are not shared at linux-firmware.git, it is under legal approval process.
> Meantime, submitting the DT node changes for FW for review.
>
> --------
> Changes in v3:
> * Rebased on top of linux-next
> * Added firmware path for modem for rb3gen2 board for GPS usecase
> * Link to v2: https://lore.kernel.org/all/20240402090349.30172-1-quic_kbajaj@quicinc.com/
>
> [...]
Applied, thanks!
[1/2] arm64: dts: qcom: qcm6490-idp: Enable various remoteprocs
commit: 99a1c9eedf6098826c0f9dcbda2c23e5dad20244
[2/2] arm64: dts: qcom: qcs6490-rb3gen2: Enable various remoteprocs
commit: ac6d35b9b74c113753bd266e01d6b853618a1e37
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2024-04-21 22:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 12:09 [PATCH v3 0/2] Enable various remoteprocs for qcm6490-idp and qcs6490-rb3gen2 Komal Bajaj
2024-04-17 12:09 ` [PATCH v3 1/2] arm64: dts: qcom: qcm6490-idp: Enable various remoteprocs Komal Bajaj
2024-04-17 18:25 ` Dmitry Baryshkov
2024-04-17 12:09 ` [PATCH v3 2/2] arm64: dts: qcom: qcs6490-rb3gen2: " Komal Bajaj
2024-04-17 18:24 ` Dmitry Baryshkov
2024-04-21 22:29 ` 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=171373856754.1196479.8348340567259271476.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=quic_bjorande@quicinc.com \
--cc=quic_kbajaj@quicinc.com \
--cc=quic_tsoni@quicinc.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;
as well as URLs for NNTP newsgroup(s).