From: Mark Brown <broonie@kernel.org>
To: u0084500@gmail.com
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, chiaen_wu@richtek.com,
cy_huang@richtek.com, matthias.bgg@gmail.com,
lgirdwood@gmail.com, linux-mediatek@lists.infradead.org,
alice_chen@richtek.com
Subject: Re: [PATCH 1/2] regulator: mt6370: Use 'fwnode_gpiod_get_index' to fix gpio parsing
Date: Thu, 30 Jun 2022 12:30:14 +0100 [thread overview]
Message-ID: <165658861401.321126.9625331227015919731.b4-ty@kernel.org> (raw)
In-Reply-To: <1656466861-7737-1-git-send-email-u0084500@gmail.com>
On Wed, 29 Jun 2022 09:41:00 +0800, cy_huang wrote:
> From: ChiYuan Huang <cy_huang@richtek.com>
>
> From the common binding, 'enable-gpio' or 'enable-gpios' are all well
> for external 'enable' gpio.
>
> 'gpiod_get_from_of_node' only parse the 'enable' property, it need to
> add the gpio suffix. It's more convenient to use fwnode_gpiod_get_index.
> Although fwnode parsing is not preferred, but 'of_parse_cb' already can
> guarantee the callback will only be used by regulator of_node parsing.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/regulator.git for-next
Thanks!
[1/2] regulator: mt6370: Use 'fwnode_gpiod_get_index' to fix gpio parsing
commit: 4806c991bf4ff959acf921ea72f931a945a968ae
[2/2] regulator: mt6370: Use the correct header for platform_device_id
commit: 46ae6fb58fd49c4cb2d1ca34e87d603b7c96ba97
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:[~2022-06-30 11:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 1:41 cy_huang
2022-06-29 1:41 ` [PATCH 2/2] regulator: mt6370: Use the correct header for platform_device_id cy_huang
2022-06-29 8:23 ` AngeloGioacchino Del Regno
2022-06-29 8:23 ` [PATCH 1/2] regulator: mt6370: Use 'fwnode_gpiod_get_index' to fix gpio parsing AngeloGioacchino Del Regno
2022-06-29 9:02 ` ChiYuan Huang
2022-06-30 11:30 ` 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=165658861401.321126.9625331227015919731.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=alice_chen@richtek.com \
--cc=chiaen_wu@richtek.com \
--cc=cy_huang@richtek.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=u0084500@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
all inboxes | Powered by JetHome®