From: jason@lakedaemon.net (Jason Cooper)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv1 0/5] Marvell EBU irqchip improvements
Date: Wed, 10 Apr 2013 14:57:57 -0400 [thread overview]
Message-ID: <20130410185757.GF28693@titan.lakedaemon.net> (raw)
In-Reply-To: <20130410205102.0c7d3b53@skate>
Thomas (both),
On Wed, Apr 10, 2013 at 08:51:02PM +0200, Thomas Petazzoni wrote:
> On Wed, 10 Apr 2013 15:30:25 -0300, Ezequiel Garcia wrote:
>
> > Indeed it applies cleanly on v3.9-rc6, thank you. On my AXP and A370
> > boards:
> >
> > Tested-by: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
>
> Thanks for your testing!
>
> Thomas (tglx), are you ok with the drivers/irqchip/ changes?
Would it be alright if we took this series through arm-soc with your
Ack? Unfortunately, I see no way to reorder it or split it up to
prevent cross tree dependencies. Conflicts on your side should be
trivial.
thx,
Jason.
next prev parent reply other threads:[~2013-04-10 18:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 21:26 [PATCHv1 0/5] Marvell EBU irqchip improvements Thomas Petazzoni
2013-04-09 21:26 ` [PATCHv1 1/5] ARM: mvebu: move L2 cache initialization in init_early() Thomas Petazzoni
2013-04-09 21:26 ` [PATCHv1 2/5] irqchip: move IRQ driver for Armada 370/XP Thomas Petazzoni
2013-04-09 21:26 ` [PATCHv1 3/5] irqchip: armada-370-xp: move IRQ handler to avoid forward declaration Thomas Petazzoni
2013-04-09 21:26 ` [PATCHv1 4/5] irqchip: armada-370-xp: slightly cleanup irq controller driver Thomas Petazzoni
2013-04-09 21:26 ` [PATCHv1 5/5] ARM: mvebu: do not duplicate the mpic alias Thomas Petazzoni
2013-04-10 13:09 ` [PATCHv1 0/5] Marvell EBU irqchip improvements Ezequiel Garcia
2013-04-10 17:21 ` Thomas Petazzoni
2013-04-10 18:30 ` Ezequiel Garcia
2013-04-10 18:51 ` Thomas Petazzoni
2013-04-10 18:57 ` Jason Cooper [this message]
2013-04-15 19:48 ` Jason Cooper
2013-05-13 15:59 ` Jason Cooper
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=20130410185757.GF28693@titan.lakedaemon.net \
--to=jason@lakedaemon.net \
--cc=linux-arm-kernel@lists.infradead.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).