From: Wolfram Sang <wsa@the-dreams.de>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>,
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>, Peter Rosin <peda@axentia.se>,
linux-i2c <linux-i2c@vger.kernel.org>,
linux-gpio <linux-gpio@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 4/4] gpio: pca953x: fix an incorrect lockdep warning
Date: Sat, 24 Sep 2016 10:55:24 +0200 [thread overview]
Message-ID: <20160924085524.GB1434@katana> (raw)
In-Reply-To: <CACRpkdbYgetpYntO6KsVLh1n_7DU+1AD3AwVVkmV5ud5A6Q31g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 690 bytes --]
On Fri, Sep 23, 2016 at 10:10:57AM +0200, Linus Walleij wrote:
> On Wed, Sep 21, 2016 at 7:45 AM, Wolfram Sang <wsa@the-dreams.de> wrote:
>
> >> In order to get rid of the warning, retrieve the adapter nesting depth
> >> and use it as lockdep subclass for chip->i2c_lock.
> >>
> >> Signed-off-by: Bartosz Golaszewski <bgolaszewski@baylibre.com>
> >
> > Linus, we'd like that in 4.9. Can I get your ack for the gpio part?
>
> Acked-by: Linus Walleij <linus.walleij@linaro.org>
>
> Sorry for not attending quick enough, I was down in the
> block layer.
Well, it was close but still quick enough. Glad to see that one can come
back from the depths of the block layer ;)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-09-24 8:55 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 16:02 [PATCH v2 0/4] gpio: fix an incorrect lockdep warning Bartosz Golaszewski
2016-09-16 16:02 ` [PATCH v2 1/4] i2c: export i2c_adapter_depth() Bartosz Golaszewski
2016-09-16 16:02 ` [PATCH v2 2/4] lockdep: make MAX_LOCKDEP_SUBCLASSES unconditionally visible Bartosz Golaszewski
2016-09-16 16:02 ` [PATCH v2 3/4] i2c: add a warning to i2c_adapter_depth() Bartosz Golaszewski
2016-09-16 16:02 ` [PATCH v2 4/4] gpio: pca953x: fix an incorrect lockdep warning Bartosz Golaszewski
2016-09-21 5:45 ` Wolfram Sang
2016-09-23 8:10 ` Linus Walleij
2016-09-24 8:55 ` Wolfram Sang [this message]
2016-09-24 9:15 ` Wolfram Sang
2016-09-24 14:26 ` Geert Uytterhoeven
2016-09-16 17:26 ` [PATCH v2 0/4] gpio: " Wolfram Sang
2016-09-16 17:45 ` Peter Rosin
2016-09-16 17:58 ` Wolfram Sang
2016-09-18 8:52 ` Peter Rosin
2016-09-18 19:43 ` Bartosz Golaszewski
2016-09-18 19:45 ` Bartosz Golaszewski
2016-09-19 8:01 ` Peter Rosin
2016-09-19 8:14 ` Peter Zijlstra
2016-09-19 8:48 ` Peter Rosin
2016-09-19 9:03 ` Peter Zijlstra
2016-09-20 8:48 ` Peter Rosin
2016-09-20 10:07 ` Bartosz Golaszewski
2016-09-20 10:28 ` Peter Zijlstra
2016-09-20 10:48 ` Peter Rosin
2016-09-20 11:30 ` Geert Uytterhoeven
2016-09-20 12:32 ` Bartosz Golaszewski
2016-09-20 15:33 ` Thomas Gleixner
2016-09-21 9:47 ` Peter Rosin
2016-09-17 1:19 ` Peter Zijlstra
2016-09-17 10:18 ` Wolfram Sang
2016-09-17 18:59 ` Bartosz Golaszewski
2016-09-24 8:56 ` 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=20160924085524.GB1434@katana \
--to=wsa@the-dreams.de \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bgolaszewski@baylibre.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=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 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.