linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Grant Likely <grant.likely@secretlab.ca>,
	Linus Walleij <linus.walleij@linaro.org>
Cc: linux-kernel@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH] gpiolib: add another might_sleep
Date: Thu, 13 Sep 2012 10:36:23 +0200	[thread overview]
Message-ID: <20120913083623.GH19497@pengutronix.de> (raw)
In-Reply-To: <20110829190142.GA17354@ponder.secretlab.ca>

Hello,

On Mon, Aug 29, 2011 at 01:01:42PM -0600, Grant Likely wrote:
> On Thu, Feb 17, 2011 at 10:18:53PM +0100, Uwe Kleine-König wrote:
> > Signed-off-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
> 
> Applied, thanks.
I cannot see it in Linus' tree?!

> > ---
> >  drivers/gpio/gpiolib.c |    1 +
> >  1 files changed, 1 insertions(+), 0 deletions(-)
> > 
> > diff --git a/drivers/gpio/gpiolib.c b/drivers/gpio/gpiolib.c
> > index 5fc5e2d..2c9f814 100644
> > --- a/drivers/gpio/gpiolib.c
> > +++ b/drivers/gpio/gpiolib.c
> > @@ -1207,6 +1207,7 @@ int gpio_request(unsigned gpio, const char *label)
> >  	if (chip->request) {
> >  		/* chip->request may sleep */
> >  		spin_unlock_irqrestore(&gpio_lock, flags);
> > +		might_sleep_if(chip->can_sleep);
> >  		status = chip->request(chip, gpio - chip->base);
> >  		spin_lock_irqsave(&gpio_lock, flags);
> >  
> > -- 
> > 1.7.2.3
> > 

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

  reply	other threads:[~2012-09-13  8:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-17 21:18 [PATCH] gpiolib: add another might_sleep Uwe Kleine-König
2011-08-29 19:01 ` Grant Likely
2012-09-13  8:36   ` Uwe Kleine-König [this message]
2012-09-16 21:55     ` Linus Walleij

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=20120913083623.GH19497@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=grant.likely@secretlab.ca \
    --cc=kernel@pengutronix.de \
    --cc=linus.walleij@linaro.org \
    --cc=linux-kernel@vger.kernel.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).