Re: [PATCH 1/7] irqchip: atmel-aic5: Add sama5d4 support

From: Nicolas Ferre
Date: Thu Sep 11 2014 - 12:30:01 EST


On 11/09/2014 18:28, Alexandre Belloni :
> On 11/09/2014 at 18:17:27 +0200, Nicolas Ferre wrote :
>> On 11/09/2014 17:54, Alexandre Belloni :
>>> Add sama5d4 support to irq-atmel-aic5.
>>>
>>> Signed-off-by: Alexandre Belloni <alexandre.belloni@xxxxxxxxxxxxxxxxxx>
>>> ---
>>> Cc: Jason Cooper <jason@xxxxxxxxxxxxxx>
>>
>> Supposed to be before the "---" ;-)
>
> This actually depends on the maintainer preferences, after the ---
> marker means that it will not appear in the final commit log which was
> my intention.

And it still works with git send-email? good to know! (and sorry for the
noise ;-)).

>>
>>> drivers/irqchip/irq-atmel-aic5.c | 10 ++++++++++
>>> 1 file changed, 10 insertions(+)
>>>
>>> diff --git a/drivers/irqchip/irq-atmel-aic5.c b/drivers/irqchip/irq-atmel-aic5.c
>>> index dc7d98607a89..a11aae8fb006 100644
>>> --- a/drivers/irqchip/irq-atmel-aic5.c
>>> +++ b/drivers/irqchip/irq-atmel-aic5.c
>>> @@ -295,6 +295,7 @@ static void __init sama5d3_aic_irq_fixup(struct device_node *root)
>>>
>>> static const struct of_device_id __initdata aic5_irq_fixups[] = {
>>> { .compatible = "atmel,sama5d3", .data = sama5d3_aic_irq_fixup },
>>> + { .compatible = "atmel,sama5d4", .data = sama5d3_aic_irq_fixup },
>>> { /* sentinel */ },
>>> };
>>>
>>> @@ -349,3 +350,12 @@ static int __init sama5d3_aic5_of_init(struct device_node *node,
>>> return aic5_of_init(node, parent, NR_SAMA5D3_IRQS);
>>> }
>>> IRQCHIP_DECLARE(sama5d3_aic5, "atmel,sama5d3-aic", sama5d3_aic5_of_init);
>>> +
>>> +#define NR_SAMA5D4_IRQS 68
>>> +
>>> +static int __init sama5d4_aic5_of_init(struct device_node *node,
>>> + struct device_node *parent)
>>> +{
>>> + return aic5_of_init(node, parent, NR_SAMA5D4_IRQS);
>>> +}
>>> +IRQCHIP_DECLARE(sama5d4_aic5, "atmel,sama5d4-aic", sama5d4_aic5_of_init);
>>>
>>
>>
>> --
>> Nicolas Ferre
>


--
Nicolas Ferre
--
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/