linux-kernel - Re: [PATCH next] spi: spi_amd: Fix an IS

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <174422993445.1502711.4345013913869460825.b4-ty@kernel.org>
Date: Wed, 09 Apr 2025 21:18:54 +0100
From: Mark Brown <broonie@...nel.org>
To: Raju Rangoju <Raju.Rangoju@....com>, 
 Dan Carpenter <dan.carpenter@...aro.org>
Cc: Akshata MukundShetty <akshata.mukundshetty@....com>, 
 Krishnamoorthi M <krishnamoorthi.m@....com>, linux-spi@...r.kernel.org, 
 linux-kernel@...r.kernel.org, kernel-janitors@...r.kernel.org
Subject: Re: [PATCH next] spi: spi_amd: Fix an IS_ERR() vs NULL check in
 probe

On Wed, 09 Apr 2025 14:00:35 +0300, Dan Carpenter wrote:
> The devm_ioremap() function returns NULL on error, it doesn't
> return error pointers.  Update the error checking to match.
> 
> 

Applied to

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

Thanks!

[1/1] spi: spi_amd: Fix an IS_ERR() vs NULL check in probe
      commit: e686365c0411275474527c2055ac133f2eb47526

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