From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv1 0/5] Marvell EBU irqchip improvements
Date: Wed, 10 Apr 2013 19:21:06 +0200 [thread overview]
Message-ID: <20130410192106.73d81f2c@skate> (raw)
In-Reply-To: <20130410130902.GA29100@localhost>
Dear Ezequiel Garcia,
On Wed, 10 Apr 2013 10:09:03 -0300, Ezequiel Garcia wrote:
> I'm trying to test this patchset, assuming you've based it on top of
> v3.9-rc5.
>
> However, patch 4/5 doesn't apply and I'm not really sure which
> other patches may be depending on this.
>
> Any hints?
The patch set is based on 3.9-rc6, with no other dependencies. However,
since a patch has been applied on the mvebu IRQ controller driver
between 3.9-rc5 and 3.9-rc6, it probably explains the fact that the
patch set doesn't apply as is on 3.9-rc5.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-04-10 17:21 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 [this message]
2013-04-10 18:30 ` Ezequiel Garcia
2013-04-10 18:51 ` Thomas Petazzoni
2013-04-10 18:57 ` Jason Cooper
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=20130410192106.73d81f2c@skate \
--to=thomas.petazzoni@free-electrons.com \
--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).