From: kernel test robot <lkp@intel.com>
To: David Lechner <dlechner@baylibre.com>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Mark Brown <broonie@kernel.org>
Subject: [linux-next:master 1595/9113] drivers/spi/spi-axi-spi-engine.c:106: warning: Function parameter or struct member 'p' not described in 'spi_engine_message_state'
Date: Mon, 18 Dec 2023 21:09:38 +0800 [thread overview]
Message-ID: <202312182101.QOWovo29-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: ceb2fe0d438644e1de06b9a6468a1fb8e2199c70
commit: 7f970ecb77b6759d37ee743fc36fc0daba960e75 [1595/9113] spi: axi-spi-engine: move msg state to new struct
config: m68k-randconfig-r036-20220907 (https://download.01.org/0day-ci/archive/20231218/202312182101.QOWovo29-lkp@intel.com/config)
compiler: m68k-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231218/202312182101.QOWovo29-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202312182101.QOWovo29-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/spi/spi-axi-spi-engine.c:106: warning: Function parameter or struct member 'p' not described in 'spi_engine_message_state'
>> drivers/spi/spi-axi-spi-engine.c:106: warning: Function parameter or struct member 'cmd_length' not described in 'spi_engine_message_state'
>> drivers/spi/spi-axi-spi-engine.c:106: warning: Function parameter or struct member 'cmd_buf' not described in 'spi_engine_message_state'
>> drivers/spi/spi-axi-spi-engine.c:106: warning: Function parameter or struct member 'tx_xfer' not described in 'spi_engine_message_state'
>> drivers/spi/spi-axi-spi-engine.c:106: warning: Function parameter or struct member 'tx_length' not described in 'spi_engine_message_state'
>> drivers/spi/spi-axi-spi-engine.c:106: warning: Function parameter or struct member 'tx_buf' not described in 'spi_engine_message_state'
>> drivers/spi/spi-axi-spi-engine.c:106: warning: Function parameter or struct member 'rx_xfer' not described in 'spi_engine_message_state'
>> drivers/spi/spi-axi-spi-engine.c:106: warning: Function parameter or struct member 'rx_length' not described in 'spi_engine_message_state'
>> drivers/spi/spi-axi-spi-engine.c:106: warning: Function parameter or struct member 'rx_buf' not described in 'spi_engine_message_state'
>> drivers/spi/spi-axi-spi-engine.c:106: warning: Function parameter or struct member 'sync_id' not described in 'spi_engine_message_state'
vim +106 drivers/spi/spi-axi-spi-engine.c
81
82 /**
83 * struct spi_engine_message_state - SPI engine per-message state
84 */
85 struct spi_engine_message_state {
86 /** Instructions for executing this message. */
87 struct spi_engine_program *p;
88 /** Number of elements in cmd_buf array. */
89 unsigned cmd_length;
90 /** Array of commands not yet written to CMD FIFO. */
91 const uint16_t *cmd_buf;
92 /** Next xfer with tx_buf not yet fully written to TX FIFO. */
93 struct spi_transfer *tx_xfer;
94 /** Size of tx_buf in bytes. */
95 unsigned int tx_length;
96 /** Bytes not yet written to TX FIFO. */
97 const uint8_t *tx_buf;
98 /** Next xfer with rx_buf not yet fully written to RX FIFO. */
99 struct spi_transfer *rx_xfer;
100 /** Size of tx_buf in bytes. */
101 unsigned int rx_length;
102 /** Bytes not yet written to the RX FIFO. */
103 uint8_t *rx_buf;
104 /** ID to correlate SYNC interrupts with this message. */
105 u8 sync_id;
> 106 };
107
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-12-18 13:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202312182101.QOWovo29-lkp@intel.com \
--to=lkp@intel.com \
--cc=broonie@kernel.org \
--cc=dlechner@baylibre.com \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
/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;
as well as URLs for NNTP newsgroup(s).