All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: linux-kernel@vger.kernel.org, cy_huang@richtek.com,
	lgirdwood@gmail.com, robh+dt@kernel.org,
	krzysztof.kozlowski@linaro.org,
	krzysztof.kozlowski+dt@linaro.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v3 0/2] regulator: richtek,rt4801: parse GPIOs per regulator
Date: Mon, 25 Apr 2022 16:01:05 +0100	[thread overview]
Message-ID: <165089886500.211842.728549769223794277.b4-ty@kernel.org> (raw)
In-Reply-To: <20220425072455.27356-1-krzysztof.kozlowski@linaro.org>

On Mon, 25 Apr 2022 09:24:53 +0200, Krzysztof Kozlowski wrote:
> Not tested.
> 
> Follow up of discussion:
> https://lore.kernel.org/all/2d124d53-1f36-5315-3877-af8f8ad5f824@linaro.org/#t
> 
> Changes since v2
> ================
> Patch 2: Do not use core's ena_gpiod feature because of lost voltage issue
>          (ChiYuan Huang).
> 
> [...]

Applied to

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

Thanks!

[1/2] regulator: dt-bindings: richtek,rt4801: use existing ena_gpiod feature
      commit: a498db69dc6d7511d76a4f04ec19c5e378db1c3b
[2/2] regulator: richtek,rt4801: parse GPIOs per regulator
      commit: 6963569103c02b22076da245b19bd081d8da8f9e

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-04-25 15:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-25  7:24 [PATCH v3 0/2] regulator: richtek,rt4801: parse GPIOs per regulator Krzysztof Kozlowski
2022-04-25  7:24 ` [PATCH v3 1/2] regulator: dt-bindings: richtek,rt4801: use existing ena_gpiod feature Krzysztof Kozlowski
2022-04-25  7:24 ` [PATCH v3 2/2] regulator: richtek,rt4801: parse GPIOs per regulator Krzysztof Kozlowski
2022-04-25  7:58   ` ChiYuan Huang
2022-04-25  8:01     ` Krzysztof Kozlowski
2022-04-25  8:08       ` ChiYuan Huang
2022-04-25  8:50         ` ChiYuan Huang
2022-04-25 15:01 ` 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=165089886500.211842.728549769223794277.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=cy_huang@richtek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.