linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: eric.y.miao@gmail.com (Eric Miao)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] PalmTreo: generalisation of Treo680 code
Date: Sat, 10 Oct 2009 22:06:59 +0800	[thread overview]
Message-ID: <f17812d70910100706r6bb37749ud15fd496fcd2fc28@mail.gmail.com> (raw)
In-Reply-To: <200909131127.05790.marek.vasut@gmail.com>

Sorry for late response. Applied to 'devel'.

On Sun, Sep 13, 2009 at 5:27 PM, Marek Vasut <marek.vasut@gmail.com> wrote:
> Dne Ne 13. z??? 2009 11:03:37 Tom?? 'Sleep_Walker' ?ech napsal(a):
>> Hi,
>>
>> thanks for reading my patch!
>>
>> Dne So 12. z??? 2009 21:29:06 Marek Vasut napsal(a):
>> > ...
>> >
>> > > -static struct gpio_led_platform_data gpio_led_info = {
>> > > - .leds ? ? ? ? ? = gpio_leds,
>> > > - .num_leds ? ? ? = ARRAY_SIZE(gpio_leds),
>> > > +static struct gpio_led_platform_data treo680_gpio_led_info = {
>> > > + .leds ? ? ? ? ? = treo680_gpio_leds,
>> > > + .num_leds ? ? ? = ARRAY_SIZE(treo680_gpio_leds),
>> > > ?};
>> >
>> > Be careful so you dont run into symbol redefinition here (gpio_led_info)
>> > in case the kernel supports more than this one device ...
>>
>> That's why I change the name. It's called now 'treo680_gpio_led_info' as
>> ?you can see.
>>
>> > ...
>> >
>> > > +#endif /* CONFIG_MACH_TREO680 */
>> > > +
>> > > ?/* setup udc GPIOs initial state */
>> > > -static void __init treo680_udc_init(void)
>> > > +static void __init treo_udc_init(void)
>> > > ?{
>> > > - if (!gpio_request(GPIO_NR_TREO680_USB_PULLUP, "UDC Vbus")) {
>> > > - ? ? ? ? gpio_direction_output(GPIO_NR_TREO680_USB_PULLUP, 1);
>> > > - ? ? ? ? gpio_free(GPIO_NR_TREO680_USB_PULLUP);
>> > > + if (!gpio_request(GPIO_NR_TREO_USB_PULLUP, "UDC Vbus")) {
>> > > + ? ? ? ? gpio_direction_output(GPIO_NR_TREO_USB_PULLUP, 1);
>> > > + ? ? ? ? gpio_free(GPIO_NR_TREO_USB_PULLUP);
>> > > ? }
>> > > ?}
>> >
>> > Is this really needed or is it just a copy-paste from other Palm device?
>>
>> Unfortunately yes. There is no copy-paste in this code which wasn't checked
>> ?and tested. It doesn't work correctly without that.
>>
>> Best regards,
>>
>> Tomas Cech
>>
>
> Oh ok, you have my Ack on both then.
>

  reply	other threads:[~2009-10-10 14:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-11 11:57 generalise Treo680 code and add support for Palm Centro - round 3 Tomáš Čech
2009-09-11 11:57 ` [PATCH 1/2] PalmTreo: generalisation of Treo680 code Tomáš Čech
2009-09-11 11:57   ` [PATCH 2/2] PalmTreo: add Palm Centro 685 support Tomáš Čech
2009-09-12 19:31     ` Marek Vasut
2009-09-13  9:06       ` Tomáš 'Sleep_Walker' Čech
2009-10-10 14:13         ` Eric Miao
2009-09-11 12:02   ` [PATCH 1/2] PalmTreo: generalisation of Treo680 code Tomáš 'Sleep_Walker' Čech
2009-09-12 19:29   ` Marek Vasut
2009-09-13  9:03     ` Tomáš 'Sleep_Walker' Čech
2009-09-13  9:27       ` Marek Vasut
2009-10-10 14:06         ` Eric Miao [this message]
2009-10-12 18:45           ` Tomáš 'Sleep_Walker' Čech
2009-09-17 21:08 ` generalise Treo680 code and add support for Palm Centro - round 3 Tomáš 'Sleep_Walker' Čech
2009-09-18  1:05   ` Marek Vasut
2009-09-18  6:06     ` Eric Miao

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=f17812d70910100706r6bb37749ud15fd496fcd2fc28@mail.gmail.com \
    --to=eric.y.miao@gmail.com \
    --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).