All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans-Christian Noren Egtvedt <egtvedt@samfundet.no>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: 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>,
	Haavard Skinnemoen <hskinnemoen@gmail.com>
Subject: Re: [PATCH 131/182] avr32: gpio: use gpiochip data pointer
Date: Wed, 9 Dec 2015 15:01:20 +0100	[thread overview]
Message-ID: <20151209140120.GA3015@samfundet.no> (raw)
In-Reply-To: <1449668213-4111-1-git-send-email-linus.walleij@linaro.org>

Around Wed 09 Dec 2015 14:36:53 +0100 or thereabout, Linus Walleij wrote:
> This makes the driver use the data pointer added to the gpio_chip
> to store a pointer to the state container instead of relying on
> container_of().
> 
> Cc: Haavard Skinnemoen <hskinnemoen@gmail.com>
> Cc: Hans-Christian Egtvedt <egtvedt@samfundet.no>
> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>

Acked-by: Hans-Christian Noren Egtvedt <egtvedt@samfundet.no>

> ---
> AVR32 folks: please ACK this patch so I can take it through the
> GPIO tree.

Thanks for fixing.

> BTW: consider tidying up and moving this driver to drivers/pinctrl
> and implement the right pin control interfaces for AVR32 ...
> thanks.

I note the heads up, added to my backlog.

> ---
>  arch/avr32/mach-at32ap/pio.c | 12 ++++++------
>  1 file changed, 6 insertions(+), 6 deletions(-)

<snipp diff>

-- 
mvh
Hans-Christian Egtvedt

      reply	other threads:[~2015-12-09 14:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-09 13:36 [PATCH 131/182] avr32: gpio: use gpiochip data pointer Linus Walleij
2015-12-09 14:01 ` Hans-Christian Noren Egtvedt [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=20151209140120.GA3015@samfundet.no \
    --to=egtvedt@samfundet.no \
    --cc=acourbot@nvidia.com \
    --cc=hskinnemoen@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.