linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Rob Herring <robh+dt@kernel.org>,
	Adam Ward <Adam.Ward.opensource@diasemi.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	Vincent Whitchurch <vincent.whitchurch@axis.com>,
	devicetree@vger.kernel.org,
	Support Opensource <support.opensource@diasemi.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3 00/10] regulator: da9121: extend support to variants, add features
Date: Tue, 01 Dec 2020 13:57:56 +0000	[thread overview]
Message-ID: <160683107677.35139.1688443189294014005.b4-ty@kernel.org> (raw)
In-Reply-To: <cover.1606755367.git.Adam.Ward.opensource@diasemi.com>

On Mon, 30 Nov 2020 16:59:04 +0000, Adam Ward wrote:
> This series extends the DA9121 driver to add support for related products:
> 
>   DA9130, 10A, Dual-Phase (Automotive Grade)
>   DA9122, 5A + 5A
>   DA9131, 5A + 5A (Automotive Grade)
>   DA9220, 3A + 3A
>   DA9132, 3A + 3A (Automotive Grade)
>   DA9217, 6A, Dual-Phase
> 
> [...]

Applied to

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

Thanks!

[01/10] regulator: Update DA9121 dt-bindings
        (no commit info)
[02/10] regulator: da9121: Add header file
        (no commit info)
[03/10] regulator: da9121: Add device variants
        (no commit info)
[04/10] regulator: da9121: Add device variant regmaps
        (no commit info)
[05/10] regulator: da9121: Add device variant descriptors
        (no commit info)
[06/10] regulator: da9121: Add support for device variants via devicetree
        (no commit info)
[07/10] regulator: da9121: Update registration to support multiple buck variants
        (no commit info)
[08/10] regulator: da9121: add current support
        (no commit info)
[09/10] regulator: da9121: add mode support
        (no commit info)
[10/10] regulator: da9121: add interrupt support
        (no commit info)

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:[~2020-12-01 13:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-30 16:59 [PATCH V3 00/10] regulator: da9121: extend support to variants, add features Adam Ward
2020-11-30 16:59 ` [PATCH V3 01/10] regulator: Update DA9121 dt-bindings Adam Ward
2020-11-30 16:59 ` [PATCH V3 02/10] regulator: da9121: Add header file Adam Ward
2020-11-30 16:59 ` [PATCH V3 03/10] regulator: da9121: Add device variants Adam Ward
2020-11-30 16:59 ` [PATCH V3 04/10] regulator: da9121: Add device variant regmaps Adam Ward
2020-11-30 16:59 ` [PATCH V3 05/10] regulator: da9121: Add device variant descriptors Adam Ward
2020-11-30 16:59 ` [PATCH V3 06/10] regulator: da9121: Add support for device variants via devicetree Adam Ward
2020-11-30 16:59 ` [PATCH V3 07/10] regulator: da9121: Update registration to support multiple buck variants Adam Ward
2020-11-30 16:59 ` [PATCH V3 08/10] regulator: da9121: add current support Adam Ward
2020-11-30 16:59 ` [PATCH V3 09/10] regulator: da9121: add mode support Adam Ward
2020-11-30 16:59 ` [PATCH V3 10/10] regulator: da9121: add interrupt support Adam Ward
2020-12-01 13:57 ` Mark Brown [this message]
2020-12-01 16:51   ` [PATCH V3 00/10] regulator: da9121: extend support to variants, add features Adam Thomson
2020-12-01 16:55     ` Mark Brown

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=160683107677.35139.1688443189294014005.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=Adam.Ward.opensource@diasemi.com \
    --cc=devicetree@vger.kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=support.opensource@diasemi.com \
    --cc=vincent.whitchurch@axis.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;
as well as URLs for NNTP newsgroup(s).