linux-kernel - Re: [PATCH -next] spi: fsl: Remove unused extern declarations

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: <169031149939.1603510.6271194546109675378.b4-ty@kernel.org>
Date:   Tue, 25 Jul 2023 19:58:19 +0100
From:   Mark Brown <broonie@...nel.org>
To:     YueHaibing <yuehaibing@...wei.com>
Cc:     linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH -next] spi: fsl: Remove unused extern declarations

On Tue, 25 Jul 2023 21:54:11 +0800, YueHaibing wrote:
> commit b36ece832512 ("spi/mpc8xxx: refactor the common code for SPI/eSPI controller")
> left mpc8xxx_spi_bufs() behind.
> And since commit 3c5395b66ff6 ("spi: fsl-(e)spi: simplify cleanup code")
> mpc8xxx_spi_remove() is not used anymore.
> 
> 

Applied to

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

Thanks!

[1/1] spi: fsl: Remove unused extern declarations
      commit: 7ad1c439fb25907dba31af5d66b44c6a3b999c89

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