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:     Jiapeng Chong <jiapeng.chong@linux.alibaba.com>,
        oder_chiou@realtek.com
Cc:     Mark Brown <broonie@kernel.org>, lgirdwood@gmail.com,
        linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
        tiwai@suse.com
Subject: Re: [PATCH] ASoC: rt286: Remove redundant assignment to d_len_code
Date:   Tue, 11 May 2021 09:25:43 +0100
Message-Id: <162072058170.33157.14418303282464363989.b4-ty@kernel.org>
In-Reply-To: <1620298735-31708-1-git-send-email-jiapeng.chong@linux.alibaba.com>
References: <1620298735-31708-1-git-send-email-jiapeng.chong@linux.alibaba.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
Precedence: bulk

On Thu, 6 May 2021 18:58:55 +0800, Jiapeng Chong wrote:
> Variable d_len_code is set to zero, but this value is never read as
> it is overwritten or not used later on, hence it is a redundant
> assignment and can be removed.
> 
> Clean up the following clang-analyzer warning:
> 
> sound/soc/codecs/rt286.c:728:2: warning: Value stored to 'd_len_code' is
> never read [clang-analyzer-deadcode.DeadStores].

Applied to

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

Thanks!

[1/1] ASoC: rt286: Remove redundant assignment to d_len_code
      commit: 1d122dd3b168f55e2e29982cff80f1c15f66ef26

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