Re: [PATCH V4 01/14] sh: Eliminate unused irq_reg_{readl,writel} accessors

From: Geert Uytterhoeven
Date: Mon Jan 19 2015 - 14:13:31 EST


Hi Jason,

On Sun, Nov 16, 2014 at 10:34 AM, Geert Uytterhoeven
<geert@xxxxxxxxxxxxxx> wrote:
> Hi Jason,
>
> On Fri, Nov 14, 2014 at 6:05 PM, Jason Cooper <jason@xxxxxxxxxxxxxx> wrote:
>> On Fri, Nov 14, 2014 at 05:38:44PM +0100, Ralf Baechle wrote:
>>> On Mon, Nov 10, 2014 at 09:13:49AM +0100, Geert Uytterhoeven wrote:
>>>
>>> > On Fri, Nov 7, 2014 at 7:44 AM, Kevin Cernekee <cernekee@xxxxxxxxx> wrote:
>>> > > Defining these macros way down in arch/sh/.../irq.c doesn't cause
>>> > > kernel/irq/generic-chip.c to use them. As far as I can tell this code
>>> > > has no effect.
>>> > >
>>> > > Signed-off-by: Kevin Cernekee <cernekee@xxxxxxxxx>
>>> >
>>> > Compared preprocessor and asm output before and after, no difference
>>> > except for line numbers, so
>>> >
>>> > Tested-by: Geert Uytterhoeven <geert+renesas@xxxxxxxxx>
>>>
>>> I noticed the remainder of of this series is now in Jason Cooper's irqchip
>>> tree. Is anybody still taking care of SH? If not I can funnel it
>>> through the MIPS tree.
>>
>> Are the SH maintainers active? I admit I know very little about the
>> arch. I'm more than happy to pick it up and keep it with the rest of
>> the series, I just didn't want to step on toes...
>
> SH is orphaned, so it would be great if you could pick it up.
> Thanks!

I think you forgot to pick it up, as se7343 and se7722 are still broken:

http://kisskb.ellerman.id.au/kisskb/buildresult/12346740/
http://kisskb.ellerman.id.au/kisskb/buildresult/12346745/

Will you still do so, or shall I forward the patch to Andrew Morton?

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/