From: Bartosz Golaszewski <bgolaszewski@baylibre.com>
To: Linus Walleij <linus.walleij@linaro.org>,
Alexandre Courbot <gnurou@gmail.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Vignesh R <vigneshr@ti.com>, Yong Li <yong.b.li@intel.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>, Wolfram Sang <wsa@the-dreams.de>,
Peter Rosin <peda@axentia.se>
Cc: linux-i2c <linux-i2c@vger.kernel.org>,
linux-gpio <linux-gpio@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>
Subject: [PATCH] gpio: pca953x: add a comment explaining the need for a lockdep subclass
Date: Mon, 26 Sep 2016 11:54:14 +0200 [thread overview]
Message-ID: <1474883655-15824-1-git-send-email-bgolaszewski@baylibre.com> (raw)
Since there's an rc8 I thought I'd send a follow-up patch to the
series addressing the lockdep false positive in pca953x.
The reason for setting the subclass in the probe function is not
explained in the code nor is it obvious at first glance. This patch
adds a comment explaining the problem.
Rebased on top of current i2c/for-next.
Bartosz Golaszewski (1):
gpio: pca953x: add a comment explaining the need for a lockdep
subclass
drivers/gpio/gpio-pca953x.c | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
--
2.7.4
next reply other threads:[~2016-09-26 9:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-26 9:54 Bartosz Golaszewski [this message]
2016-09-26 9:54 ` [PATCH] gpio: pca953x: add a comment explaining the need for a lockdep subclass Bartosz Golaszewski
2016-09-26 10:00 ` Wolfram Sang
2016-09-29 6:06 ` Wolfram Sang
2016-09-29 7:56 ` Bartosz Golaszewski
2016-09-29 8:04 ` Wolfram Sang
2016-10-04 12:17 ` Linus Walleij
2016-10-12 7:00 ` Wolfram Sang
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=1474883655-15824-1-git-send-email-bgolaszewski@baylibre.com \
--to=bgolaszewski@baylibre.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=geert+renesas@glider.be \
--cc=gnurou@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peda@axentia.se \
--cc=peterz@infradead.org \
--cc=vigneshr@ti.com \
--cc=wsa@the-dreams.de \
--cc=yong.b.li@intel.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).