Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   Mark Brown <broonie@kernel.org>
To:     tiwai@suse.com, ckeepax@opensource.cirrus.com, krzk@kernel.org,
        geert@linux-m68k.org, srinivas.kandagatla@linaro.org,
        linux-kernel@vger.kernel.org, perex@perex.cz,
        rf@opensource.wolfsonmicro.com, lgirdwood@gmail.com,
        nuno.sa@analog.com, alsa-devel@alsa-project.org,
        jack.yu@realtek.com, shumingf@realtek.com,
        Steve Lee <steves.lee@maximintegrated.com>
Cc:     Mark Brown <broonie@kernel.org>, ryan.lee.maxim@gmail.com,
        steves.lee.maxim@gmail.com
Subject: Re: [PATCH] ASoC: max98390: Add support for tx slot configuration.
Date:   Tue,  6 Apr 2021 18:39:37 +0100
Message-Id: <161773049108.51713.10192288839186913998.b4-ty@kernel.org>
In-Reply-To: <20210405143801.29770-1-steves.lee@maximintegrated.com>
References: <20210405143801.29770-1-steves.lee@maximintegrated.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Mon, 5 Apr 2021 23:38:01 +0900, Steve Lee wrote:
>  Update voltage/current tx slot configuration support.

Applied to

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

Thanks!

[1/1] ASoC: max98390: Add support for tx slot configuration.
      commit: e5870bd0e40c749fd96a4e565497c789bee456bf

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