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 v5.18
Date: Mon, 21 Mar 2022 12:35:29 +0000	[thread overview]
Message-ID: <20220321123541.37912C340E8@smtp.kernel.org> (raw)

The following changes since commit e783362eb54cd99b2cac8b3a9aeac942e6f6ac07:

  Linux 5.17-rc1 (2022-01-23 10:12:53 +0200)

are available in the Git repository at:

  https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git tags/regmap-v5.18

for you to fetch changes up to 0074f3f2b1e43d3cedd97e47fb6980db6d2ba79e:

  regmap: allow a defined reg_base to be added to every address (2022-03-18 16:53:19 +0000)

----------------------------------------------------------------
regmap: Updates for v5.18

A couple of small fixes, plus some new features that enable us to handle
devices that reformat register addresses depending on the bus used to
handle the control interface more gracefully.

----------------------------------------------------------------
Colin Foster (2):
      regmap: add configurable downshift for addresses
      regmap: allow a defined reg_base to be added to every address

Luca Ceresoli (1):
      regmap-irq: Fix typo in comment

Tom Rix (1):
      regmap: irq: cleanup comments

 drivers/base/regmap/internal.h   |  2 ++
 drivers/base/regmap/regmap-irq.c |  6 +++---
 drivers/base/regmap/regmap.c     | 11 +++++++++++
 include/linux/regmap.h           |  6 ++++++
 4 files changed, 22 insertions(+), 3 deletions(-)

             reply	other threads:[~2022-03-21 12:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-21 12:35 Mark Brown [this message]
2022-03-22  1:39 ` 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=20220321123541.37912C340E8@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

all inboxes | Powered by JetHome®