mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Aidan MacDonald <aidanmacdonald.0x0@gmail.com>
Cc: gregkh@linuxfoundation.org, rafael@kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/6] regmap-irq: Cleanups and remove unused functionality
Date: Thu, 11 May 2023 14:43:19 +0900	[thread overview]
Message-ID: <168378379961.328087.747032449434710098.b4-ty@kernel.org> (raw)
In-Reply-To: <20230509110100.3980123-1-aidanmacdonald.0x0@gmail.com>

On Tue, 09 May 2023 12:00:54 +0100, Aidan MacDonald wrote:
> This is a straightforward patch series, mostly just removing a bunch
> of old features that were only used by a handful of drivers.
> 
> - 1/6 is a documentation fix
> - 2/6, 3/6, and 4/6 remove unused, deprecated functionality
> - 5/6 makes the behavior of .handle_mask_sync() a bit more consistent
>   w.r.t. mask and unmask registers, to aid maintainability.
> - 6/6 removes now-unused "inverted mask/unmask" compatibility code.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regmap.git for-next

Thanks!

[1/6] regmap-irq: Fix typo in documentation for .get_irq_reg()
      commit: 212bc1ce618dd7c734920a68988fe4b473f09f40
[2/6] regmap-irq: Remove virtual registers
      commit: f33a751d5a7fe03b11d95e6a33e1fdd3b4f8ec18
[3/6] regmap-irq: Remove type registers
      (no commit info)
[4/6] regmap-irq: Remove support for not_fixed_stride
      (no commit info)
[5/6] regmap-irq: Minor adjustments to .handle_mask_sync()
      (no commit info)
[6/6] regmap-irq: Drop backward compatibility for inverted mask/unmask
      (no commit info)

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark


      parent reply	other threads:[~2023-05-11  5:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-09 11:00 Aidan MacDonald
2023-05-09 11:00 ` [PATCH v1 1/6] regmap-irq: Fix typo in documentation for .get_irq_reg() Aidan MacDonald
2023-05-09 11:00 ` [PATCH v1 2/6] regmap-irq: Remove virtual registers Aidan MacDonald
2023-05-09 11:00 ` [PATCH v1 3/6] regmap-irq: Remove type registers Aidan MacDonald
2023-05-11  1:24   ` Mark Brown
2023-05-11  9:09     ` Aidan MacDonald
2023-05-09 11:00 ` [PATCH v1 4/6] regmap-irq: Remove support for not_fixed_stride Aidan MacDonald
2023-05-09 11:00 ` [PATCH v1 5/6] regmap-irq: Minor adjustments to .handle_mask_sync() Aidan MacDonald
2023-05-09 11:01 ` [PATCH v1 6/6] regmap-irq: Drop backward compatibility for inverted mask/unmask Aidan MacDonald
2023-05-11  5:43 ` Mark Brown [this message]

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=168378379961.328087.747032449434710098.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=aidanmacdonald.0x0@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.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®