Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Mark Brown <broonie@kernel.org>
To:     peter.ujfalusi@linux.intel.com, Chunxu Li <chunxu.li@mediatek.com>,
        lgirdwood@gmail.com, angelogioacchino.delregno@collabora.com,
        daniel.baluta@nxp.com, pierre-louis.bossart@linux.intel.com
Cc:     matthias.bgg@gmail.com, sound-open-firmware@alsa-project.org,
        alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
        linux-mediatek@lists.infradead.org, yc.hung@mediatek.com,
        linux-arm-kernel@lists.infradead.org,
        project_global_chrome_upstream_group@mediatek.com
In-Reply-To: <20220917022610.594-1-chunxu.li@mediatek.com>
References: <20220917022610.594-1-chunxu.li@mediatek.com>
Subject: Re: [PATCH] ASoC: SOF: mediatek: add pcm_hw_params callback for mt8186
Message-Id: <166370679567.361668.2078852324764910878.b4-ty@kernel.org>
Date:   Tue, 20 Sep 2022 21:46:35 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Sat, 17 Sep 2022 10:26:10 +0800, Chunxu Li wrote:
> add pcm_hw_params callback for mt8186 to support continue
> update dma host position
> 
> 

Applied to

   broonie/sound.git for-next

Thanks!

[1/1] ASoC: SOF: mediatek: add pcm_hw_params callback for mt8186
      commit: 78091edc1c7806846049e1d480f6a8051507ed94

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