From: Thomas Gleixner <tglx@kernel.org>
To: Maulik Shah <maulik.shah@oss.qualcomm.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
Maulik Shah <maulik.shah@oss.qualcomm.com>
Subject: Re: [PATCH v2 3/3] irqchip/qcom-pdc: Add puwra compatible for PDC secondary mode
Date: Wed, 17 Jun 2026 18:32:44 +0200 [thread overview]
Message-ID: <87mrwtcekz.ffs@fw13> (raw)
In-Reply-To: <20260616-purwa-pdc-v2-3-8dda7ef25ce5@oss.qualcomm.com>
On Tue, Jun 16 2026 at 15:57, Maulik Shah wrote:
> --- a/drivers/irqchip/qcom-pdc.c
> +++ b/drivers/irqchip/qcom-pdc.c
> @@ -704,7 +704,10 @@ static int qcom_pdc_probe(struct platform_device *pdev, struct device_node *pare
> }
>
> pdc->x1e_quirk = true;
> + }
>
> + if (of_device_is_compatible(node, "qcom,x1e80100-pdc") ||
> + of_device_is_compatible(node, "qcom,x1p42100-pdc")) {
> if (!qcom_scm_is_available())
> return -EPROBE_DEFER;
Bah. Can you please prominently tell in the cover letter that the series
has dependencies on some other series instead of hiding that information
in a lump of sha1 references which do not exist for me?
prev parent reply other threads:[~2026-06-17 16:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-16 10:27 [PATCH v2 0/3] purwa: Drop the Hamoa PDC workaround from purwa Maulik Shah
2026-06-16 10:27 ` [PATCH v2 1/3] dt-bindings: interrupt-controller: qcom,pdc: Document Purwa PDC Maulik Shah
2026-06-16 14:09 ` Konrad Dybcio
2026-06-17 8:14 ` Krzysztof Kozlowski
2026-06-16 10:27 ` [PATCH v2 2/3] arm64: dts: qcom: purwa: Drop the Hamoa workaround for PDC Maulik Shah
2026-06-16 14:09 ` Konrad Dybcio
2026-06-16 10:27 ` [PATCH v2 3/3] irqchip/qcom-pdc: Add puwra compatible for PDC secondary mode Maulik Shah
2026-06-17 16:32 ` Thomas Gleixner [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=87mrwtcekz.ffs@fw13 \
--to=tglx@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maulik.shah@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.