linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: grant.likely@secretlab.ca (Grant Likely)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] gpio: pl061: remove old comment
Date: Fri, 30 Nov 2012 11:13:05 +0000	[thread overview]
Message-ID: <20121130111305.E92EC3E14C4@localhost> (raw)
In-Reply-To: <9726894cfe3ff11c9f3a95e436ae386637eba98f.1353577495.git.baruch@tkos.co.il>

On Thu, 22 Nov 2012 11:46:14 +0200, Baruch Siach <baruch@tkos.co.il> wrote:
> Since 3ab524754 (gpio: pl061: convert to use generic irq chip) we only have one
> spinlock in struct pl061_gpio.
> 
> Cc: Rob Herring <rob.herring@calxeda.com>
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>

Applied, thanks.

g.

> ---
>  drivers/gpio/gpio-pl061.c |    7 +------
>  1 file changed, 1 insertion(+), 6 deletions(-)
> 
> diff --git a/drivers/gpio/gpio-pl061.c b/drivers/gpio/gpio-pl061.c
> index b4b5da4..2b2e73c 100644
> --- a/drivers/gpio/gpio-pl061.c
> +++ b/drivers/gpio/gpio-pl061.c
> @@ -48,12 +48,7 @@ struct pl061_context_save_regs {
>  #endif
>  
>  struct pl061_gpio {
> -	/* Each of the two spinlocks protects a different set of hardware
> -	 * regiters and data structurs. This decouples the code of the IRQ from
> -	 * the GPIO code. This also makes the case of a GPIO routine call from
> -	 * the IRQ code simpler.
> -	 */
> -	spinlock_t		lock;		/* GPIO registers */
> +	spinlock_t		lock;
>  
>  	void __iomem		*base;
>  	int			irq_base;
> -- 
> 1.7.10.4
> 

-- 
Grant Likely, B.Sc, P.Eng.
Secret Lab Technologies, Ltd.

      parent reply	other threads:[~2012-11-30 11:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-22  9:46 [PATCH] gpio: pl061: remove old comment Baruch Siach
2012-11-26  6:53 ` Linus Walleij
2012-11-30 11:13 ` Grant Likely [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=20121130111305.E92EC3E14C4@localhost \
    --to=grant.likely@secretlab.ca \
    --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).