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.15
Date: Mon, 30 Aug 2021 13:50:34 +0100 [thread overview]
Message-ID: <20210830125048.919B3D1B482@fitzroy.sirena.org.uk> (raw)
The following changes since commit e22ce8eb631bdc47a4a4ea7ecf4e4ba499db4f93:
Linux 5.14-rc7 (2021-08-22 14:24:56 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git tags/regmap-v5.15
for you to fetch changes up to ca5537c9be13c205492e704c5a3016f54b2fefec:
Merge remote-tracking branch 'regmap/for-5.15' into regmap-next (2021-08-26 13:45:27 +0100)
----------------------------------------------------------------
regmap: Updates for v5.15
A few small fixes for regmaps this time, plus support for
allowing drivers to select raw spinlocks for the locks in order
to allow usage in interrutpt controllers.
----------------------------------------------------------------
Icenowy Zheng (1):
regmap: allow const array for {devm_,}regmap_field_bulk_alloc reg_fields
Jeongtae Park (1):
regmap: fix the offset of register error log
Jinchao Wang (1):
regmap: Prefer unsigned int to bare use of unsigned
Mark Brown (2):
Merge series "Use raw spinlocks in the ls-extirq driver" from Vladimir Oltean <vladimir.oltean@nxp.com>:
Merge remote-tracking branch 'regmap/for-5.15' into regmap-next
Vladimir Oltean (1):
regmap: teach regmap to use raw spinlocks if requested in the config
drivers/base/regmap/internal.h | 4 +++
drivers/base/regmap/regmap-debugfs.c | 2 +-
drivers/base/regmap/regmap-mmio.c | 2 +-
drivers/base/regmap/regmap.c | 49 +++++++++++++++++++++++++++---------
include/linux/regmap.h | 7 ++++--
5 files changed, 48 insertions(+), 16 deletions(-)
next reply other threads:[~2021-08-30 12:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 12:50 Mark Brown [this message]
2021-08-30 17:17 ` Linus Torvalds
2021-08-30 18:47 ` 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=20210830125048.919B3D1B482@fitzroy.sirena.org.uk \
--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
all inboxes | Powered by JetHome®