From: Mark Brown <broonie@kernel.org>
To: Peter Geis <pgwipeout@gmail.com>, Liam Girdwood <lgirdwood@gmail.com>
Cc: Mark Brown <broonie@kernel.org>,
linux-kernel@vger.kernel.org,
Ezequiel Garcia <ezequiel@collabora.com>
Subject: Re: [PATCH 0/3] regulator: fan53555: tcs4525 fix and cleanup
Date: Wed, 12 May 2021 18:04:40 +0100 [thread overview]
Message-ID: <162083902381.44966.4390626020202703159.b4-ty@kernel.org> (raw)
In-Reply-To: <20210511211335.2935163-1-pgwipeout@gmail.com>
On Tue, 11 May 2021 17:13:32 -0400, Peter Geis wrote:
> The tcs4525 voltage calculation is incorrect, which leads to a deadlock
> on the rk3566-quartz64 board when loading cpufreq.
> Fix the voltage calculation to correct the deadlock.
> While we are at it, add a safety check and clean up the function names
> to be more accurate.
>
> Peter Geis (3):
> regulator: fan53555: fix TCS4525 voltage calulation
> regulator: fan53555: only bind tcs4525 to correct chip id
> regulator: fan53555: fix tcs4525 function names
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[1/3] regulator: fan53555: fix TCS4525 voltage calulation
commit: f8c8871f5eff3981eeb13421aca2c1cfda4a5204
[2/3] regulator: fan53555: only bind tcs4525 to correct chip id
commit: f9028dcdf589f4ab528372088623aa4e8d324df2
[3/3] regulator: fan53555: fix tcs4525 function names
commit: b3cc8ec04f50d9c860534fe4e3617a8d10ed9ea9
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
next prev parent reply other threads:[~2021-05-12 19:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-11 21:13 [PATCH 0/3] regulator: fan53555: tcs4525 fix and cleanup Peter Geis
2021-05-11 21:13 ` [PATCH 1/3] regulator: fan53555: fix TCS4525 voltage calulation Peter Geis
2021-05-11 21:13 ` [PATCH 2/3] regulator: fan53555: only bind tcs4525 to correct chip id Peter Geis
2021-05-11 21:13 ` [PATCH 3/3] regulator: fan53555: fix tcs4525 function names Peter Geis
2021-05-12 17:04 ` Mark Brown [this message]
2021-05-13 17:23 ` [PATCH 0/3] regulator: fan53555: tcs4525 fix and cleanup Ezequiel Garcia
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=162083902381.44966.4390626020202703159.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=ezequiel@collabora.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pgwipeout@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).