From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: genirq: Generic irq chip available in git
Date: Sun, 8 May 2011 14:35:30 +0100 [thread overview]
Message-ID: <20110508133530.GA13815@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20110508082222.GA27807@n2100.arm.linux.org.uk>
On Sun, May 08, 2011 at 09:22:22AM +0100, Russell King - ARM Linux wrote:
> On Wed, Apr 27, 2011 at 10:25:42PM +0100, Russell King - ARM Linux wrote:
> > Thanks, now pulled into the 'consolidation-irq' branch. If people
> > wish to send the per-SoC patches to the patch system, or put them
> > in their git trees, or indeed whatever, that stuff can be merged
> > onto that branch so its easier to see where the IRQ consolidation
> > is at.
> I've had nothing further from anyone on this since merging it. If people
> aren't using this stuff then there's no point it sitting in my tree, and
> there's no point me sending it to mainline as part of my merges.
> So I'm dropping the branch out of the merges for the time being.
Would it not make sense to go ahead and apply all the patches that
maintainers already acked? I rather suspect many people had thought
that Thomas' future pushes of the code would also include the patches
that they'd already approved and haven't realised that they need to
manually push the patches to you.
next prev parent reply other threads:[~2011-05-08 13:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-23 16:37 genirq: Generic irq chip available in git Thomas Gleixner
2011-04-27 21:25 ` Russell King - ARM Linux
2011-05-08 8:22 ` Russell King - ARM Linux
2011-05-08 13:35 ` Mark Brown [this message]
2011-05-08 14:00 ` Russell King - ARM Linux
2011-05-08 14:03 ` Mark Brown
2011-05-11 17:45 ` Nori, Sekhar
2011-05-11 17:55 ` Russell King - ARM Linux
2011-05-11 17:58 ` Mark Brown
2011-05-11 18:03 ` Russell King - ARM Linux
2011-05-16 12:15 ` Tony Lindgren
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=20110508133530.GA13815@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.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).