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 v6.3
Date: Mon, 20 Feb 2023 14:33:34 +0000 [thread overview]
Message-ID: <20230220143343.694A6C433D2@smtp.kernel.org> (raw)
The following changes since commit 1b929c02afd37871d5afb9d498426f83432e71c2:
Linux 6.2-rc1 (2022-12-25 13:41:39 -0800)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git tags/regmap-v6.3
for you to fetch changes up to 40f4b05868101e047a8502ebb94f05312186421b:
Merge remote-tracking branch 'regmap/for-6.3' into regmap-next (2023-02-17 02:14:50 +0000)
----------------------------------------------------------------
regmap: Updates for v6.3
A quiet release for regmap, we've seen several cleanups, an update for a
change in the MDIO APIs and one small fix.
----------------------------------------------------------------
Aidan MacDonald (2):
regmap-irq: Remove unused type_invert flag
regmap-irq: Remove unused mask_invert flag
Andrew Lunn (1):
regmap: Rework regmap_mdio_c45_{read|write} for new C45 API.
Christophe JAILLET (1):
regmap: Reorder fields in 'struct regmap_bus' to save some memory
Daniel Golle (1):
regmap: apply reg_base and reg_downshift for single register ops
Mark Brown (1):
Merge remote-tracking branch 'regmap/for-6.3' into regmap-next
drivers/base/regmap/regmap-irq.c | 25 ++----------------------
drivers/base/regmap/regmap-mdio.c | 41 ++++++++++++++++++++++-----------------
drivers/base/regmap/regmap.c | 6 ++++++
include/linux/regmap.h | 19 +++++++++---------
4 files changed, 41 insertions(+), 50 deletions(-)
next reply other threads:[~2023-02-20 14:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-20 14:33 Mark Brown [this message]
2023-02-22 19:53 ` [GIT PULL] regmap updates for v6.3 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=20230220143343.694A6C433D2@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 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.