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, lgirdwood@gmail.com, lars@metafoo.de,
        linux-kernel@vger.kernel.org,
        Shengjiu Wang <shengjiu.wang@nxp.com>, perex@perex.cz,
        alsa-devel@alsa-project.org
In-Reply-To: <1642646642-15908-1-git-send-email-shengjiu.wang@nxp.com>
References: <1642646642-15908-1-git-send-email-shengjiu.wang@nxp.com>
Subject: Re: [PATCH] ASoC: soc-generic-dmaengine-pcm: separate max_buffer_size assignment
Message-Id: <164310603029.74844.18163154288522285277.b4-ty@kernel.org>
Date:   Tue, 25 Jan 2022 10:20:30 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Thu, 20 Jan 2022 10:44:02 +0800, Shengjiu Wang wrote:
> The config->pcm_hardware may be NULL when config->prealloc_buffer_size
> is not zero, so it is better to move max_buffer_size assignment under
> a separate condition.
> 
> 

Applied to

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

Thanks!

[1/1] ASoC: soc-generic-dmaengine-pcm: separate max_buffer_size assignment
      commit: 88c62b16281e5fe748f22f44da3def8a91fb1c34

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