From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: neil.armstrong@linaro.org, Thomas Gleixner <tglx@linutronix.de>,
Marc Zyngier <marc.zyngier@arm.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>
Cc: Heiner Kallweit <hkallweit1@gmail.com>,
Kevin Hilman <khilman@baylibre.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
"open list:ARM/Amlogic Meson..."
<linux-amlogic@lists.infradead.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH v2] dt-bindings: interrupt-controller: Convert Amlogic Meson GPIO interrupt controller binding
Date: Tue, 20 Jun 2023 09:36:38 +0200 [thread overview]
Message-ID: <a895bdba-a48e-17e9-043e-9b950bbc1a85@linaro.org> (raw)
In-Reply-To: <777cf5df-6358-fa46-66cd-153d29763f77@linaro.org>
On 20/06/2023 09:33, Neil Armstrong wrote:
> Hi,
>
> On 12/03/2023 22:29, Heiner Kallweit wrote:
>> Convert Amlogic Meson GPIO interrupt controller binding to yaml.
>>
>> Reviewed-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com>
>> Reviewed-by: Rob Herring <robh@kernel.org>
>> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
>> ---
>> - consider that more than one compatible may be set
>> - remove bus part from example
>> - remove minItem/maxItem properties for compatible
>> - reduce compatible fallback complexity
>> - add that 8 or 12 GIC interrupts can be used
>> - fix typo
>> ---
>> .../amlogic,meson-gpio-intc.txt | 38 ----------
>> .../amlogic,meson-gpio-intc.yaml | 72 +++++++++++++++++++
>> 2 files changed, 72 insertions(+), 38 deletions(-)
>> delete mode 100644 Documentation/devicetree/bindings/interrupt-controller/amlogic,meson-gpio-intc.txt
>> create mode 100644 Documentation/devicetree/bindings/interrupt-controller/amlogic,meson-gpio-intc.yaml
>
> Gentle ping, this patch is fully reviewed and is lying on the list for the last 3 months.
Maybe just take it through your Amlogic SoC tree in such case? It's less
preferred than subsystem, but still what matters is to get this merged.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-06-20 7:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-12 21:29 [PATCH v2] dt-bindings: interrupt-controller: Convert Amlogic Meson GPIO interrupt controller binding Heiner Kallweit
2023-03-30 5:53 ` Heiner Kallweit
2023-06-20 7:33 ` Neil Armstrong
2023-06-20 7:36 ` Krzysztof Kozlowski [this message]
2023-06-20 7:41 ` neil.armstrong
2023-06-22 7:57 ` Neil Armstrong
-- strict thread matches above, loose matches on Subject: below --
2023-01-23 21:22 [PATCH 0/8] soc: amlogic: switch bindings to yaml and adjust some dtbs's Heiner Kallweit
2023-01-27 21:14 ` [PATCH v2] dt-bindings: interrupt-controller: Convert Amlogic Meson GPIO interrupt controller binding Heiner Kallweit
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=a895bdba-a48e-17e9-043e-9b950bbc1a85@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=hkallweit1@gmail.com \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=marc.zyngier@arm.com \
--cc=martin.blumenstingl@googlemail.com \
--cc=neil.armstrong@linaro.org \
--cc=robh+dt@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 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).