linux-kernel - Re: [PATCH] spi: spi-zynq-qspi: Fix some wrong goto jumps & missing error code

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: <162265058628.22666.9665445837542581247.b4-ty@kernel.org>
Date:   Wed,  2 Jun 2021 17:16:47 +0100
From:   Mark Brown <broonie@...nel.org>
To:     linux-kernel@...r.kernel.org, zpershuai <zpershuai@...il.com>,
        Michal Simek <michal.simek@...inx.com>,
        linux-spi@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Cc:     Mark Brown <broonie@...nel.org>
Subject: Re: [PATCH] spi: spi-zynq-qspi: Fix some wrong goto jumps & missing error code

On Thu, 27 May 2021 18:20:57 +0800, zpershuai wrote:
> In zynq_qspi_probe function, when enable the device clock is done,
> the return of all the functions should goto the clk_dis_all label.
> 
> If num_cs is not right then this should return a negative error
> code but currently it returns success.

Applied to

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

Thanks!

[1/1] spi: spi-zynq-qspi: Fix some wrong goto jumps & missing error code
      commit: f131767eefc47de2f8afb7950cdea78397997d66

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