From: Olof Johansson <olof@lixom.net>
To: Daniel Palmer <daniel@0x0f.com>
Cc: soc@kernel.org, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, mark-pk.tsai@mediatek.com,
arnd@arndb.de, maz@kernel.org
Subject: Re: [PATCH v2 0/5] ARM: mstar: wire up interrupt controllers
Date: Sat, 3 Oct 2020 12:48:51 -0700 [thread overview]
Message-ID: <20201003194851.GG8203@lx2k> (raw)
In-Reply-To: <20201002133418.2250277-1-daniel@0x0f.com>
On Fri, Oct 02, 2020 at 10:34:13PM +0900, Daniel Palmer wrote:
> Mark-PK Tsai's driver for the MStar interrupt
> controller should be going into 5.10[0].
>
> This small series selects the driver when building
> support for MStar/SigmaStar Arm v7 SoCs, adds the
> instances of it to the base dtsi and wires up the
> interrupt for pm_uart.
>
> Differences from v1:
>
> - Added two extra commits that fix up the file names
> for the MStar dtsi/dts files as requested by Arnd.
>
> Daniel Palmer (5):
> ARM: mstar: Select MStar intc
> ARM: mstar: Add interrupt controller to base dtsi
> ARM: mstar: Add interrupt to pm_uart
> ARM: mstar: Add mstar prefix to all of the dtsi/dts files
> ARM: mstar: Fix up the fallout from moving the dts/dtsi files
Thanks, applied to arm/soc (patch 1), and arm/dt for the rest.
-Olof
prev parent reply other threads:[~2020-10-03 20:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-02 13:34 [PATCH v2 0/5] ARM: mstar: wire up interrupt controllers Daniel Palmer
2020-10-02 13:34 ` [PATCH v2 1/5] ARM: mstar: Select MStar intc Daniel Palmer
2020-10-02 13:34 ` [PATCH v2 2/5] ARM: mstar: Add interrupt controller to base dtsi Daniel Palmer
2020-10-02 13:34 ` [PATCH v2 3/5] ARM: mstar: Add interrupt to pm_uart Daniel Palmer
2020-10-02 13:34 ` [PATCH v2 4/5] ARM: mstar: Add mstar prefix to all of the dtsi/dts files Daniel Palmer
2020-10-02 13:34 ` [PATCH v2 5/5] ARM: mstar: Fix up the fallout from moving the dts/dtsi files Daniel Palmer
2020-10-03 19:48 ` Olof Johansson [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=20201003194851.GG8203@lx2k \
--to=olof@lixom.net \
--cc=arnd@arndb.de \
--cc=daniel@0x0f.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark-pk.tsai@mediatek.com \
--cc=maz@kernel.org \
--cc=soc@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).