linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Johan Hovold <johan@kernel.org>
Cc: "Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>,
	"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
	"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
	"Manivannan Sadhasivam" <mani@kernel.org>,
	"Bjorn Helgaas" <bhelgaas@google.com>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	"Conor Dooley" <conor+dt@kernel.org>,
	"Bjorn Andersson" <andersson@kernel.org>,
	"Abel Vesa" <abel.vesa@linaro.org>,
	linux-arm-msm@vger.kernel.org, linux-pci@vger.kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH 9/9] dt-bindings: PCI: qcom,pcie-x1e80100: Add missing required power-domains
Date: Thu, 30 Oct 2025 13:08:27 -0500	[thread overview]
Message-ID: <20251030180827.GA110725-robh@kernel.org> (raw)
In-Reply-To: <aQJE5kkOGh76dLvf@hovoldconsulting.com>

On Wed, Oct 29, 2025 at 05:46:30PM +0100, Johan Hovold wrote:
> On Wed, Oct 29, 2025 at 04:40:46PM +0100, Krzysztof Kozlowski wrote:
> > Power domains should be required for PCI, so the proper SoC supplies are
> > turned on.
> > 
> > Cc: <stable@vger.kernel.org>
> 
> I have a feeling I've pointed this out before, but these kind of binding
> patches really does not seem to qualify for stable backporting (e.g.
> does not "fix a real bug that bothers people").

Presumably if someone omits power-domain and the driver doesn't work, 
then it's a bug affecting them.

I'm fine with dropping the stable tag because it will still most likely 
get picked up with the Fixes tag. :)

Rob
 

  parent reply	other threads:[~2025-10-30 18:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-29 15:40 [PATCH 0/9] dt-bindings: PCI: qcom: Add missing required power-domains Krzysztof Kozlowski
2025-10-29 15:40 ` [PATCH 1/9] dt-bindings: PCI: qcom,pcie-sa8775p: " Krzysztof Kozlowski
2025-10-30  8:41   ` Krzysztof Kozlowski
2025-10-29 15:40 ` [PATCH 2/9] dt-bindings: PCI: qcom,pcie-sc7280: " Krzysztof Kozlowski
2025-10-29 15:40 ` [PATCH 3/9] dt-bindings: PCI: qcom,pcie-sc8280xp: " Krzysztof Kozlowski
2025-10-29 15:40 ` [PATCH 4/9] dt-bindings: PCI: qcom,pcie-sm8150: " Krzysztof Kozlowski
2025-10-29 15:40 ` [PATCH 5/9] dt-bindings: PCI: qcom,pcie-sm8250: " Krzysztof Kozlowski
2025-10-29 15:40 ` [PATCH 6/9] dt-bindings: PCI: qcom,pcie-sm8350: " Krzysztof Kozlowski
2025-10-29 15:40 ` [PATCH 7/9] dt-bindings: PCI: qcom,pcie-sm8450: " Krzysztof Kozlowski
2025-10-29 15:40 ` [PATCH 8/9] dt-bindings: PCI: qcom,pcie-sm8550: " Krzysztof Kozlowski
2025-10-29 15:40 ` [PATCH 9/9] dt-bindings: PCI: qcom,pcie-x1e80100: " Krzysztof Kozlowski
2025-10-29 16:46   ` Johan Hovold
2025-10-30  8:16     ` Krzysztof Kozlowski
2025-10-30 18:08     ` Rob Herring [this message]
2025-10-31 14:04       ` 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=20251030180827.GA110725-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=abel.vesa@linaro.org \
    --cc=andersson@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=johan@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=kwilczynski@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=mani@kernel.org \
    --cc=stable@vger.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).