[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <174231137374.151099.386870711250177057.b4-ty@kernel.org>
Date: Tue, 18 Mar 2025 15:22:53 +0000
From: Mark Brown <broonie@...nel.org>
To: Longbin Li <looong.bin@...il.com>,
Dan Carpenter <dan.carpenter@...aro.org>
Cc: linux-kernel@...r.kernel.org, linux-spi@...r.kernel.org
Subject: Re: [PATCH 0/2] spi: sg2044-nor: fix a couple static checker bugs
On Fri, 14 Mar 2025 13:10:04 +0300, Dan Carpenter wrote:
> Here are two fixes for Smatch warnings.
>
> Dan Carpenter (2):
> spi: sg2044-nor: fix signedness bug in sg2044_spifmc_write()
> spi: sg2044-nor: Fix uninitialized variable in probe
>
> drivers/spi/spi-sg2044-nor.c | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/2] spi: sg2044-nor: fix signedness bug in sg2044_spifmc_write()
commit: 16c6cac2463d57d3dc15057937fd7aedacff656e
[2/2] spi: sg2044-nor: fix uninitialized variable in probe
commit: a1d8f70954f69e333b252795808164839bb2e7cf
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
Powered by blists - more mailing lists