Russell,
On Thu, 5 Dec 2013, Russell King - ARM Linux wrote:
> On Thu, Dec 05, 2013 at 01:41:53AM +0100, Thomas Gleixner wrote:
> > @all who feel responsible for gic_arch_extn
> >
> > On Wed, 4 Dec 2013, Thomas Gleixner wrote:
> > > I'm going to reply in a separate mail on this, because you have
> > > brought this to my attention, but you are not responsible in the first
> > > place for this brainfart.
> >
> > Who came up with that gic_arch_extn concept in the first place?
>
> If you'd spend more time reviewing IRQ patches then maybe you'd catch
> this at review time. So please stop your rediculous whinging when
> most of the problem is your own lack of time.
I'm not a native english speaker, so I want to make sure in the first
place that you meant:
"ridiculous whingeing"
Assumed that you meant that, let me ridicule you a bit.
The gic_arch_extn concept got merged with:
commit d7ed36a4ea84e3a850f9932e2058ceef987d1acd
Author: Santosh Shilimkar <santosh.shilimkar@xxxxxx>
Date: Wed Mar 2 08:03:22 2011 +0100
ARM: 6777/1: gic: Add hooks for architecture specific extensions
<SNIP>
Cc: Russell King <rmk+kernel@xxxxxxxxxxxxxxxx>
Signed-off-by: Santosh Shilimkar <santosh.shilimkar@xxxxxx>
Acked-by: Colin Cross <ccross@xxxxxxxxxxx>
Tested-by: Colin Cross <ccross@xxxxxxxxxxx>
Signed-off-by: Russell King <rmk+kernel@xxxxxxxxxxxxxxxx>
---
arch/arm/common/gic.c | 47 ++++++++++++....
arch/arm/include/asm/hardware/gic.h | 1
The patch in question was never cc'ed to me and you merged it on your
own.
So now you have the chuzpe to blame me for that, just because this
code moved to drivers/irqchip with
commit 81243e444c6e9d1625073e4a3d3bc244c8a545f0
Author: Rob Herring <rob.herring@xxxxxxxxxxx>
Date: Tue Nov 20 21:21:40 2012 -0600
irqchip: Move ARM GIC to drivers/irqchip
almost two years later?
The code move neither exempts you from the responsibility of merging
it nor does it imply a retroactive responsibility for me to review all
patches which went into that code prior to the move.
Thanks,
tglx
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
