linux-kernel - Re: [PATCH v2] ASoC: SOF: imx: Fix devm_ioremap

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: <175682023505.513793.6818545507364756748.b4-ty@kernel.org>
Date: Tue, 02 Sep 2025 14:37:15 +0100
From: Mark Brown <broonie@...nel.org>
To: Daniel Baluta <daniel.baluta@....com>
Cc: linux-sound@...r.kernel.org, imx@...ts.linux.dev, 
 linux-kernel@...r.kernel.org, Frank.Li@....com, robh@...nel.org, 
 laurentiu.mihalcea@....com, dan.carpenter@...aro.org, waqar.hameed@...s.com, 
 festevam@...il.com, kernel@...gutronix.de, lgirdwood@...il.com, 
 peter.ujfalusi@...ux.intel.com, yung-chuan.liao@...ux.intel.com, 
 ranjani.sridharan@...ux.intel.com, kai.vehmanen@...ux.intel.com
Subject: Re: [PATCH v2] ASoC: SOF: imx: Fix devm_ioremap_resource check

On Tue, 02 Sep 2025 13:21:00 +0300, Daniel Baluta wrote:
> devm_ioremap_resource does not return NULL on error
> but an error pointer so we need to use IS_ERR to check
> the return code.
> 
> While at it also pass the error code to dev_err_probe
> to improve logging.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: SOF: imx: Fix devm_ioremap_resource check
      commit: 0c28431f6fe13f3a3be0978f79c1a7ae8a93d028

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