From: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>
To: Joel Stanley <joel@jms.id.au>
Cc: "Jonathan Neuschäfer" <j.neuschaefer@gmx.net>,
"Linux ARM" <linux-arm-kernel@lists.infradead.org>,
"Tomer Maimon" <tmaimon77@gmail.com>,
"Avi Fishman" <avifishman70@gmail.com>,
"Patrick Venture" <venture@google.com>,
"OpenBMC Maillist" <openbmc@lists.ozlabs.org>,
"Tali Perry" <tali.perry1@gmail.com>,
"Russell King" <linux@armlinux.org.uk>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Benjamin Fair" <benjaminfair@google.com>
Subject: Re: [PATCH] ARM: npcm: wpcm450: select interrupt controller driver
Date: Tue, 18 May 2021 11:37:00 +0200 [thread overview]
Message-ID: <YKOKvAyu6/9Kw9DP@latitude> (raw)
In-Reply-To: <CACPK8XdVNfjbs+KmhT8g899d74t7M8b6iBuGC_3=DEBy+A_VHg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 616 bytes --]
On Tue, May 18, 2021 at 07:12:40AM +0000, Joel Stanley wrote:
> On Thu, 13 May 2021 at 16:57, Jonathan Neuschäfer <j.neuschaefer@gmx.net> wrote:
> >
> > The interrupt controller driver is necessary in order to have a
> > functioning Linux system on WPCM450. Select it in mach-npcm/Kconfig.
> >
> > Signed-off-by: Jonathan Neuschäfer <j.neuschaefer@gmx.net>
>
> Fixes: ece3fe93e8f4 ("ARM: npcm: Introduce Nuvoton WPCM450 SoC")
Ah, right, the fixes tag makes sense.
> Reviewed-by: Joel Stanley <joel@jms.id.au>
>
> I will send this to the soc maintainers to apply as a fix.
Thanks!
Jonathan
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
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:[~2021-05-18 9:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-13 16:56 [PATCH] ARM: npcm: wpcm450: select interrupt controller driver Jonathan Neuschäfer
2021-05-18 7:12 ` Joel Stanley
2021-05-18 9:37 ` Jonathan Neuschäfer [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=YKOKvAyu6/9Kw9DP@latitude \
--to=j.neuschaefer@gmx.net \
--cc=avifishman70@gmail.com \
--cc=benjaminfair@google.com \
--cc=joel@jms.id.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=openbmc@lists.ozlabs.org \
--cc=tali.perry1@gmail.com \
--cc=tmaimon77@gmail.com \
--cc=venture@google.com \
/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