Re: [PATCH 09/14] ARM: mvebu: Remove init_irq declaration in machine description
On Mon, May 13, 2013 at 8:53 AM, Maxime Ripard
wrote:
> Hi Jason,
>
> Le 13/05/2013 17:19, Jason Cooper a écrit :
>> On Mon, May 13, 2013 at 11:44:08AM +0200, Maxime Ripard wrote:
>>> Commit ebafed7a ("ARM: irq: Call irqchip_init if no init_irq function is
>>> specified") removed the need to explictly setup the init_irq field in
>>> the machine description when using only irqchip_init. Remove that
>>> declaration for mvebu as well.
>>>
>>> Signed-off-by: Maxime Ripard
>>> ---
>>> arch/arm/mach-mvebu/armada-370-xp.c | 1 -
>>> 1 file changed, 1 deletion(-)
>>
>> Maxime,
>>
>> Do do want the individual submaintainers to take these? Or, send one
>> branch to Arnd and Olof? I'm fine with either one as any merge
>> conflicts should be trivial.
>
> I don't have a strong opinion on this one, I guess both will be fine.
> Arnd, Olof, what do you prefer?
>
> I'll probably have to send a v2 anyway, I forgot to remove the include
> of the irqchip headers.
Since each and every patch applies cleanly and things work well both
before and after, let's have each maintainer that is active apply
their own. If there are platforms that don't have a significant number
of patches, i.e. if they're not collecting a branch, then we can apply
those. Please follow up with us with the stragglers, I'll assume the
rest will come in through the respective maintainers.
-Olof
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 09/14] ARM: mvebu: Remove init_irq declaration in machine description
Hi Jason,
Le 13/05/2013 17:19, Jason Cooper a écrit :
> On Mon, May 13, 2013 at 11:44:08AM +0200, Maxime Ripard wrote:
>> Commit ebafed7a ("ARM: irq: Call irqchip_init if no init_irq function is
>> specified") removed the need to explictly setup the init_irq field in
>> the machine description when using only irqchip_init. Remove that
>> declaration for mvebu as well.
>>
>> Signed-off-by: Maxime Ripard
>> ---
>> arch/arm/mach-mvebu/armada-370-xp.c | 1 -
>> 1 file changed, 1 deletion(-)
>
> Maxime,
>
> Do do want the individual submaintainers to take these? Or, send one
> branch to Arnd and Olof? I'm fine with either one as any merge
> conflicts should be trivial.
I don't have a strong opinion on this one, I guess both will be fine.
Arnd, Olof, what do you prefer?
I'll probably have to send a v2 anyway, I forgot to remove the include
of the irqchip headers.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 09/14] ARM: mvebu: Remove init_irq declaration in machine description
On Mon, May 13, 2013 at 11:44:08AM +0200, Maxime Ripard wrote:
> Commit ebafed7a ("ARM: irq: Call irqchip_init if no init_irq function is
> specified") removed the need to explictly setup the init_irq field in
> the machine description when using only irqchip_init. Remove that
> declaration for mvebu as well.
>
> Signed-off-by: Maxime Ripard
> ---
> arch/arm/mach-mvebu/armada-370-xp.c | 1 -
> 1 file changed, 1 deletion(-)
Maxime,
Do do want the individual submaintainers to take these? Or, send one
branch to Arnd and Olof? I'm fine with either one as any merge
conflicts should be trivial.
In either case,
Acked-by: Jason Cooper
thx,
Jason.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 09/14] ARM: mvebu: Remove init_irq declaration in machine description
On Mon, May 13, 2013 at 11:44:08AM +0200, Maxime Ripard wrote: Commit ebafed7a (ARM: irq: Call irqchip_init if no init_irq function is specified) removed the need to explictly setup the init_irq field in the machine description when using only irqchip_init. Remove that declaration for mvebu as well. Signed-off-by: Maxime Ripard maxime.rip...@free-electrons.com --- arch/arm/mach-mvebu/armada-370-xp.c | 1 - 1 file changed, 1 deletion(-) Maxime, Do do want the individual submaintainers to take these? Or, send one branch to Arnd and Olof? I'm fine with either one as any merge conflicts should be trivial. In either case, Acked-by: Jason Cooper ja...@lakedaemon.net thx, Jason. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 09/14] ARM: mvebu: Remove init_irq declaration in machine description
Hi Jason, Le 13/05/2013 17:19, Jason Cooper a écrit : On Mon, May 13, 2013 at 11:44:08AM +0200, Maxime Ripard wrote: Commit ebafed7a (ARM: irq: Call irqchip_init if no init_irq function is specified) removed the need to explictly setup the init_irq field in the machine description when using only irqchip_init. Remove that declaration for mvebu as well. Signed-off-by: Maxime Ripard maxime.rip...@free-electrons.com --- arch/arm/mach-mvebu/armada-370-xp.c | 1 - 1 file changed, 1 deletion(-) Maxime, Do do want the individual submaintainers to take these? Or, send one branch to Arnd and Olof? I'm fine with either one as any merge conflicts should be trivial. I don't have a strong opinion on this one, I guess both will be fine. Arnd, Olof, what do you prefer? I'll probably have to send a v2 anyway, I forgot to remove the include of the irqchip headers. Maxime -- Maxime Ripard, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH 09/14] ARM: mvebu: Remove init_irq declaration in machine description
On Mon, May 13, 2013 at 8:53 AM, Maxime Ripard maxime.rip...@free-electrons.com wrote: Hi Jason, Le 13/05/2013 17:19, Jason Cooper a écrit : On Mon, May 13, 2013 at 11:44:08AM +0200, Maxime Ripard wrote: Commit ebafed7a (ARM: irq: Call irqchip_init if no init_irq function is specified) removed the need to explictly setup the init_irq field in the machine description when using only irqchip_init. Remove that declaration for mvebu as well. Signed-off-by: Maxime Ripard maxime.rip...@free-electrons.com --- arch/arm/mach-mvebu/armada-370-xp.c | 1 - 1 file changed, 1 deletion(-) Maxime, Do do want the individual submaintainers to take these? Or, send one branch to Arnd and Olof? I'm fine with either one as any merge conflicts should be trivial. I don't have a strong opinion on this one, I guess both will be fine. Arnd, Olof, what do you prefer? I'll probably have to send a v2 anyway, I forgot to remove the include of the irqchip headers. Since each and every patch applies cleanly and things work well both before and after, let's have each maintainer that is active apply their own. If there are platforms that don't have a significant number of patches, i.e. if they're not collecting a branch, then we can apply those. Please follow up with us with the stragglers, I'll assume the rest will come in through the respective maintainers. -Olof -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
