All of lore.kernel.org
 help / color / mirror / Atom feed
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.9
Date: Mon, 11 Mar 2024 15:12:40 +0000	[thread overview]
Message-ID: <20240311151253.0E617C43390@smtp.kernel.org> (raw)

The following changes since commit 6613476e225e090cc9aad49be7fa504e290dd33d:

  Linux 6.8-rc1 (2024-01-21 14:11:32 -0800)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git tags/regmap-v6.9

for you to fetch changes up to bb92804ba2b6636e28db05f589a9a8ef62a07917:

  regmap: kunit: Add a test for ranges in combination with windows (2024-02-26 13:46:24 +0000)

----------------------------------------------------------------
regmap: Updates for v6.9

Just two updates this time around, a rework of max_register handling
which enables us to support devices with only one register better and a
new test which will be used to validate use of some new SPI
optimisations which will be coming in during this merge window.

----------------------------------------------------------------
Jan Dakinevich (1):
      regmap: rework ->max_register handling

Mark Brown (1):
      regmap: kunit: Add a test for ranges in combination with windows

 drivers/base/regmap/internal.h      |  1 +
 drivers/base/regmap/regcache-flat.c |  2 +-
 drivers/base/regmap/regcache.c      |  4 ++-
 drivers/base/regmap/regmap-kunit.c  | 66 +++++++++++++++++++++++++++++++++++++
 drivers/base/regmap/regmap.c        | 10 +++---
 include/linux/regmap.h              |  5 +++
 6 files changed, 82 insertions(+), 6 deletions(-)

             reply	other threads:[~2024-03-11 15:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-11 15:12 Mark Brown [this message]
2024-03-13 19:28 ` [GIT PULL] regmap updates for v6.9 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=20240311151253.0E617C43390@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.