public inbox for linux-pci@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Manivannan Sadhasivam <mani@kernel.org>,
	Bjorn Helgaas <helgaas@kernel.org>
Cc: Ziyue Zhang <ziyue.zhang@oss.qualcomm.com>,
	andersson@kernel.org, konradybcio@kernel.org, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org, jingoohan1@gmail.com,
	lpieralisi@kernel.org, kwilczynski@kernel.org,
	bhelgaas@google.com, johan+linaro@kernel.org, vkoul@kernel.org,
	kishon@kernel.org, neil.armstrong@linaro.org,
	abel.vesa@linaro.org, kw@linux.com,
	linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
	linux-phy@lists.infradead.org, qiang.yu@oss.qualcomm.com,
	quic_krichai@quicinc.com, quic_vbadigan@quicinc.com
Subject: Re: [PATCH v1 1/1] arm64: dts: qcom: hamoa: Move PCIe PERST and Wake GPIOs to port nodes
Date: Thu, 19 Mar 2026 14:12:03 +0100	[thread overview]
Message-ID: <42f4a7a9-44db-4132-86a5-b9b8ee74119d@kernel.org> (raw)
In-Reply-To: <f5vqy4tfhfxeu4li33qffjzrlgqgbflidds35qdni3trdoues2@kvuzjxenrdff>

On 19/03/2026 06:28, Manivannan Sadhasivam wrote:
>>  If it only affects developers who generated DTs based
>> on 960609b22be5 for internal testing, we should say that so it's clear
>> that no end users will see any regressions or boot failures.
>>
> 
> Whoever have included commit 960609b22be5 in their kernel and using the above
> mentioned machines will see the failure. But looks like no one really tested
> v7.0-rcS on these machines as we haven't gotten any reports so far.
> 
>> Is there some way to verify that after this patch, none of the
>> generated DTBs are in this half-baked situation?  Some kind of
>> automated DTB checker?
> 
> I sent out a DT binding series [1] that was supposed to catch these issues
> during DTB validation phase, but unfortunately it got stuck in the review. I'll
> try to stir things up.
> 

What about other projects which use this DTB directly (e.g. OpenBSD)?
Are they considered broken with 960609b22be5?

Best regards,
Krzysztof

  reply	other threads:[~2026-03-19 13:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-13  9:46 [PATCH v1 1/1] arm64: dts: qcom: hamoa: Move PCIe PERST and Wake GPIOs to port nodes Ziyue Zhang
2026-03-13 16:45 ` Bjorn Helgaas
2026-03-14 14:20   ` Manivannan Sadhasivam
2026-03-16  2:53     ` Bjorn Andersson
2026-03-16  3:20       ` Manivannan Sadhasivam
2026-03-19  2:42         ` Bjorn Andersson
2026-03-19  5:39           ` Manivannan Sadhasivam
2026-03-19 13:50             ` Tobias Heider
2026-03-24  6:07               ` Manivannan Sadhasivam
2026-03-24 19:14                 ` Tobias Heider
2026-03-27 14:17                   ` Bjorn Helgaas
2026-03-27 16:02                     ` Manivannan Sadhasivam
2026-03-17 17:13     ` Bjorn Helgaas
2026-03-19  5:28       ` Manivannan Sadhasivam
2026-03-19 13:12         ` Krzysztof Kozlowski [this message]
2026-03-19 17:17         ` Bjorn Helgaas
2026-03-24  5:59           ` Manivannan Sadhasivam
2026-03-16 11:16 ` Konrad Dybcio

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=42f4a7a9-44db-4132-86a5-b9b8ee74119d@kernel.org \
    --to=krzk@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=helgaas@kernel.org \
    --cc=jingoohan1@gmail.com \
    --cc=johan+linaro@kernel.org \
    --cc=kishon@kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=kw@linux.com \
    --cc=kwilczynski@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=lpieralisi@kernel.org \
    --cc=mani@kernel.org \
    --cc=neil.armstrong@linaro.org \
    --cc=qiang.yu@oss.qualcomm.com \
    --cc=quic_krichai@quicinc.com \
    --cc=quic_vbadigan@quicinc.com \
    --cc=robh@kernel.org \
    --cc=vkoul@kernel.org \
    --cc=ziyue.zhang@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