linux-kernel - Re: [PATCH] spi: uniphier: Fix a bug that doesn't point to private data correctly

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] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 22 Dec 2021 14:04:47 +0000
From:   Mark Brown <broonie@...nel.org>
To:     Kunihiko Hayashi <hayashi.kunihiko@...ionext.com>
Cc:     stable@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
        linux-kernel@...r.kernel.org,
        Masami Hiramatsu <mhiramat@...nel.org>,
        linux-spi@...r.kernel.org,
        Keiji Hayashibara <hayashibara.keiji@...ionext.com>
Subject: Re: [PATCH] spi: uniphier: Fix a bug that doesn't point to private data correctly

On Wed, 22 Dec 2021 13:48:12 +0900, Kunihiko Hayashi wrote:
> In uniphier_spi_remove(), there is a wrong code to get private data from
> the platform device, so the driver can't be removed properly.
> 
> The driver should get spi_master from the platform device and retrieve
> the private data from it.
> 
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: uniphier: Fix a bug that doesn't point to private data correctly
      commit: 80bb73a9fbcde4ecc55e12f10c73fabbe68a24d1

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