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 v5.13
Date: Mon, 26 Apr 2021 15:39:45 +0100 [thread overview]
Message-ID: <20210426144029.45F7361139@mail.kernel.org> (raw)
The following changes since commit e49d033bddf5b565044e2abe4241353959bc9120:
Linux 5.12-rc6 (2021-04-04 14:15:36 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git tags/regmap-v5.13
for you to fetch changes up to ccac12acc0c0d66b26ce7834e2dcf54ae159e63a:
Merge remote-tracking branch 'regmap/for-5.13' into regmap-next (2021-04-07 21:22:41 +0100)
----------------------------------------------------------------
regmap: Updates for v5.13
A couple of fixes in this release, plus a couple of new features for
regmap-irq - we now support sub-irq blocks at arbatrary addresses and
can remap configuration bitfields for interrupts split over multiple
registers to the Linux configurations.
----------------------------------------------------------------
Colin Ian King (1):
regmap-irq: Fix dereference of a potentially null d->virt_buf
Guru Das Srinagesh (3):
regmap-irq: Extend sub-irq to support non-fixed reg strides
regmap-irq: Introduce virtual regs to handle more config regs
regmap-irq: Add driver callback to configure virtual regs
Mark Brown (2):
Merge remote-tracking branch 'regmap/for-5.12' into regmap-linus
Merge remote-tracking branch 'regmap/for-5.13' into regmap-next
Meng Li (1):
regmap: set debugfs_name to NULL after it is freed
drivers/base/regmap/regmap-debugfs.c | 1 +
drivers/base/regmap/regmap-irq.c | 126 +++++++++++++++++++++++++++--------
include/linux/regmap.h | 16 +++++
3 files changed, 114 insertions(+), 29 deletions(-)
next reply other threads:[~2021-04-26 14:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-26 14:39 Mark Brown [this message]
2021-04-26 23:36 ` [GIT PULL] regmap updates for v5.13 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=20210426144029.45F7361139@mail.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