From: Ralf Baechle <ralf@linux-mips.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Alexander Couzens <lynxis@fe80.eu>,
linux-mips@linux-mips.org, Alban Bedel <albeu@free.fr>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
devicetree@vger.kernel.org, Jason Cooper <jason@lakedaemon.net>,
Marc Zyngier <marc.zyngier@arm.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] MIPS: ath79: add irq chip ar7240-misc-intc
Date: Tue, 22 Sep 2015 19:12:29 +0200 [thread overview]
Message-ID: <20150922171228.GB18064@linux-mips.org> (raw)
In-Reply-To: <alpine.DEB.2.11.1509221223280.5606@nanos>
On Tue, Sep 22, 2015 at 12:24:26PM +0200, Thomas Gleixner wrote:
> > The ar7240 misc irq chip use ack handler
> > instead of ack_mask handler. All new ath79 chips use
> > the ar7240 misc irq chip
> >
> > Signed-off-by: Alexander Couzens <lynxis@fe80.eu>
> > Acked-by: Alban Bedel <albeu@free.fr>
> > ---
> > .../interrupt-controller/qca,ath79-misc-intc.txt | 20 ++++++++++++++++++--
> > arch/mips/ath79/irq.c | 10 ++++++++++
>
> That driver should probably move into drivers/irqchip.
Like a fair number of other irq.c type files in arch/mips that could
reasonably easily be rewritten to go to drivers/irqchip.
> Other than that.
>
> Acked-by: Thomas Gleixner <tglx@linutronix.de>
Thanks, I replaced the previous version of this patch with this one.
Ralf
next prev parent reply other threads:[~2015-09-22 17:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-19 4:26 [PATCH 0/2] v3 ath79 misc irq controller Alexander Couzens
[not found] ` <1442636780-2891-1-git-send-email-lynxis-qyMx1GtpvWw@public.gmane.org>
2015-09-19 4:26 ` [PATCH 1/2] MIPS: ath79: set missing irq ack handler for ar7100-misc-intc irq chip Alexander Couzens
2015-09-22 10:23 ` Thomas Gleixner
2015-09-22 17:09 ` Ralf Baechle
2015-09-19 4:26 ` [PATCH 2/2] MIPS: ath79: add irq chip ar7240-misc-intc Alexander Couzens
2015-09-22 10:24 ` Thomas Gleixner
2015-09-22 17:12 ` Ralf Baechle [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-09-03 3:34 [PATCH 0/2] ath79 misc irq controller Alexander Couzens
[not found] ` <1441251262-13335-1-git-send-email-lynxis-qyMx1GtpvWw@public.gmane.org>
2015-09-03 3:34 ` [PATCH 2/2] MIPS: ath79: add irq chip ar7240-misc-intc Alexander Couzens
[not found] ` <1441251262-13335-3-git-send-email-lynxis-qyMx1GtpvWw@public.gmane.org>
2015-09-03 8:34 ` Alban
2015-09-03 10:23 ` Mark Rutland
2015-08-06 10:43 [PATCH 1/2] MIPS: ath79: set irq ACK handler for ar7100-misc-intc irq chip Alexander Couzens
2015-08-06 10:43 ` [PATCH 2/2] MIPS: ath79: add irq chip ar7240-misc-intc Alexander Couzens
[not found] ` <1438857805-18443-2-git-send-email-lynxis-qyMx1GtpvWw@public.gmane.org>
2015-08-10 18:22 ` Alban
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=20150922171228.GB18064@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=albeu@free.fr \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jason@lakedaemon.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=lynxis@fe80.eu \
--cc=marc.zyngier@arm.com \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@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;
as well as URLs for NNTP newsgroup(s).