From: "Grygorii.Strashko@linaro.org" <grygorii.strashko@linaro.org>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
linux-gpio@vger.kernel.org,
Grygorii Strashko <grygorii.Strashko@ti.com>,
Javier Martinez Canillas <javier@dowhile0.org>
Subject: Re: gpio: omap: fix error handling in omap_gpio_irq_type
Date: Tue, 09 Jun 2015 17:01:18 +0300 [thread overview]
Message-ID: <5576F1AE.10306@linaro.org> (raw)
In-Reply-To: <20150609090237.GA3605@mwanda>
On 06/09/2015 12:02 PM, Dan Carpenter wrote:
>
> The patch 1562e4618ded: "gpio: omap: fix error handling in
> omap_gpio_irq_type" from May 22, 2015, leads to the following static
> checker warning:
>
> drivers/gpio/gpio-omap.c:523 omap_gpio_irq_type()
> warn: inconsistent returns 'spin_lock:&bank->lock'.
Fix for this issue has been posted already.
http://www.spinics.net/lists/linux-gpio/msg06440.html
--
regards,
-grygorii
prev parent reply other threads:[~2015-06-09 14:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-09 9:02 gpio: omap: fix error handling in omap_gpio_irq_type Dan Carpenter
2015-06-09 14:01 ` Grygorii.Strashko@linaro.org [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=5576F1AE.10306@linaro.org \
--to=grygorii.strashko@linaro.org \
--cc=dan.carpenter@oracle.com \
--cc=grygorii.Strashko@ti.com \
--cc=javier@dowhile0.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@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 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.