From: Wolfram Sang <wsa@kernel.org>
To: Daniel Mack <daniel@zonque.org>
Cc: linux-i2c@vger.kernel.org
Subject: Re: [PATCH] i2c: core: fix lockdep warning for sparsely nested adapter chain
Date: Sat, 28 Oct 2023 14:47:09 +0200 [thread overview]
Message-ID: <ZT0Cza5q5Cjuqyeh@shikoro> (raw)
In-Reply-To: <20231018094613.849007-1-daniel@zonque.org>
[-- Attachment #1: Type: text/plain, Size: 526 bytes --]
On Wed, Oct 18, 2023 at 11:46:13AM +0200, Daniel Mack wrote:
> When adapters are chained in a sparse manner (with intermediate MFD devices,
> for instance) the code currently fails to use the correct subclass for
> the adapter's bus_lock which leads to false-positive lockdep warnings.
>
> Fix this by walking the entire pedigree of the device and count all
> adapters along the way instead of just checking the immediate parent.
>
> Signed-off-by: Daniel Mack <daniel@zonque.org>
Applied to for-next, thanks!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2023-10-28 12:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-18 9:46 [PATCH] i2c: core: fix lockdep warning for sparsely nested adapter chain Daniel Mack
2023-10-26 17:04 ` Wolfram Sang
2023-10-28 12:47 ` Wolfram Sang [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=ZT0Cza5q5Cjuqyeh@shikoro \
--to=wsa@kernel.org \
--cc=daniel@zonque.org \
--cc=linux-i2c@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