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 v7.1-merge-window
Date: Fri, 24 Apr 2026 15:58:55 +0100 [thread overview]
Message-ID: <2ff8c5eda05df6460917985d94298d9d@kernel.org> (raw)
The following changes since commit 8ad7f3b265a87cd4e5052677545f90f14c855b10:
regmap: i3c: Add non-devm regmap_init_i3c() helper (2026-04-10 11:46:15 +0100)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git tags/regmap-fix-v7.1-merge-window
for you to fetch changes up to 7e555fcae40ab2ba91fd5cd54a5a83096414957f:
regmap: ram: fix memory leaks in __regmap_init_ram() on error (2026-04-17 12:07:31 +0100)
----------------------------------------------------------------
regmap: Fixes for v7.1
There's couple of patches here that came in since my pull request:
- What is effectively a quirk for shoehorning support for a wider range
of I2C regmaps on weirdly restricted SMBus controllers.
- One minor fix for a memory leak on in error handling in the dummy
driver used by the KUnit tests.
----------------------------------------------------------------
Nishanth Sampath Kumar (1):
regmap-i2c: add SMBus byte/word reg16 bus for adapters lacking I2C_FUNC_I2C
Yuho Choi (1):
regmap: ram: fix memory leaks in __regmap_init_ram() on error
drivers/base/regmap/regmap-i2c.c | 49 ++++++++++++++++++++++++++++++++++++++++
drivers/base/regmap/regmap-ram.c | 8 ++++++-
2 files changed, 56 insertions(+), 1 deletion(-)
next reply other threads:[~2026-04-24 14:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-24 14:58 Mark Brown [this message]
2026-04-24 20:37 ` [GIT PULL] regmap fixes for v7.1-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=2ff8c5eda05df6460917985d94298d9d@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 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.