linux-kernel - Re: [PATCH] spi: bcm2835: implement ctlr->max_transfer

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: <170722135486.992289.5399586153021617257.b4-ty@kernel.org>
Date: Tue, 06 Feb 2024 12:09:14 +0000
From: Mark Brown <broonie@...nel.org>
To: Florian Fainelli <florian.fainelli@...adcom.com>, 
 Ray Jui <rjui@...adcom.com>, Scott Branden <sbranden@...adcom.com>, 
 David Lechner <dlechner@...libre.com>
Cc: Broadcom internal kernel review list <bcm-kernel-feedback-list@...adcom.com>, 
 linux-spi@...r.kernel.org, linux-rpi-kernel@...ts.infradead.org, 
 linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] spi: bcm2835: implement ctlr->max_transfer_size

On Fri, 26 Jan 2024 16:00:23 -0600, David Lechner wrote:
> The core SPI code will handle splitting transfers if needed as long
> as ctlr->max_transfer_size is implemented. It does this in
> __spi_pump_transfer_message() immediately before calling
> ctlr->prepare_message. So effectively, this change does not
> alter the behavior of the driver.
> 
> Also, several peripheral drivers make use of spi_max_transfer_size(),
> so this should improve compatibility with those drivers.
> 
> [...]

Applied to

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

Thanks!

[1/1] spi: bcm2835: implement ctlr->max_transfer_size
      commit: 2733092baa3e8a1f05fd16088808be17c98990b4

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