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.16
Date: Mon, 26 May 2025 11:29:47 +0100	[thread overview]
Message-ID: <4d6be2993d367094dcf8e574ee49b317.broonie@kernel.org> (raw)

The following changes since commit 0af2f6be1b4281385b618cb86ad946eded089ac8:

  Linux 6.15-rc1 (2025-04-06 13:11:33 -0700)

are available in the Git repository at:

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

for you to fetch changes up to 1c12fbdf40e17df2efc24bf2009a0c3bfa75bfa7:

  regmap: irq: Add support for chips without separate IRQ status (2025-05-22 13:11:50 +0100)

----------------------------------------------------------------
regmap: Updates for v6.16

This release we have one new feature, support for chips that report edge
interrupts but don't provide distinct readback of that status per line,
plus a few cleanups.

----------------------------------------------------------------
Andrew Davis (1):
      regmap: Move selecting for REGMAP_MDIO and REGMAP_IRQ

Andy Shevchenko (1):
      regmap-irq: Use dedicated interrupt wake setters

Mathieu Dubois-Briand (1):
      regmap: irq: Add support for chips without separate IRQ status

Thorsten Blum (1):
      regcache: Use sort()'s default swap() implementation

 drivers/base/regmap/Kconfig      |   4 +-
 drivers/base/regmap/regcache.c   |  13 +----
 drivers/base/regmap/regmap-irq.c | 103 ++++++++++++++++++++++++++-------------
 include/linux/regmap.h           |   3 ++
 4 files changed, 76 insertions(+), 47 deletions(-)

             reply	other threads:[~2025-05-26 10:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-26 10:29 Mark Brown [this message]
2025-05-28  0:30 ` [GIT PULL] regmap updates for v6.16 pr-tracker-bot
2025-05-28  0:30 ` 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=4d6be2993d367094dcf8e574ee49b317.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 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.