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:     cgel.zte@gmail.com
Cc:     ranjani.sridharan@linux.intel.com,
        ye xingchen <ye.xingchen@zte.com.cn>,
        linux-kernel@vger.kernel.org, sound-open-firmware@alsa-project.org,
        tiwai@suse.com, pierre-louis.bossart@linux.intel.com,
        perex@perex.cz, kai.vehmanen@linux.intel.com,
        Zeal Robot <zealci@zte.com.cn>, alsa-devel@alsa-project.org,
        lgirdwood@gmail.com, daniel.baluta@nxp.com,
        yung-chuan.liao@linux.intel.com, peter.ujfalusi@linux.intel.com
In-Reply-To: <20220916062511.153962-1-ye.xingchen@zte.com.cn>
References: <20220916062511.153962-1-ye.xingchen@zte.com.cn>
Subject: Re: [PATCH linux-next] ASOC: SOF: use devm_kcalloc() instead of devm_kzalloc()
Message-Id: <166362900561.3419825.13047486503989578103.b4-ty@kernel.org>
Date:   Tue, 20 Sep 2022 00:10:05 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Fri, 16 Sep 2022 06:25:11 +0000, cgel.zte@gmail.com wrote:
> From: ye xingchen <ye.xingchen@zte.com.cn>
> 
> Use 2-factor multiplication argument form devm_kcalloc() instead
> of devm_kzalloc().
> 
> 

Applied to

   broonie/sound.git for-next

Thanks!

[1/1] ASOC: SOF: use devm_kcalloc() instead of devm_kzalloc()
      commit: 7b88552c26971ccbc6ff35e9d544f7fac94ffef1

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