From: Rob Herring <robh@kernel.org>
To: Benjamin Gaignard <benjamin.gaignard@st.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
jason@lakedaemon.net, marc.zyngier@arm.com,
linux-kernel@vger.kernel.org, robh+dt@kernel.org,
Benjamin Gaignard <benjamin.gaignard@st.com>,
tglx@linutronix.de, linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org, alexandre.torgue@st.com
Subject: Re: [PATCH v3 1/3] dt-bindings: interrupt-controller: stm32: Document hwlock properties
Date: Tue, 18 Dec 2018 09:06:17 -0600 [thread overview]
Message-ID: <20181218150617.GA26851@bogus> (raw)
In-Reply-To: <20181217142215.17493-2-benjamin.gaignard@st.com>
On Mon, 17 Dec 2018 15:22:13 +0100, Benjamin Gaignard wrote:
> Add hwlocks as optional property
>
> Signed-off-by: Benjamin Gaignard <benjamin.gaignard@st.com>
> ---
> .../devicetree/bindings/interrupt-controller/st,stm32-exti.txt | 4 ++++
> 1 file changed, 4 insertions(+)
>
Reviewed-by: Rob Herring <robh@kernel.org>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2018-12-18 15:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-17 14:22 [PATCH v3 0/3] Make STM32 interrupt controller use hwspinlock Benjamin Gaignard
2018-12-17 14:22 ` [PATCH v3 1/3] dt-bindings: interrupt-controller: stm32: Document hwlock properties Benjamin Gaignard
2018-12-18 15:06 ` Rob Herring [this message]
2018-12-17 14:22 ` [PATCH v3 2/3] irqchip: stm32: protect configuration registers with hwspinlock Benjamin Gaignard
2018-12-17 14:22 ` [PATCH v3 3/3] ARM: dts: stm32: Add hwlock for irqchip on stm32mp157 Benjamin Gaignard
2018-12-29 18:30 ` kbuild test robot
2018-12-18 15:39 ` [PATCH v3 0/3] Make STM32 interrupt controller use hwspinlock Marc Zyngier
2018-12-19 15:00 ` 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=20181218150617.GA26851@bogus \
--to=robh@kernel.org \
--cc=alexandre.torgue@st.com \
--cc=benjamin.gaignard@st.com \
--cc=devicetree@vger.kernel.org \
--cc=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--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