From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] pinctrl/at91: fix compatible order
Date: Mon, 15 Oct 2012 14:33:19 +0200 [thread overview]
Message-ID: <CACRpkda0_=j3k8sYNjPSbQFU25VKeAxY=95ea81hfWRPUoo4_Q@mail.gmail.com> (raw)
In-Reply-To: <5078235C.1040204@atmel.com>
On Fri, Oct 12, 2012 at 4:04 PM, ludovic.desroches
<ludovic.desroches@atmel.com> wrote:
> Le 10/12/2012 11:23 AM, Jean-Christophe PLAGNIOL-VILLARD a ?crit :
>
>> the sam9x5 is new version of the rm9200 not the invert
>>
>> Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
>> Cc: Linus Walleij <linus.walleij@linaro.org>
>> ---
>> drivers/pinctrl/pinctrl-at91.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/pinctrl/pinctrl-at91.c
>> b/drivers/pinctrl/pinctrl-at91.c
>> index 9c0fe11..bdb152b 100644
>> --- a/drivers/pinctrl/pinctrl-at91.c
>> +++ b/drivers/pinctrl/pinctrl-at91.c
>> @@ -1331,8 +1331,8 @@ static void __devinit at91_gpio_probe_fixup(void)
>> }
>>
>> static struct of_device_id at91_gpio_of_match[] __devinitdata = {
>> - { .compatible = "atmel,at91rm9200-gpio", .data = &at91rm9200_ops
>> },
>> { .compatible = "atmel,at91sam9x5-gpio", .data = &at91sam9x5_ops,
>> },
>> + { .compatible = "atmel,at91rm9200-gpio", .data = &at91rm9200_ops
>> },
>> { /* sentinel */ }
>> };
>>
>
> Do it also for at91_pinctrl_of_match[], there is the same issue.
Shall I apply this patch to my at91 branch or will it be updated to
cover both cases?
Yours,
Linus Walleij
next prev parent reply other threads:[~2012-10-15 12:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-12 9:23 [PATCH 1/1] pinctrl/at91: fix compatible order Jean-Christophe PLAGNIOL-VILLARD
2012-10-12 14:04 ` ludovic.desroches
2012-10-15 12:33 ` Linus Walleij [this message]
2012-10-15 13:32 ` Jean-Christophe PLAGNIOL-VILLARD
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='CACRpkda0_=j3k8sYNjPSbQFU25VKeAxY=95ea81hfWRPUoo4_Q@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--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).