mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: krzysztof.kozlowski+dt@linaro.org, lgirdwood@gmail.com,
	Jerome Neanne <jneanne@baylibre.com>,
	robh+dt@kernel.org
Cc: linux-kernel@vger.kernel.org, khilman@baylibre.com,
	msp@baylibre.com, devicetree@vger.kernel.org
Subject: Re: [PATCH 0/2] Add input_supply support in gpio_regulator_config
Date: Thu, 29 Sep 2022 16:52:08 +0100	[thread overview]
Message-ID: <166446672840.175965.2897291078173491886.b4-ty@kernel.org> (raw)
In-Reply-To: <20220929132526.29427-1-jneanne@baylibre.com>

On Thu, 29 Sep 2022 15:25:24 +0200, Jerome Neanne wrote:
> This is simillar needs and implementation as fixed-regulator.
> Used to extract regulator parent from the device tree.
> 
> Provide implementation and bindings for vin-supply property.
> 
> Jerome Neanne (2):
>   regulator: gpio: Add input_supply support in gpio_regulator_config
>   dt-bindings: gpio-regulator: add vin-supply property support
> 
> [...]

Applied to

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

Thanks!

[1/2] regulator: gpio: Add input_supply support in gpio_regulator_config
      commit: adfdfcbdbd32b356323a3db6d3a683270051a7e6
[2/2] dt-bindings: gpio-regulator: add vin-supply property support
      commit: 392cc0a4a0c4b25534f3148b192f18be468f67bd

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:[~2022-09-29 15:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-29 13:25 Jerome Neanne
2022-09-29 13:25 ` [PATCH 1/2] regulator: gpio: " Jerome Neanne
2022-09-29 13:25 ` [PATCH 2/2] dt-bindings: gpio-regulator: add vin-supply property support Jerome Neanne
2022-09-29 15:52 ` 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=166446672840.175965.2897291078173491886.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jneanne@baylibre.com \
    --cc=khilman@baylibre.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=msp@baylibre.com \
    --cc=robh+dt@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®