From: Krzysztof Kozlowski <krzk@kernel.org>
To: Gokul Sriram Palanisamy <quic_gokulsri@quicinc.com>,
andersson@kernel.org, krzk+dt@kernel.org,
linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: quic_viswanat@quicinc.com, quic_mmanikan@quicinc.com,
quic_varada@quicinc.com, quic_srichara@quicinc.com
Subject: Re: [PATCH 0/4] Add new driver for WCSS secure PIL loading
Date: Tue, 20 Aug 2024 13:12:58 +0200 [thread overview]
Message-ID: <4d1c0d17-20b8-4989-9757-61031e9f03a4@kernel.org> (raw)
In-Reply-To: <20240820085517.435566-1-quic_gokulsri@quicinc.com>
On 20/08/2024 10:55, Gokul Sriram Palanisamy wrote:
> This series depends on q6 clock removal series [1].
How? So this cannot be tested and merged?
That's second patchset to day with some totally bogus dependencies.
People, stop it.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-08-20 11:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 8:55 [PATCH 0/4] Add new driver for WCSS secure PIL loading Gokul Sriram Palanisamy
2024-08-20 8:55 ` [PATCH 1/2] dt-bindings: remoteproc: qcom: document hexagon based WCSS secure PIL Gokul Sriram Palanisamy
2024-08-20 11:20 ` Krzysztof Kozlowski
2024-08-22 10:47 ` Gokul Sriram P
2024-08-22 11:30 ` Krzysztof Kozlowski
[not found] ` <982ca02e-a0b0-4dac-9294-ae2c2fb3463f@quicinc.com>
2024-08-23 13:47 ` Krzysztof Kozlowski
2024-08-20 8:55 ` [PATCH 2/2] remoteproc: qcom: add hexagon based WCSS secure PIL driver Gokul Sriram Palanisamy
2024-08-20 11:25 ` Krzysztof Kozlowski
2024-08-22 9:01 ` Gokul Sriram P
2024-08-20 8:55 ` [PATCH 3/4] arm64: dts: qcom: ipq5332: add nodes to bringup q6 Gokul Sriram Palanisamy
2024-08-20 11:21 ` Krzysztof Kozlowski
2024-08-22 10:38 ` Gokul Sriram P
2024-08-20 8:55 ` [PATCH 4/4] arm64: dts: qcom: ipq9574: add nodes to bring up q6 Gokul Sriram Palanisamy
2024-08-20 11:12 ` Krzysztof Kozlowski [this message]
2024-08-22 10:43 ` [PATCH 0/4] Add new driver for WCSS secure PIL loading Gokul Sriram P
2024-08-22 11:28 ` Krzysztof Kozlowski
2024-08-23 9:49 ` Gokul Sriram P
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=4d1c0d17-20b8-4989-9757-61031e9f03a4@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=quic_gokulsri@quicinc.com \
--cc=quic_mmanikan@quicinc.com \
--cc=quic_srichara@quicinc.com \
--cc=quic_varada@quicinc.com \
--cc=quic_viswanat@quicinc.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