From: Greg Ungerer <gerg@uclinux.org>
To: Linus Walleij <linus.walleij@linaro.org>,
linux-gpio@vger.kernel.org, Johan Hovold <johan@kernel.org>,
Alexandre Courbot <acourbot@nvidia.com>,
Michael Welling <mwelling@ieee.org>,
Markus Pargmann <mpa@pengutronix.de>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: Re: [PATCH 134/182] m68k: gpio: switch to gpiochip_add_data()
Date: Mon, 14 Dec 2015 10:49:50 +1000 [thread overview]
Message-ID: <566E122E.8070700@uclinux.org> (raw)
In-Reply-To: <1449668315-4352-1-git-send-email-linus.walleij@linaro.org>
Hi Linus,
On 09/12/15 23:38, Linus Walleij wrote:
> We're planning to remove the gpiochip_add() function to swith
> to gpiochip_add_data() with NULL for data argument.
>
> Cc: Greg Ungerer <gerg@uclinux.org>
> Cc: Geert Uytterhoeven <geert@linux-m68k.org>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
> ---
> Coldfire maintainers: please ACK this so I can take it through
> the GPIO tree.
Acked-by: Greg Ungerer <gerg@uclinux.org>
Thanks
Greg
> Also consider abstracting out GPIO and moving it to drivers/gpio
> at some point. It would involve some work though.
> ---
> arch/m68k/coldfire/gpio.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/m68k/coldfire/gpio.c b/arch/m68k/coldfire/gpio.c
> index e7e428681ec5..19c335d5031d 100644
> --- a/arch/m68k/coldfire/gpio.c
> +++ b/arch/m68k/coldfire/gpio.c
> @@ -178,7 +178,7 @@ static struct gpio_chip mcfgpio_chip = {
>
> static int __init mcfgpio_sysinit(void)
> {
> - gpiochip_add(&mcfgpio_chip);
> + gpiochip_add_data(&mcfgpio_chip, NULL);
> return subsys_system_register(&mcfgpio_subsys, NULL);
> }
>
>
prev parent reply other threads:[~2015-12-14 0:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 13:38 [PATCH 134/182] m68k: gpio: switch to gpiochip_add_data() Linus Walleij
2015-12-09 13:59 ` Geert Uytterhoeven
2015-12-11 18:28 ` Linus Walleij
2015-12-14 0:49 ` Greg Ungerer [this message]
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=566E122E.8070700@uclinux.org \
--to=gerg@uclinux.org \
--cc=acourbot@nvidia.com \
--cc=geert@linux-m68k.org \
--cc=johan@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=mpa@pengutronix.de \
--cc=mwelling@ieee.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).