mirror of https://lore.kernel.org/lkml/
 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.17
Date: Mon, 28 Jul 2025 13:24:10 +0100	[thread overview]
Message-ID: <322b34fec942b961f17af6f02cb6b6a6.broonie@kernel.org> (raw)

The following changes since commit 19272b37aa4f83ca52bdf9c16d5d81bdd1354494:

  Linux 6.16-rc1 (2025-06-08 13:44:43 -0700)

are available in the Git repository at:

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

for you to fetch changes up to ffc72771ff6ec9f5b431a86c4b00d8ef0fea958b:

  regmap: Annotate that MMIO implies fast IO (2025-07-25 13:44:33 +0100)

----------------------------------------------------------------
regmap: Updates for v6.17

A very quiet release for regmap this time, just two cleanup patches and
one almost cleanup patch which saves individual MMIO regmaps flagging
themselves as having fast I/O.

----------------------------------------------------------------
Al Viro (1):
      regmap: get rid of redundant debugfs_file_{get,put}()

Krzysztof Kozlowski (1):
      regmap: kunit: Constify regmap_range_cfg array

Wolfram Sang (1):
      regmap: Annotate that MMIO implies fast IO

 drivers/base/regmap/regmap-debugfs.c | 10 ----------
 drivers/base/regmap/regmap-kunit.c   |  2 +-
 include/linux/regmap.h               |  8 ++++----
 3 files changed, 5 insertions(+), 15 deletions(-)

             reply	other threads:[~2025-07-28 12:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-28 12:24 Mark Brown [this message]
2025-07-29  6:50 ` 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=322b34fec942b961f17af6f02cb6b6a6.broonie@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

all inboxes | Powered by JetHome®