Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-mips@linux-mips.org
Subject: Re: [PATCH -mm][MIPS] GPIO LED driver for the WGT634U machine
Date: Wed, 15 Aug 2007 17:39:31 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0708151736150.5158@anakin> (raw)
In-Reply-To: <20070815112507.GB17615@hall.aurel32.net>

On Wed, 15 Aug 2007, Aurelien Jarno wrote:
> --- a/arch/mips/bcm947xx/wgt634u.c
> +++ b/arch/mips/bcm947xx/wgt634u.c

> +static const struct gpio_led wgt634u_leds[] = {

> +static const struct gpio_led_platform_data wgt634u_led_data = {
> +	.num_leds =     ARRAY_SIZE(wgt634u_leds),
> +	.leds =         (void *) wgt634u_leds,
                        ^^^^^^^^

gpio_led_platform_data.leds is of type struct gpio_led *.
Should it be const, or should the const be dropped from wgt634u_leds?

> +static struct platform_device wgt634u_gpio_leds = {
> +	.name =         "leds-gpio",
> +	.id =           -1,
> +	.dev = {
> +		.platform_data = (void *) &wgt634u_led_data,
                                 ^^^^^^^^
device.platform_data is a void *, so you can drop the cast.

Gr{oetje,eeting}s,

						Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

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

  reply	other threads:[~2007-08-15 15:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-15 11:25 [PATCH -mm][MIPS] GPIO LED driver for the WGT634U machine Aurelien Jarno
2007-08-15 15:39 ` Geert Uytterhoeven [this message]
2007-08-15 16:00   ` Geert Uytterhoeven
2007-08-15 18:41   ` Aurelien Jarno

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=Pine.LNX.4.64.0708151736150.5158@anakin \
    --to=geert@linux-m68k.org \
    --cc=akpm@linux-foundation.org \
    --cc=aurelien@aurel32.net \
    --cc=linux-mips@linux-mips.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