linux-kernel - Re: [PATCH] spi: spi-fsl-dspi: delete EOQ transfer mode

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: <159827591891.48232.1958676153438917876.b4-ty@kernel.org>
Date:   Mon, 24 Aug 2020 14:32:03 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Vladimir Oltean <olteanv@...il.com>
Cc:     linux-kernel@...r.kernel.org, angelo.dureghello@...esys.com,
        linux-spi@...r.kernel.org
Subject: Re: [PATCH] spi: spi-fsl-dspi: delete EOQ transfer mode

On Mon, 24 Aug 2020 00:26:57 +0300, Vladimir Oltean wrote:
> After the only user of the limited EOQ mode has now been converted to
> DMA as of commit b09058bbf5f0 ("spi: spi-fsl-dspi: set ColdFire to DMA
> mode"), we can finally delete this code.

Applied to

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

Thanks!

[1/1] spi: spi-fsl-dspi: delete EOQ transfer mode
      commit: 20c05a05506361a6c355e9944d5616f5ed1e01c8

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