Devicetree
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Bjorn Andersson <andersson@kernel.org>,
	Mathieu Poirier <mathieu.poirier@linaro.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Manivannan Sadhasivam <mani@kernel.org>,
	Mukesh Ojha <mukesh.ojha@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org, linux-remoteproc@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: remoteproc: qcom,sm8550-pas: Add Hawi and Maili MPSS compatible
Date: Tue, 4 Aug 2026 10:43:46 +0200	[thread overview]
Message-ID: <0dbe41fe-e05b-4e5a-9de2-a682674ce40a@kernel.org> (raw)
In-Reply-To: <178546838834.317434.17458132438871669858.b4-ty@kernel.org>

On 31/07/2026 05:26, Bjorn Andersson wrote:
> 
> On Mon, 13 Jul 2026 15:02:37 +0530, Mukesh Ojha wrote:
>> Document compatible string for the MPSS Peripheral Authentication
>> Service on the Hawi and Maili SoCs. The Hawi and Maili MPSS is
>> compatible with the SM8650 MPSS (six interrupts, CX and MSS power
>> domains, memory region).
>>
>>
> 
> Applied, thanks!
> 
> [1/1] dt-bindings: remoteproc: qcom,sm8550-pas: Add Hawi and Maili MPSS compatible
>       commit: 77a6aafb404dda8ed6c2689dd78e10377ccebb4d

So this was applied and IMMEDIATELY after fixup was sent. I assume the
fixup was known and somehow was waiting till gets applied.

This is just wrong approach. Can we drop the patch instead?

Best regards,
Krzysztof

  reply	other threads:[~2026-08-04  8:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-13  9:32 [PATCH] dt-bindings: remoteproc: qcom,sm8550-pas: Add Hawi and Maili MPSS compatible Mukesh Ojha
2026-07-14 13:31 ` Manivannan Sadhasivam
2026-07-17  7:36 ` Yijie Yang
2026-07-21  8:39 ` Krzysztof Kozlowski
2026-07-27 11:22 ` Krzysztof Kozlowski
2026-07-31  3:26 ` Bjorn Andersson
2026-08-04  8:43   ` Krzysztof Kozlowski [this message]
2026-08-04 16:00     ` Bjorn Andersson
2026-08-04 16:02       ` Krzysztof Kozlowski

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=0dbe41fe-e05b-4e5a-9de2-a682674ce40a@kernel.org \
    --to=krzk@kernel.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@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=mani@kernel.org \
    --cc=mathieu.poirier@linaro.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