linux-kernel - Re: [PATCH v1 0/1] spi: spi-gxp: BUG: Correct spi write return value

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: <169589012541.2716525.12263477961965733985.b4-ty@kernel.org>
Date:   Thu, 28 Sep 2023 10:35:25 +0200
From:   Mark Brown <broonie@...nel.org>
To:     verdun@....com, nick.hawkins@....com, linux-spi@...r.kernel.org,
        linux-kernel@...r.kernel.org, charles.kearney@....com
Subject: Re: [PATCH v1 0/1] spi: spi-gxp: BUG: Correct spi write return
 value

On Wed, 20 Sep 2023 21:53:38 +0000, charles.kearney@....com wrote:
> Bug fix to correct return value of gxp_spi_write function to zero.
> Completion of succesful operation should return zero.
> 
> Fixes: 730bc8ba5e9e spi: spi-gxp: Add support for HPE GXP SoCs
> 
> Charles Kearney (1):
>   spi: spi-gxp: BUG: Correct spi write return value
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: spi-gxp: BUG: Correct spi write return value
      commit: 1a8196a93e493c0a50b800cb09cef60b124eee15

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