All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ruben Wauters <rubenru09@aol.com>
To: Mark Brown <broonie@kernel.org>
Cc: Ruben Wauters <rubenru09@aol.com>,
	linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-doc@vger.kernel.org
Subject: [PATCH] spi: Add documentation for last_cs_index_mask
Date: Tue,  9 Apr 2024 19:41:05 +0100	[thread overview]
Message-ID: <20240409184106.22715-1-rubenru09@aol.com> (raw)
In-Reply-To: 20240409184106.22715-1-rubenru09.ref@aol.com

Documentation was missing for last_cs_index_mask, this was shown by
a warning in make htmldocs.

I have based the documentation off the docs for cs_index_mask, given
that they should be similar.

This is my first patch, so I hope I did everything right, please let
me know if I need to change something, and I shall endevour to do it
properly.

Signed-off-by: Ruben Wauters <rubenru09@aol.com>
---
 include/linux/spi/spi.h | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/include/linux/spi/spi.h b/include/linux/spi/spi.h
index c459809efee4..ed941e65791a 100644
--- a/include/linux/spi/spi.h
+++ b/include/linux/spi/spi.h
@@ -453,6 +453,8 @@ extern struct spi_device *spi_new_ancillary_device(struct spi_device *spi, u8 ch
  * @last_cs_mode_high: was (mode & SPI_CS_HIGH) true on the last call to set_cs.
  * @last_cs: the last chip_select that is recorded by set_cs, -1 on non chip
  *           selected
+ * @last_cs_index_mask: the last active chip select bit masks in the chip select
+ *                      array
  * @xfer_completion: used by core transfer_one_message()
  * @busy: message pump is busy
  * @running: message pump is running
-- 
2.40.1


       reply	other threads:[~2024-04-09 19:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20240409184106.22715-1-rubenru09.ref@aol.com>
2024-04-09 18:41 ` Ruben Wauters [this message]
2024-04-09 19:09   ` [PATCH] spi: Add documentation for last_cs_index_mask Mark Brown
2024-04-09 19:18     ` Ruben Wauters

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240409184106.22715-1-rubenru09@aol.com \
    --to=rubenru09@aol.com \
    --cc=broonie@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.