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 updates for v7.2
Date: Mon, 15 Jun 2026 18:04:28 +0100 [thread overview]
Message-ID: <b58ab35c6f5d73318a150bd6a8ca56e4@kernel.org> (raw)
The following changes since commit 254f49634ee16a731174d2ae34bc50bd5f45e731:
Linux 7.1-rc1 (2026-04-26 14:19:00 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git tags/regmap-v7.2
for you to fetch changes up to 34808ac8ddafc3e2c2a59e84eaab0a410e7a0fdc:
regmap-i2c: fix sparse warning in regmap_smbus_word_write_reg16 (2026-05-21 09:47:39 +0100)
----------------------------------------------------------------
regmap: Update for v7.2
This time around we just have a single fix for a sparse warning.
----------------------------------------------------------------
Nishanth Sampath Kumar (1):
regmap-i2c: fix sparse warning in regmap_smbus_word_write_reg16
drivers/base/regmap/regmap-i2c.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
next reply other threads:[~2026-06-15 17:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-15 17:04 Mark Brown [this message]
2026-06-16 2:30 ` [GIT PULL] regmap updates for v7.2 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=b58ab35c6f5d73318a150bd6a8ca56e4@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.