public inbox for linux-kernel@vger.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.8
Date: Sun, 07 Jan 2024 22:37:36 +0000	[thread overview]
Message-ID: <20240107223748.885ECC433C8@smtp.kernel.org> (raw)

The following changes since commit b85ea95d086471afb4ad062012a4d73cd328fa86:

  Linux 6.7-rc1 (2023-11-12 16:19:07 -0800)

are available in the Git repository at:

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

for you to fetch changes up to 3b201c9af7c0cad2e8311d96c0c1b399606c70fa:

  regmap: fix kcalloc() arguments order (2023-12-20 18:11:38 +0000)

----------------------------------------------------------------
regmap: Updates for v6.8

This was a very quiet release for regmap, we added kunit test coverage
for a noinc fix that was merged during v6.7 and a couple of other
trivial cleanups.

----------------------------------------------------------------
Ben Wolsieffer (2):
      regmap: ram: support noinc semantics
      regmap: kunit: add noinc write test

Dmitry Antipov (1):
      regmap: fix kcalloc() arguments order

Hugo Villeneuve (1):
      regmap: fix regmap_noinc_write() description

 drivers/base/regmap/internal.h       |  1 +
 drivers/base/regmap/regmap-kunit.c   | 60 ++++++++++++++++++++++++++++++++++++
 drivers/base/regmap/regmap-ram.c     |  4 +--
 drivers/base/regmap/regmap-raw-ram.c | 31 +++++++++++++------
 drivers/base/regmap/regmap.c         |  2 +-
 5 files changed, 85 insertions(+), 13 deletions(-)

             reply	other threads:[~2024-01-07 22:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-07 22:37 Mark Brown [this message]
2024-01-09 23:41 ` [GIT PULL] regmap updates for v6.8 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=20240107223748.885ECC433C8@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