linux-kernel - Re: [PATCH v2 0/3] spi: stm32-qspi: Remove unused parameters

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: <165459880493.302078.4977236000024044341.b4-ty@kernel.org>
Date:   Tue, 07 Jun 2022 11:46:44 +0100
From:   Mark Brown <broonie@...nel.org>
To:     alexandre.torgue@...s.st.com, patrice.chotard@...s.st.com
Cc:     linux-kernel@...r.kernel.org, christophe.kerello@...s.st.com,
        linux-arm-kernel@...ts.infradead.org, linux-spi@...r.kernel.org,
        linux-stm32@...md-mailman.stormreply.com
Subject: Re: [PATCH v2 0/3] spi: stm32-qspi: Remove unused parameters

On Thu, 2 Jun 2022 11:25:37 +0200, patrice.chotard@...s.st.com wrote:
> From: Patrice Chotard <patrice.chotard@...s.st.com>
> 
> This series cleans up spi-stm32-qspi driver by removing unused parameters
> 
> Changes since v1:
>   _ add missing patch which removes unused param for stm32_qspi_wait_poll_status()
> 
> [...]

Applied to

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

Thanks!

[1/3] spi: stm32-qspi: Remove stm32_qspi_get_mode() unused parameter
      commit: 5945ff905764ceba7eb721bac7f61c7c5ce16a50
[2/3] spi: stm32-qspi: Remove stm32_qspi_wait_cmd() unused parameter
      commit: 75c28a43a43f2c09f8feeb58413449d65a77968b
[3/3] spi: stm32-qspi: Remove stm32_qspi_wait_poll_status() unused parameter
      commit: 6ce7061a75f7edeebe8710502042810109698619

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