mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: lgirdwood@gmail.com, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
	like@awinic.com
Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	liweilei@awinic.com, liangdong@awinic.com,
	wangweidong.a@awinic.com
Subject: Re: [PATCH v5 0/2] regulator: aw37503: add regulator driver for Awinic AW37503
Date: Tue, 22 Aug 2023 17:33:41 +0100	[thread overview]
Message-ID: <169272202114.71818.13706933583974169859.b4-ty@kernel.org> (raw)
In-Reply-To: <20230821035355.1269976-1-like@awinic.com>

On Mon, 21 Aug 2023 03:53:53 +0000, like@awinic.com wrote:
> Add regulator driver for the device Awinic AW37503 which is
> single inductor - dual output power supply device. AW37503
> device is designed to support general positive/negative
> driven applications like TFT display panels.
> 
> v4->v5: Delete the unnecessary '|' in the awinic,aw37503.yaml.
> v3->v4: Correct yamllint warnings/errors.
> v2->v3: Switch to use the dev_err_probe().
>         Keep the Kconfig and Makefile sorted.
>         Correct yamllint warnings/errors.
> v1->v2: Remove unneeded fields and correct yamllint warnings/errors.
> 
> [...]

Applied to

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

Thanks!

[1/2] regulator: aw37503: add regulator driver for Awinic AW37503
      commit: 2796a01cdf2c639e605088c53a1ac36923ade93c
[2/2] regulator: dt-bindings: Add Awinic AW37503
      commit: 86a1b61a0c7316febecd03d47eaf893eb5a57659

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:[~2023-08-22 16:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-21  3:53 like
2023-08-21  3:53 ` [PATCH v5 1/2] " like
2023-08-21  3:53 ` [PATCH v5 2/2] regulator: dt-bindings: Add " like
2023-08-21  6:04   ` Krzysztof Kozlowski
2023-08-22 16:33 ` 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=169272202114.71818.13706933583974169859.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=lgirdwood@gmail.com \
    --cc=liangdong@awinic.com \
    --cc=like@awinic.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liweilei@awinic.com \
    --cc=robh+dt@kernel.org \
    --cc=wangweidong.a@awinic.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®