linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: Axel Lin <axel.lin@gmail.com>
Cc: linux-kernel@vger.kernel.org,
	Tomoya MORINAGA <tomoya-linux@dsn.lapis-semi.com>,
	Feng Tang <feng.tang@intel.com>,
	Linus Walleij <linus.walleij@stericsson.com>
Subject: Re: [PATCH 1/2 RESEND] gpio: Add missing spin_lock_init in gpio-ml-ioh driver
Date: Wed, 1 Feb 2012 21:59:49 -0700	[thread overview]
Message-ID: <20120202045949.GL15343@ponder.secretlab.ca> (raw)
In-Reply-To: <1328064605.3533.1.camel@phoenix>

On Wed, Feb 01, 2012 at 10:50:05AM +0800, Axel Lin wrote:
> This bug was introduced by commit 54be5663
> "gpio-ml-ioh: Support interrupt function" which adds a spinlock to struct
> ioh_gpio but never init the spinlock.
> 
> Signed-off-by: Axel Lin <axel.lin@gmail.com>

Applied both, thanks.

g.

> ---
>  drivers/gpio/gpio-ml-ioh.c |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> diff --git a/drivers/gpio/gpio-ml-ioh.c b/drivers/gpio/gpio-ml-ioh.c
> index 461958f..271fd49 100644
> --- a/drivers/gpio/gpio-ml-ioh.c
> +++ b/drivers/gpio/gpio-ml-ioh.c
> @@ -448,6 +448,7 @@ static int __devinit ioh_gpio_probe(struct pci_dev *pdev,
>  		chip->reg = chip->base;
>  		chip->ch = i;
>  		mutex_init(&chip->lock);
> +		spin_lock_init(&chip->spinlock);
>  		ioh_gpio_setup(chip, num_ports[i]);
>  		ret = gpiochip_add(&chip->gpio);
>  		if (ret) {
> -- 
> 1.7.5.4
> 
> 
> 

      parent reply	other threads:[~2012-02-02  4:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-01  2:50 [PATCH 1/2 RESEND] gpio: Add missing spin_lock_init in gpio-ml-ioh driver Axel Lin
2012-02-01  2:51 ` [PATCH 2/2 RESEND] gpio: Add missing spin_lock_init in gpio-pch driver Axel Lin
2012-02-02  4:59 ` 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=20120202045949.GL15343@ponder.secretlab.ca \
    --to=grant.likely@secretlab.ca \
    --cc=axel.lin@gmail.com \
    --cc=feng.tang@intel.com \
    --cc=linus.walleij@stericsson.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tomoya-linux@dsn.lapis-semi.com \
    /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).