From: Mark Brown <broonie@kernel.org>
To: Liam Girdwood <lgirdwood@gmail.com>, Mark Brown <broonie@kernel.org>
Cc: linux-kernel@vger.kernel.org, Markus Reichl <m.reichl@fivetechno.de>
Subject: Re: [PATCH 0/8] regulator: mp8859: Cleanups and enhancements
Date: Tue, 27 Feb 2024 11:31:32 +0000 [thread overview]
Message-ID: <170903349247.16921.2831732986732449411.b4-ty@kernel.org> (raw)
In-Reply-To: <20240225-regulator-mp8859-v1-0-68ee2c839ded@kernel.org>
On Sun, 25 Feb 2024 14:59:26 +0000, Mark Brown wrote:
> I had cause to look at the MP8859 driver together with the datasheet and
> noticed a few small issues and missing features. This series deals with
> many of these issues, the device also has support for interrupts which
> are not implemented here.
>
>
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[1/8] regulator: mp8859: Specify register accessibility and enable caching
commit: b65e9149bdb76e9b09f6fb76fea1f10bde256619
[2/8] regulator: mp8859: Validate and log device identifier information
commit: 6c848d772eee0f03b72542f35e1a66469030390f
[3/8] regulator: mp8859: Support enable control
commit: b79d93d99e084bf1abafba2b7aabff6a06defcd0
[4/8] regulator: mp8859: Support mode operations
commit: 673d06a858864c7dca9dd5c36a78f5f7fda793af
[5/8] regulator: mp8859: Support active discharge control
commit: d7217c91bbde48ee60d3ce67cda6557f56c6b639
[6/8] regulator: mp8859: Support status and error readback
commit: 4317ecadbeeab5464a8c34b27b73e2d2f81ef718
[7/8] regulator: mp8859: Report slew rate
commit: 6df0921e9013622091c283aa2a5be8c5d1ca3642
[8/8] regulator: mp8859: Implement set_current_limit()
commit: c8e794cfb05344af7b9ae920b5548a25a7e91fe9
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
prev parent reply other threads:[~2024-02-27 11:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-25 14:59 Mark Brown
2024-02-25 14:59 ` [PATCH 1/8] regulator: mp8859: Specify register accessibility and enable caching Mark Brown
2024-02-25 14:59 ` [PATCH 2/8] regulator: mp8859: Validate and log device identifier information Mark Brown
2024-02-25 14:59 ` [PATCH 3/8] regulator: mp8859: Support enable control Mark Brown
2024-02-25 14:59 ` [PATCH 4/8] regulator: mp8859: Support mode operations Mark Brown
2024-02-25 14:59 ` [PATCH 5/8] regulator: mp8859: Support active discharge control Mark Brown
2024-02-25 14:59 ` [PATCH 6/8] regulator: mp8859: Support status and error readback Mark Brown
2024-02-25 14:59 ` [PATCH 7/8] regulator: mp8859: Report slew rate Mark Brown
2024-02-25 14:59 ` [PATCH 8/8] regulator: mp8859: Implement set_current_limit() Mark Brown
2024-02-26 8:14 ` [PATCH 0/8] regulator: mp8859: Cleanups and enhancements Markus Reichl
2024-02-27 11:31 ` 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=170903349247.16921.2831732986732449411.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.reichl@fivetechno.de \
/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®