From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Marc Zyngier <maz@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/2] irqchip: Add support for IDT 79rc3243x interrupt controller
Date: Thu, 22 Apr 2021 19:15:54 +0200 [thread overview]
Message-ID: <20210422171554.GA14257@alpha.franken.de> (raw)
In-Reply-To: <87mttqicj4.wl-maz@kernel.org>
On Thu, Apr 22, 2021 at 04:06:55PM +0100, Marc Zyngier wrote:
> On Thu, 22 Apr 2021 15:53:28 +0100,
> Thomas Bogendoerfer <tsbogend@alpha.franken.de> wrote:
> >
> > IDT 79rc3243x SoCs have rather simple interrupt controllers connected
> > to the MIPS CPU interrupt lines. Each of them has room for up to
> > 32 interrupts.
> >
> > Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
> > ---
> > Changes in v4:
> > - changed comaptible string to idt,32434-pic
>
> I have dropped v3 from irq/irqchip-next and picked v4, but please send
thanks
> patches on top of that version if you have further changes.
sure will do.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2021-04-22 17:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 14:53 [PATCH v4 1/2] irqchip: Add support for IDT 79rc3243x interrupt controller Thomas Bogendoerfer
2021-04-22 14:53 ` [PATCH v4 2/2] dt-bindings: interrupt-controller: Add IDT 79RC3243x Interrupt Controller Thomas Bogendoerfer
2021-04-22 15:07 ` [irqchip: irq/irqchip-next] " irqchip-bot for Thomas Bogendoerfer
2021-04-22 18:23 ` [PATCH v4 2/2] " Rob Herring
2021-04-27 21:57 ` Rob Herring
2021-04-22 15:06 ` [PATCH v4 1/2] irqchip: Add support for IDT 79rc3243x interrupt controller Marc Zyngier
2021-04-22 17:15 ` Thomas Bogendoerfer [this message]
2021-04-22 15:07 ` [irqchip: irq/irqchip-next] " irqchip-bot for Thomas Bogendoerfer
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=20210422171554.GA14257@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.