linux-kernel - Re: [PATCH 0/2] Cleanup chip info in spi-dw driver

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: <158705187475.53607.4216901757113789779.b4-ty@kernel.org>
Date:   Thu, 16 Apr 2020 16:45:07 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Clement Leger <cleger@...ray.eu>
Cc:     linux-kernel@...r.kernel.org, linux-spi@...r.kernel.org
Subject: Re: [PATCH 0/2] Cleanup chip info in spi-dw driver

On Thu, 16 Apr 2020 13:08:23 +0200, Clement Leger wrote:
> Some mechanisms have no more user, and as such code paths are unused.
> Remove these code paths and associated structs members.
> 
> Clement Leger (2):
>   spi: dw: remove unused dw_spi_chip handling
>   spi: dw: remove cs_control and poll_mode members from chip_data
> 
> [...]

Applied, thanks!

[1/2] spi: dw: remove unused dw_spi_chip handling
      commit: ae9e6ac4d8542d1b16fad4bd3c3e447632437623
[2/2] spi: dw: remove cs_control and poll_mode members from chip_data
      commit: 33e8fd4bfbd7eb0921eb55caceed54e51912a4e6

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