summaryrefslogtreecommitdiffstats
path: root/include/linux
diff options
context:
space:
mode:
authorDavid Lechner <dlechner@baylibre.com>2024-01-31 11:07:27 -0600
committerMark Brown <broonie@kernel.org>2024-01-31 17:10:25 +0000
commite6c5812dc4d0b3e890608cb9c98597d1bed7e937 (patch)
tree29097209a075eb155ff1b8426a8f07dcf4336ae2 /include/linux
parent8613dda6af8ee1e8675a37c86bf8d4661d24bf14 (diff)
downloadlinux-stable-e6c5812dc4d0b3e890608cb9c98597d1bed7e937.tar.gz
linux-stable-e6c5812dc4d0b3e890608cb9c98597d1bed7e937.tar.bz2
linux-stable-e6c5812dc4d0b3e890608cb9c98597d1bed7e937.zip
spi: reorder spi_message struct member doc comments
The members of `struct spi_message` were reordered in commit ae2ade4ba581 ("spi: Reorder fields in 'struct spi_message'") but the documentation comments were not updated to match. This commit updates the comments to match the new order. Signed-off-by: David Lechner <dlechner@baylibre.com> Link: https://msgid.link/r/20240131170732.1665105-1-dlechner@baylibre.com Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'include/linux')
-rw-r--r--include/linux/spi/spi.h4
1 files changed, 2 insertions, 2 deletions
diff --git a/include/linux/spi/spi.h b/include/linux/spi/spi.h
index f306aececeaf..29c3e4dd5d93 100644
--- a/include/linux/spi/spi.h
+++ b/include/linux/spi/spi.h
@@ -1113,16 +1113,16 @@ struct spi_transfer {
* @spi: SPI device to which the transaction is queued
* @is_dma_mapped: if true, the caller provided both DMA and CPU virtual
* addresses for each transfer buffer
+ * @prepared: spi_prepare_message was called for the this message
+ * @status: zero for success, else negative errno
* @complete: called to report transaction completions
* @context: the argument to complete() when it's called
* @frame_length: the total number of bytes in the message
* @actual_length: the total number of bytes that were transferred in all
* successful segments
- * @status: zero for success, else negative errno
* @queue: for use by whichever driver currently owns the message
* @state: for use by whichever driver currently owns the message
* @resources: for resource management when the SPI message is processed
- * @prepared: spi_prepare_message was called for the this message
*
* A @spi_message is used to execute an atomic sequence of data transfers,
* each represented by a struct spi_transfer. The sequence is "atomic"