From: David Lechner <dlechner@baylibre.com>
To: Mark Brown <broonie@kernel.org>
Cc: "David Lechner" <dlechner@baylibre.com>,
"Michael Hennerich" <michael.hennerich@analog.com>,
"Nuno Sá" <nuno.sa@analog.com>,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
"kernel test robot" <lkp@intel.com>
Subject: [PATCH] spi: axi-spi-engine: fix struct member doc warnings
Date: Mon, 18 Dec 2023 08:53:45 -0600 [thread overview]
Message-ID: <20231218145348.339470-1-dlechner@baylibre.com> (raw)
The build bots are complaining that the members of struct
spi_engine_message_state are not described. This adds the
proper @name: syntax to the comments to fix this.
Reported-by: kernel test robot <lkp@intel.com>
Closes: https://lore.kernel.org/oe-kbuild-all/202312182101.QOWovo29-lkp@intel.com/
Signed-off-by: David Lechner <dlechner@baylibre.com>
---
drivers/spi/spi-axi-spi-engine.c | 20 ++++++++++----------
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/drivers/spi/spi-axi-spi-engine.c b/drivers/spi/spi-axi-spi-engine.c
index 58280dd1c901..9ace259d2d29 100644
--- a/drivers/spi/spi-axi-spi-engine.c
+++ b/drivers/spi/spi-axi-spi-engine.c
@@ -85,25 +85,25 @@ struct spi_engine_program {
* struct spi_engine_message_state - SPI engine per-message state
*/
struct spi_engine_message_state {
- /** Instructions for executing this message. */
+ /** @p: Instructions for executing this message. */
struct spi_engine_program *p;
- /** Number of elements in cmd_buf array. */
+ /** @cmd_length: Number of elements in cmd_buf array. */
unsigned cmd_length;
- /** Array of commands not yet written to CMD FIFO. */
+ /** @cmd_buf: Array of commands not yet written to CMD FIFO. */
const uint16_t *cmd_buf;
- /** Next xfer with tx_buf not yet fully written to TX FIFO. */
+ /** @tx_xfer: Next xfer with tx_buf not yet fully written to TX FIFO. */
struct spi_transfer *tx_xfer;
- /** Size of tx_buf in bytes. */
+ /** @tx_length: Size of tx_buf in bytes. */
unsigned int tx_length;
- /** Bytes not yet written to TX FIFO. */
+ /** @tx_buf: Bytes not yet written to TX FIFO. */
const uint8_t *tx_buf;
- /** Next xfer with rx_buf not yet fully written to RX FIFO. */
+ /** @rx_xfer: Next xfer with rx_buf not yet fully written to RX FIFO. */
struct spi_transfer *rx_xfer;
- /** Size of tx_buf in bytes. */
+ /** @rx_length: Size of tx_buf in bytes. */
unsigned int rx_length;
- /** Bytes not yet written to the RX FIFO. */
+ /** @rx_buf: Bytes not yet written to the RX FIFO. */
uint8_t *rx_buf;
- /** ID to correlate SYNC interrupts with this message. */
+ /** @sync_id: ID to correlate SYNC interrupts with this message. */
u8 sync_id;
};
--
2.43.0
next reply other threads:[~2023-12-18 14:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-18 14:53 David Lechner [this message]
2023-12-18 19:06 ` Mark Brown
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=20231218145348.339470-1-dlechner@baylibre.com \
--to=dlechner@baylibre.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=lkp@intel.com \
--cc=michael.hennerich@analog.com \
--cc=nuno.sa@analog.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®