From: Marc Zyngier <maz@kernel.org>
To: Alexandre Torgue <alexandre.torgue@foss.st.com>
Cc: <arnd@arndb.de>, <robh+dt@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>,
<linux-stm32@st-md-mailman.stormreply.com>,
<linux-kernel@vger.kernel.org>, Marek Vasut <marex@denx.de>,
<jagan@amarulasolutions.com>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Marcin Sloniewski <marcin.sloniewski@gmail.com>,
Ahmad Fatoum <a.fatoum@pengutronix.de>
Subject: Re: [PATCH 0/2] ARM: dts: stm32: Correct masks for GIC PPI interrupts on stm32mp
Date: Mon, 21 Feb 2022 16:16:05 +0000 [thread overview]
Message-ID: <878ru442m2.wl-maz@kernel.org> (raw)
In-Reply-To: <20220221133750.20297-1-alexandre.torgue@foss.st.com>
On Mon, 21 Feb 2022 13:37:48 +0000,
Alexandre Torgue <alexandre.torgue@foss.st.com> wrote:
>
> Using GIC_CPU_MASK_SIMPLE(x), x should reflect the number of CPUs.
>
> regards
> alex
>
> Alexandre Torgue (2):
> ARM: dts: stm32: Correct masks for GIC PPI interrupts on stm32mp13
> ARM: dts: stm32: Correct masks for GIC PPI interrupts on stm32mp15
>
> arch/arm/boot/dts/stm32mp131.dtsi | 8 ++++----
> arch/arm/boot/dts/stm32mp151.dtsi | 8 ++++----
> arch/arm/boot/dts/stm32mp153.dtsi | 7 +++++++
> 3 files changed, 15 insertions(+), 8 deletions(-)
FWIW:
Acked-by: Marc Zyngier <maz@kernel.org>
M.
--
Without deviation from the norm, progress is not possible.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-02-21 16:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-21 13:37 [PATCH 0/2] ARM: dts: stm32: Correct masks for GIC PPI interrupts on stm32mp Alexandre Torgue
2022-02-21 13:37 ` [PATCH 1/2] ARM: dts: stm32: Correct masks for GIC PPI interrupts on stm32mp13 Alexandre Torgue
2022-02-21 13:37 ` [PATCH 2/2] ARM: dts: stm32: Correct masks for GIC PPI interrupts on stm32mp15 Alexandre Torgue
2022-02-21 16:16 ` Marc Zyngier [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=878ru442m2.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=a.fatoum@pengutronix.de \
--cc=alexandre.torgue@foss.st.com \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=jagan@amarulasolutions.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=manivannan.sadhasivam@linaro.org \
--cc=marcin.sloniewski@gmail.com \
--cc=marex@denx.de \
--cc=robh+dt@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 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).