linux-kernel - Re: [PATCH] spi: microchip-core: Simplify some error message

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: <166057829988.697678.13235950902894348859.b4-ty@kernel.org>
Date:   Mon, 15 Aug 2022 16:44:59 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Yang Yingliang <yangyingliang@...wei.com>,
        Christophe JAILLET <christophe.jaillet@...adoo.fr>,
        Daire McNamara <daire.mcnamara@...rochip.com>,
        Conor Dooley <conor.dooley@...rochip.com>
Cc:     linux-kernel@...r.kernel.org, linux-riscv@...ts.infradead.org,
        kernel-janitors@...r.kernel.org, linux-spi@...r.kernel.org
Subject: Re: [PATCH] spi: microchip-core: Simplify some error message

On Fri, 5 Aug 2022 23:33:17 +0200, Christophe JAILLET wrote:
> dev_err_probe() already prints the error code in a human readable way, so
> there is no need to duplicate it as a numerical value at the end of the
> message.
> 
> Moreover, in the case of devm_clk_get() it would only display '0' because
> 'ret' is know to be 0 at this point.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: microchip-core: Simplify some error message
      commit: 7964e817d2311b37b86d6fbf588cd9fbe747b108

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