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 v5.19-rc3
Date: Fri, 24 Jun 2022 17:53:28 +0100 [thread overview]
Message-ID: <20220624165338.79927C3411C@smtp.kernel.org> (raw)
The following changes since commit f2906aa863381afb0015a9eb7fefad885d4e5a56:
Linux 5.19-rc1 (2022-06-05 17:18:54 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git tags/regmap-fix-v5.19-rc3
for you to fetch changes up to 3f05010f243be06478a9b11cfce0ce994f5a0890:
regmap-irq: Fix offset/index mismatch in read_sub_irq_data() (2022-06-22 11:59:52 +0100)
----------------------------------------------------------------
regmap: Fixes for v5.19
Two sets of fixes - one for things that were missed with the support for
custom bulk I/O operations introduced in the last merge window, and
another for some long standing issues with regmap-irq which affect a
fairly small subset of devices.
----------------------------------------------------------------
Aidan MacDonald (2):
regmap-irq: Fix a bug in regmap_irq_enable() for type_in_mask chips
regmap-irq: Fix offset/index mismatch in read_sub_irq_data()
Javier Martinez Canillas (3):
regmap: Re-introduce bulk read support check in regmap_bulk_read()
regmap: Make regmap_noinc_read() return -ENOTSUPP if map->read isn't set
regmap: Wire up regmap_config provided bulk write in missed functions
drivers/base/regmap/regmap-irq.c | 8 +++++---
drivers/base/regmap/regmap.c | 15 ++++++++-------
2 files changed, 13 insertions(+), 10 deletions(-)
next reply other threads:[~2022-06-24 16:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-24 16:53 Mark Brown [this message]
2022-06-24 21:08 ` [GIT PULL] regmap fixes for v5.19-rc3 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=20220624165338.79927C3411C@smtp.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