Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:8 as permitted sender) client-ip=2620:137:e000::3:8;
From:   Mark Brown <broonie@kernel.org>
To:     David Lin <CTLIN0@nuvoton.com>
Cc:     lgirdwood@gmail.com, alsa-devel@alsa-project.org,
        linux-kernel@vger.kernel.org, YHCHuang@nuvoton.com,
        KCHSU0@nuvoton.com, WTLI@nuvoton.com, SJLIN0@nuvoton.com,
        ctlin0.linux@gmail.com, kernel test robot <lkp@intel.com>
In-Reply-To: <20231117043011.1747594-1-CTLIN0@nuvoton.com>
References: <20231117043011.1747594-1-CTLIN0@nuvoton.com>
Subject: Re: [PATCH] ASoC: nau8822: Fix incorrect type in assignment and
 cast to restricted __be16
Message-Id: <170023935469.1567036.15285427485660372538.b4-ty@kernel.org>
Date:   Fri, 17 Nov 2023 16:42:34 +0000
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Fri, 17 Nov 2023 12:30:12 +0800, David Lin wrote:
> This issue is reproduced when W=1 build in compiler gcc-12.
> The following are sparse warnings:
> 
> sound/soc/codecs/nau8822.c:199:25: sparse: sparse: incorrect type in assignment
> sound/soc/codecs/nau8822.c:199:25: sparse: expected unsigned short
> sound/soc/codecs/nau8822.c:199:25: sparse: got restricted __be16
> sound/soc/codecs/nau8822.c:235:25: sparse: sparse: cast to restricted __be16
> sound/soc/codecs/nau8822.c:235:25: sparse: sparse: cast to restricted __be16
> sound/soc/codecs/nau8822.c:235:25: sparse: sparse: cast to restricted __be16
> sound/soc/codecs/nau8822.c:235:25: sparse: sparse: cast to restricted __be16
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: nau8822: Fix incorrect type in assignment and cast to restricted __be16
      commit: c1501f2597dd08601acd42256a4b0a0fc36bf302

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