From: Clemens Gruber <clemens.gruber@pqgruber.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-gpio@vger.kernel.org,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Wolfram Sang <wsa@the-dreams.de>,
linux-kernel@vger.kernel.org
Subject: Re: pca953x: lockdep warning since 4.10
Date: Wed, 11 Jan 2017 16:06:33 +0100 [thread overview]
Message-ID: <20170111150633.GA19933@archie.localdomain> (raw)
In-Reply-To: <CACRpkdaaCJK3=VOvyHt5hdJQJCQmaFjW5YXwEqivVPdFXDZ91Q@mail.gmail.com>
On Wed, Jan 11, 2017 at 02:43:31PM +0100, Linus Walleij wrote:
> On Sat, Jan 7, 2017 at 9:54 PM, Clemens Gruber
> <clemens.gruber@pqgruber.com> wrote:
>
> > I observed the following lockdep warning when booting an i.MX6Q board
> > with several PCAL9555A gpio expanders connected over I2C. They are
> > connected to 3 separate busses, there is no i2c-mux in use.
> >
> > This warning appears with the latest mainline Linux kernel 4.10-rc2:
>
> Can you please test the patch with subject:
> "gpio: provide lockdep keys for nested/unnested irqchips"
> that I sent out a few minutes ago?
Yes, the lockdep warning disappears. Thank you.
>
> Please provide Tested-by if it solves your issue.
I'll send my Tested-by tag in reply to your v2 of the patch (due to the
typo in v1, which breaks the build)
Clemens
prev parent reply other threads:[~2017-01-11 15:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-07 20:54 pca953x: lockdep warning since 4.10 Clemens Gruber
2017-01-08 18:13 ` Bartosz Golaszewski
2017-01-08 20:42 ` Clemens Gruber
2017-01-11 13:43 ` Linus Walleij
2017-01-11 15:06 ` Clemens Gruber [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=20170111150633.GA19933@archie.localdomain \
--to=clemens.gruber@pqgruber.com \
--cc=bgolaszewski@baylibre.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wsa@the-dreams.de \
/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).