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:     Jiaxin Yu <jiaxin.yu@mediatek.com>,
        angelogioacchino.delregno@collabora.com, dan.carpenter@oracle.com
Cc:     aaronyu@google.com, linux-arm-kernel@lists.infradead.org,
        linux-mediatek@lists.infradead.org,
        Project_Global_Chrome_Upstream_Group@mediatek.com,
        alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org
In-Reply-To: <20220726153130.27584-1-jiaxin.yu@mediatek.com>
References: <20220726153130.27584-1-jiaxin.yu@mediatek.com>
Subject: Re: [PATCH] ASoC: mediatek: mt8186: set the correct string to strncmp()
Message-Id: <165885780832.800364.7549018957037633100.b4-ty@kernel.org>
Date:   Tue, 26 Jul 2022 18:50:08 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Tue, 26 Jul 2022 23:31:30 +0800, Jiaxin Yu wrote:
> Fix Smatch static checker warning. strncmp() here only needs to compare
> the first seven bytes, so in order to make the code more clear, only the
> first seven bytes of the string used as the comparison are reserved.
> 
> Bug report: https://www.spinics.net/lists/alsa-devel/msg145608.html
> 
> sound/soc/mediatek/mt8186/mt8186-dai-adda.c:78 get_adda_priv_by_name()
> warn: strncmp() with weird length: 17 vs 7
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: mediatek: mt8186: set the correct string to strncmp()
      commit: 7df92384c86f36d0452e7abad21c7eaa91aeeef7

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