From: Mark Brown <broonie@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>
Subject: [GIT PULL] regmap fixes for v6.17-merge-window
Date: Fri, 08 Aug 2025 18:01:50 +0100 [thread overview]
Message-ID: <ab85dca88a780d53a88965c6700d08bf.broonie@kernel.org> (raw)
The following changes since commit ffc72771ff6ec9f5b431a86c4b00d8ef0fea958b:
regmap: Annotate that MMIO implies fast IO (2025-07-25 13:44:33 +0100)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git tags/regmap-fix-v6.17-merge-window
for you to fetch changes up to 76b6e14aa7b081337d118a82397d919b5e072bb4:
regmap: irq: Avoid lockdep warnings with nested regmap-irq chips (2025-08-01 13:37:07 +0100)
----------------------------------------------------------------
regmap: Fixes for v6.17
These patches fix a lockdep issue Russell King reported with nested
regmap-irqs (unusual since regmap is generally for devices on slow buses
so devices don't get nested), plus add a missing mutex free which I
noticed while implementing a fix for that issue.
----------------------------------------------------------------
Mark Brown (2):
regmap: irq: Free the regmap-irq mutex
regmap: irq: Avoid lockdep warnings with nested regmap-irq chips
drivers/base/regmap/regmap-irq.c | 30 +++++++++++++++++++++---------
1 file changed, 21 insertions(+), 9 deletions(-)
next reply other threads:[~2025-08-08 17:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-08 17:01 Mark Brown [this message]
2025-08-09 5:45 ` [GIT PULL] regmap fixes for v6.17-merge-window pr-tracker-bot
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=ab85dca88a780d53a88965c6700d08bf.broonie@kernel.org \
--to=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).