devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: "Bjorn Andersson" <andersson@kernel.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Johan Hovold" <johan+linaro@kernel.org>,
	"Konrad Dybcio" <konrad.dybcio@linaro.org>,
	"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
	"Krzysztof Wilczyński" <kw@linux.com>,
	"Rob Herring" <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
	linux-arm-msm@vger.kernel.org, linux-pci@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: (subset) [PATCH v4 0/5] arm64: dts: qcom: sc8280xp: PCIe fixes and GICv3 ITS enable
Date: Wed, 20 Mar 2024 09:40:40 +0100	[thread overview]
Message-ID: <ZfqhCKoEL4XGRs7T@hovoldconsulting.com> (raw)
In-Reply-To: <baf9c1bd-84ef-4ecb-b229-51a83fe82c3f@linaro.org>

On Wed, Mar 20, 2024 at 09:24:54AM +0100, Krzysztof Kozlowski wrote:
> On 20/03/2024 09:18, Johan Hovold wrote:

> > Perhaps you should not comment before reading up on the history of this
> > series.
> > 
> > This was all intended for 6.9, but merging was stalled for a number of
> > reasons so here we are. The patches were also going in through different
> > trees, so patch 4/5 is the first Qualcomm SoC patch.
> 
> Again, well, you sent it at few days before merge window, so how do you
> imagine this being applied for v6.9 and still fulfilling "few linux-next
> cycles before merge window" requirement? Especially that arm-soc cut off
> is much earlier :/. I talk about patch 5, of course, because that is not
> a fix (at least not marked as one). Don't expect in general a arms-co
> patch to be applied four days before merge window, thus the actual fix -
> patch #4 - should be split.

At the time there was still hope that there may be an rc8, and the patch
in question had been used by a large number of X13s users for several
weeks, which is a lot more testing than the average Qualcomm patch
receives, whether it's in linux-next or not.

And patch 5 depends on the earlier patches in the series so it belongs
in the series, which was also initially posted long before the merge
window.

I'm sure Bjorn A can handle this in general, even if he failed to notice
the CC stable tag or had other reasons for applying the fix for 6.10
instead of 6.9.

Johan

  reply	other threads:[~2024-03-20  8:40 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-06  9:56 [PATCH v4 0/5] arm64: dts: qcom: sc8280xp: PCIe fixes and GICv3 ITS enable Johan Hovold
2024-03-06  9:56 ` [PATCH v4 1/5] dt-bindings: PCI: qcom: Allow 'required-opps' Johan Hovold
2024-03-06  9:56 ` [PATCH v4 2/5] dt-bindings: PCI: qcom: Do not require 'msi-map-mask' Johan Hovold
2024-03-06  9:56 ` [PATCH v4 3/5] PCI: qcom: Disable ASPM L0s for sc8280xp, sa8540p and sa8295p Johan Hovold
2024-03-06 10:57   ` Manivannan Sadhasivam
2024-03-18  1:24   ` Bjorn Andersson
2024-03-06  9:56 ` [PATCH v4 4/5] arm64: dts: qcom: sc8280xp: add missing PCIe minimum OPP Johan Hovold
2024-03-06  9:56 ` [PATCH v4 5/5] arm64: dts: qcom: sc8280xp: enable GICv3 ITS for PCIe Johan Hovold
2024-03-08 15:47 ` [PATCH v4 0/5] arm64: dts: qcom: sc8280xp: PCIe fixes and GICv3 ITS enable Johan Hovold
2024-03-08 16:09 ` (subset) " Lorenzo Pieralisi
2024-03-19  2:48 ` Bjorn Andersson
2024-03-19  7:25   ` Johan Hovold
2024-03-20  8:09     ` Krzysztof Kozlowski
2024-03-20  8:18       ` Johan Hovold
2024-03-20  8:24         ` Krzysztof Kozlowski
2024-03-20  8:40           ` Johan Hovold [this message]
2024-03-20  9:16             ` Krzysztof Kozlowski
2024-03-20  9:52               ` Johan Hovold

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=ZfqhCKoEL4XGRs7T@hovoldconsulting.com \
    --to=johan@kernel.org \
    --cc=andersson@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=johan+linaro@kernel.org \
    --cc=konrad.dybcio@linaro.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=kw@linux.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=manivannan.sadhasivam@linaro.org \
    --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).