| Message ID | 20200525133120.57273-1-broonie@kernel.org (mailing list archive) |
|---|---|
| State | Accepted |
| Commit | c373643b8688836c1627a805875994fe0012fc17 |
| Headers | show |
| Series | spi: Remove note about transfer limit for spi_write_then_read() | expand |
On Mon, 25 May 2020 14:31:20 +0100, Mark Brown wrote: > Originally spi_write_then_read() used a fixed statically allocated > buffer which limited the maximum message size it could handle. This > restriction was removed a while ago so that we could dynamically > allocate a buffer if required but the kerneldoc was not updated to > reflect this, do so. Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/1] spi: Remove note about transfer limit for spi_write_then_read() commit: c373643b8688836c1627a805875994fe0012fc17 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
diff --git a/drivers/spi/spi.c b/drivers/spi/spi.c index c69d23379e08..a6f3f1ae72d7 100644 --- a/drivers/spi/spi.c +++ b/drivers/spi/spi.c @@ -3869,8 +3869,7 @@ static u8 *buf; * is zero for success, else a negative errno status code. * This call may only be used from a context that may sleep. * - * Parameters to this routine are always copied using a small buffer; - * portable code should never use this for more than 32 bytes. + * Parameters to this routine are always copied using a small buffer. * Performance-sensitive or bulk transfer code should instead use * spi_{async,sync}() calls with dma-safe buffers. *
Originally spi_write_then_read() used a fixed statically allocated buffer which limited the maximum message size it could handle. This restriction was removed a while ago so that we could dynamically allocate a buffer if required but the kerneldoc was not updated to reflect this, do so. Reported-by: Marc Kleine-Budde <mkl@pengutronix.de> Signed-off-by: Mark Brown <broonie@kernel.org> --- drivers/spi/spi.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)