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;
Date:   Fri, 25 Sep 2020 21:42:01 +0100
From:   Mark Brown <broonie@kernel.org>
To:     lgirdwood@gmail.com, tiwai@suse.com,
        linux-arm-kernel@lists.infradead.org, festevam@gmail.com,
        Xiubo.Lee@gmail.com, linuxppc-dev@lists.ozlabs.org,
        nicoleotsuka@gmail.com, shawnguo@kernel.org, perex@perex.cz,
        linux-imx@nxp.com, s.hauer@pengutronix.de,
        Xu Wang <vulab@iscas.ac.cn>, shengjiu.wang@gmail.com,
        alsa-devel@alsa-project.org, kernel@pengutronix.de,
        timur@kernel.org
Cc:     linux-kernel@vger.kernel.org
In-Reply-To: <20200921015918.24157-1-vulab@iscas.ac.cn>
References: <20200921015918.24157-1-vulab@iscas.ac.cn>
Subject: Re: [PATCH] fsl: imx-audmix : Use devm_kcalloc() instead of devm_kzalloc()
Message-Id: <160106647647.2866.12055149870190769449.b4-ty@kernel.org>
Precedence: bulk

On Mon, 21 Sep 2020 01:59:18 +0000, Xu Wang wrote:
> A multiplication for the size determination of a memory allocation
> indicated that an array data structure should be processed.
> Thus use the corresponding function "devm_kcalloc".

Applied to

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

Thanks!

[1/1] ASoC: fsl: imx-audmix: Use devm_kcalloc() instead of devm_kzalloc()
      commit: f95cc5c18c15a425c3dceec48df6b4e27a202dda

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