Skip to contentSkip to conversation

spi: Fix the error description in the `ptp_sts_word_post` comment

PATCH In review Dewei Meng 2 participants 2 messages Apr 21 SPI

lore
Share & tools
lore

Dewei Meng

author
#0 lore raw

PATCH 1/1 spi: Fix the error description in the `ptp_sts_word_post` comment

Based on the comment information, the description within the ptp_sts_word_post section should be changed to "See @ptp_sts_word_pre".

---
 include/linux/spi/spi.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
include/linux/spi/spi.h +1 -1
index 7587b1c5d7ec..82682dd9961d 100644
@@ -1019,7 +1019,7 @@ struct spi_res {
  *	this value may have changed compared to what was requested, depending
  *	on the available snapshotting resolution (DMA transfer,
  *	@ptp_sts_supported is false, etc).
- * @ptp_sts_word_post: See @ptp_sts_word_post. The two can be equal (meaning
+ * @ptp_sts_word_post: See @ptp_sts_word_pre. The two can be equal (meaning
  *	that a single byte should be snapshotted).
  *	If the core takes care of the timestamp (if @ptp_sts_supported is false
  *	for this controller), it will set @ptp_sts_word_pre to 0, and
Signature · 1 line
2.43.7
maintainer
#1 lore raw
Quoted 1 line · Dewei Meng

spi: Fix the error description in the ptp_sts_word_post comment

Applied to

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

Thanks!

[1/1] spi: Fix the error description in the ptp_sts_word_post comment

      https://git.kernel.org/broonie/spi/c/922f8c28811f

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