From: Rob Herring <robh@kernel.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: interrupt-controller: qcom,pdc: Add SAR2130P compatible
Date: Fri, 8 Nov 2024 15:13:22 -0600 [thread overview]
Message-ID: <20241108211322.GA2849214-robh@kernel.org> (raw)
In-Reply-To: <t2trcojqskryzbuh6cbuqev35eioduarneskwtcm5aeeqlvbkv@3kj4x36ebkqk>
On Thu, Oct 31, 2024 at 07:34:41PM +0200, Dmitry Baryshkov wrote:
> On Thu, Oct 17, 2024 at 09:13:01PM +0300, Dmitry Baryshkov wrote:
> > Document compatible for PDC interrupt controller on SAR2130P platform.
> >
> > Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> > ---
> > Documentation/devicetree/bindings/interrupt-controller/qcom,pdc.yaml | 1 +
> > 1 file changed, 1 insertion(+)
>
> Gracious ping, the patch has been acked by DT maintainers, but is still
> not present in linux-next and got no other reviews.
Applied.
> Krzysztof mentioned that the patch should be picked up by Bjorn, but all
> previous patches for PDC schema were picked up by Rob Herring or by Marc
> Zyngier (and one stray patch was picked up by Linus Walleij).
My preference is for it to be applied with the driver or dts changes.
For standalone patches, I only pick them up if the $subsystem maintainer
does not.
Rob
next prev parent reply other threads:[~2024-11-08 21:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 18:13 [PATCH] dt-bindings: interrupt-controller: qcom,pdc: Add SAR2130P compatible Dmitry Baryshkov
2024-10-18 7:19 ` Krzysztof Kozlowski
2024-10-18 7:20 ` Krzysztof Kozlowski
2024-10-26 15:58 ` Dmitry Baryshkov
2024-10-31 17:34 ` Dmitry Baryshkov
2024-11-08 21:13 ` Rob Herring [this message]
2024-11-08 22:45 ` Dmitry Baryshkov
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=20241108211322.GA2849214-robh@kernel.org \
--to=robh@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
/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.