From: tglx@linutronix.de (Thomas Gleixner)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/6] Marvell Orion SoC irqchip and clocksource
Date: Tue, 11 Jun 2013 10:45:40 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.02.1306111043200.22970@ionos> (raw)
In-Reply-To: <1370536034-23956-1-git-send-email-sebastian.hesselbarth@gmail.com>
On Thu, 6 Jun 2013, Sebastian Hesselbarth wrote:
> This patch set introduces DT-aware irqchip and clocksource drivers for
> Marvell Orion SoCs (Kirkwood, Dove, Orion5x, MV78x00) and corresponding
> patches for Dove and Kirkwood to enable them for DT-boards.
>
> The irqchip driver, of course, depends on Thomas Gleixner's work on
> irqdomain support for generic chip (tip irq/core).
>
> The ARM part of this patch set has a quite ridiculuous dependency havoc
> of mv643xx_eth DT support (current net-next) that will add to both irqchip
> and clocksource branches respectively. Therefore, I suggest that irq
> and clocksource maintainers take in the mere drivers (Patches 1+2) and
> Jason Cooper handles the remaining patches when all three drivers have
> surfaced on mainline linux.
I provided a tip branch irq/for-arm, which contains only these changes
and can be pulled by SoC/subarch maintainers so we don't end up with a
dependency nightmare. Just mention that you pulled it from me when
sending the pull request to Linus.
Thanks,
tglx
next prev parent reply other threads:[~2013-06-11 8:45 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 16:27 [PATCH 0/6] Marvell Orion SoC irqchip and clocksource Sebastian Hesselbarth
2013-06-06 16:27 ` [PATCH v3 1/6] irqchip: add support for Marvell Orion SoCs Sebastian Hesselbarth
2013-06-11 8:46 ` Thomas Gleixner
2013-06-11 13:30 ` Thomas Gleixner
2013-06-11 13:37 ` Sebastian Hesselbarth
2013-06-11 13:45 ` Thomas Gleixner
2013-06-11 14:08 ` Sebastian Hesselbarth
2013-06-11 14:13 ` Thomas Gleixner
2013-06-11 14:17 ` Sebastian Hesselbarth
2013-06-11 13:48 ` Grant Likely
2013-06-06 16:27 ` [PATCH v3 2/6] clocksource: add Marvell Orion SoC timer Sebastian Hesselbarth
2013-06-07 22:03 ` Daniel Lezcano
2013-06-06 16:27 ` [PATCH v3 3/6] ARM: dove: move device tree nodes to DT irqchip and clocksource Sebastian Hesselbarth
2013-06-06 16:27 ` [PATCH v3 4/6] ARM: kirkwood: " Sebastian Hesselbarth
2013-06-07 8:30 ` Thomas Petazzoni
2013-06-07 9:15 ` Sebastian Hesselbarth
2013-06-07 11:51 ` Sebastian Hesselbarth
2013-06-06 16:27 ` [PATCH v3 5/6] ARM: dove: convert " Sebastian Hesselbarth
2013-06-06 16:27 ` [PATCH v3 6/6] ARM: kirkwood: " Sebastian Hesselbarth
2013-06-06 16:47 ` [PATCH 0/6] Marvell Orion SoC " Jason Gunthorpe
2013-06-06 17:13 ` Jason Cooper
2013-06-10 9:35 ` [PATCH v4 2/6] clocksource: add Marvell Orion SoC timer Sebastian Hesselbarth
2013-06-10 16:04 ` Daniel Lezcano
2013-06-10 16:31 ` Sebastian Hesselbarth
2013-06-10 16:44 ` Daniel Lezcano
2013-06-10 16:47 ` Sebastian Hesselbarth
2013-06-10 17:06 ` Daniel Lezcano
2013-06-10 17:09 ` Jason Cooper
2013-06-10 17:21 ` Daniel Lezcano
2013-06-10 17:25 ` Andrew Lunn
2013-06-11 8:45 ` Thomas Gleixner [this message]
2013-06-11 12:35 ` [PATCH 0/6] Marvell Orion SoC irqchip and clocksource Ezequiel Garcia
2013-06-11 12:41 ` Sebastian Hesselbarth
2013-06-11 13:13 ` Thomas Gleixner
2013-06-11 13:14 ` Sebastian Hesselbarth
2013-06-11 15:27 ` 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=alpine.LFD.2.02.1306111043200.22970@ionos \
--to=tglx@linutronix.de \
--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).