public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Alexandre Torgue <alexandre.torgue@foss.st.com>
Cc: Rob Herring <robh+dt@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Marc Zyngier <maz@kernel.org>,
	devicetree@vger.kernel.org,
	linux-stm32@st-md-mailman.stormreply.com,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 1/3] dt-bindings: interrupt-controller: stm32-exti: document st,stm32mp13-exti
Date: Mon, 7 Feb 2022 15:45:17 -0600	[thread overview]
Message-ID: <YgGS7YkSl+hGKx/1@robh.at.kernel.org> (raw)
In-Reply-To: <20220202140005.860-2-alexandre.torgue@foss.st.com>

On Wed, 02 Feb 2022 15:00:03 +0100, Alexandre Torgue wrote:
> Support of STM32MP13 SoC implies to create a new compatible in order to
> manage EXTI/GIC mapping changes.
> 
> Signed-off-by: Alexandre Torgue <alexandre.torgue@foss.st.com>
> 

Acked-by: Rob Herring <robh@kernel.org>

  reply	other threads:[~2022-02-07 21:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-02 14:00 [PATCH v3 0/3] Add STM32MP13 EXTI support Alexandre Torgue
2022-02-02 14:00 ` [PATCH v3 1/3] dt-bindings: interrupt-controller: stm32-exti: document st,stm32mp13-exti Alexandre Torgue
2022-02-07 21:45   ` Rob Herring [this message]
2022-02-09 16:17   ` [irqchip: irq/irqchip-next] " irqchip-bot for Alexandre Torgue
2022-02-02 14:00 ` [PATCH v3 2/3] irqchip/stm32-exti: add STM32MP13 support Alexandre Torgue
2022-02-09 16:17   ` [irqchip: irq/irqchip-next] irqchip/stm32-exti: Add " irqchip-bot for Alexandre Torgue
2022-02-02 14:00 ` [PATCH v3 3/3] ARM: dts: stm32: Enable EXTI on stm32mp13 Alexandre Torgue
2022-02-09 16:17   ` [irqchip: irq/irqchip-next] " irqchip-bot for Alexandre Torgue

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=YgGS7YkSl+hGKx/1@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=alexandre.torgue@foss.st.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-stm32@st-md-mailman.stormreply.com \
    --cc=maz@kernel.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