From: Mark Brown <broonie@kernel.org>
To: Robin Gong <yibin.gong@nxp.com>,
lgirdwood@gmail.com, Christophe.Meynard@ign.fr,
Anson.Huang@nxp.com
Cc: linux-kernel@vger.kernel.org, linux-imx@nxp.com
Subject: Re: [PATCH v1] regualtor: pfuze100: correct sw1a/sw2 on pfuze3000
Date: Mon, 15 Jun 2020 16:06:01 +0100 [thread overview]
Message-ID: <159223356166.9065.14796356122373184238.b4-ty@kernel.org> (raw)
In-Reply-To: <1592171648-8752-1-git-send-email-yibin.gong@nxp.com>
On Mon, 15 Jun 2020 05:54:08 +0800, Robin Gong wrote:
> PFUZE100_SWB_REG is not proper for sw1a/sw2, because enable_mask/enable_reg
> is not correct. On PFUZE3000, sw1a/sw2 should be the same as sw1a/sw2 on
> pfuze100 except that voltages are not linear, so add new PFUZE3000_SW_REG
> and pfuze3000_sw_regulator_ops which like the non-linear PFUZE100_SW_REG
> and pfuze100_sw_regulator_ops.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[1/1] regualtor: pfuze100: correct sw1a/sw2 on pfuze3000
commit: 6f1cf5257acc6e6242ddf2f52bc7912aed77b79f
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:[~2020-06-15 15:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-14 21:54 [PATCH v1] regualtor: pfuze100: correct sw1a/sw2 on pfuze3000 Robin Gong
2020-06-15 15:06 ` 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=159223356166.9065.14796356122373184238.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=Anson.Huang@nxp.com \
--cc=Christophe.Meynard@ign.fr \
--cc=lgirdwood@gmail.com \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yibin.gong@nxp.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 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.