From: Krzysztof Kozlowski <krzk@kernel.org>
To: Bjorn Andersson <andersson@kernel.org>,
Sibi Sankar <sibi.sankar@oss.qualcomm.com>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
jingyi.wang@oss.qualcomm.com, mathieu.poirier@linaro.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: remoteproc: qcom,pas: Document SoCCP PAS for Glymur
Date: Thu, 9 Oct 2025 19:36:54 +0900 [thread overview]
Message-ID: <764c93c2-535f-450e-b395-4a0090cc3ab8@kernel.org> (raw)
In-Reply-To: <ydfiugeifs5c6v7dzms5tlkkmhf26q42pav2ugfuxjytugr5nc@ppxoiize27ug>
On 26/09/2025 02:22, Bjorn Andersson wrote:
> On Thu, Sep 25, 2025 at 05:50:34AM +0530, Sibi Sankar wrote:
>> Document compatible for Qualcomm Glymur SoC SoCCP (SoC Control Processor)
>> PAS which is fully compatible with Kaanapali.
>>
>> Signed-off-by: Sibi Sankar <sibi.sankar@oss.qualcomm.com>
>> ---
>>
>> Dependencies:
>> [1] Add initial remoteproc support for Kaanapali SoC
>> https://lore.kernel.org/linux-arm-msm/20250924-knp-remoteproc-v1-0-611bf7be8329@oss.qualcomm.com/T/#t
>
> Please don't send out patches that depend on other patches sent out the
> same day. This just assumes that the maintainer will keep track of
> dependencies and figure out when a future version of that dependency
> meets the needs of this version.
>
> Work with Jingyi to handle dependencies on your side.
@Bjorn, it is getting better.
This part of Glymur depends on Kaanapali patches. But there are
Kaanapali patches depending on Glymur!
There is absolutely zero coordination between these two and total mess
of multiplying patches instead of sending ONE thing. Submitting Glymur
and Kaanapali was really screwed.
Best regards,
Krzysztof
prev parent reply other threads:[~2025-10-09 10:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-25 0:20 [PATCH] dt-bindings: remoteproc: qcom,pas: Document SoCCP PAS for Glymur Sibi Sankar
2025-09-25 17:22 ` Bjorn Andersson
2025-10-09 10:20 ` Sibi Sankar
2025-10-09 10:36 ` Krzysztof Kozlowski [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=764c93c2-535f-450e-b395-4a0090cc3ab8@kernel.org \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jingyi.wang@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=robh@kernel.org \
--cc=sibi.sankar@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