Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Huqiang Qin <huqiang.qin@amlogic.com>
To: tglx@linutronix.de, maz@kernel.org, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
	neil.armstrong@linaro.org, khilman@baylibre.com,
	jbrunet@baylibre.com, martin.blumenstingl@googlemail.com,
	hkallweit1@gmail.com
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-amlogic@lists.infradead.org
Subject: Re: [PATCH V2 0/2] Add GPIO interrupt support for Amlogic-C3 SoCs
Date: Mon, 14 Aug 2023 15:09:30 +0800	[thread overview]
Message-ID: <d5e1e07a-fd3d-7f7f-6c73-f4334727887e@amlogic.com> (raw)
In-Reply-To: <20230628091533.3884385-1-huqiang.qin@amlogic.com>

Hi Thomas, Marc

Friendly ping.

On 2023/6/28 17:15, Huqiang Qin wrote:
> This patch adds GPIO interrupt support for Amloigc-C3 SoC (C308L and C302X)
> 
> V1 -> V2: Added driver changes
> 
> Huqiang Qin (2):
>   dt-bindings: interrupt-controller: Add support for Amlogic-C3 SoCs
>   irqchip: Add support for Amlogic-C3 SoCs
> 
>  .../interrupt-controller/amlogic,meson-gpio-intc.yaml        | 1 +
>  drivers/irqchip/irq-meson-gpio.c                             | 5 +++++
>  2 files changed, 6 insertions(+)
> 

Best Regards,
Huqiang Qin

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      parent reply	other threads:[~2023-08-14  7:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-28  9:15 [PATCH V2 0/2] Add GPIO interrupt support for Amlogic-C3 SoCs Huqiang Qin
2023-06-28  9:15 ` [PATCH V2 1/2] dt-bindings: interrupt-controller: Add " Huqiang Qin
2023-06-28 17:27   ` Conor Dooley
2023-06-28 20:52   ` Martin Blumenstingl
2023-06-28  9:15 ` [PATCH V2 2/2] irqchip: " Huqiang Qin
2023-06-28 20:52   ` Martin Blumenstingl
2023-08-14  7:09 ` Huqiang Qin [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=d5e1e07a-fd3d-7f7f-6c73-f4334727887e@amlogic.com \
    --to=huqiang.qin@amlogic.com \
    --cc=conor+dt@kernel.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=linux-kernel@vger.kernel.org \
    --cc=martin.blumenstingl@googlemail.com \
    --cc=maz@kernel.org \
    --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