From: kernel test robot <lkp@intel.com>
To: Ayush Singh <ayushdevel1325@gmail.com>, greybus-dev@lists.linaro.org
Cc: oe-kbuild-all@lists.linux.dev,
Ayush Singh <ayushdevel1325@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
gregkh@linuxfoundation.org, vaishnav@beagleboard.org,
jkridner@beagleboard.org, nm@ti.com,
krzysztof.kozlowski+dt@linaro.org, johan@kernel.org,
elder@kernel.org
Subject: Re: [PATCH v6 2/3] greybus: Add BeaglePlay Linux Driver
Date: Tue, 3 Oct 2023 15:40:31 +0800 [thread overview]
Message-ID: <202310031521.Iq3S1RE9-lkp@intel.com> (raw)
In-Reply-To: <20231002182454.211165-3-ayushdevel1325@gmail.com>
Hi Ayush,
kernel test robot noticed the following build warnings:
[auto build test WARNING on 6269320850097903b30be8f07a5c61d9f7592393]
url: https://github.com/intel-lab-lkp/linux/commits/Ayush-Singh/dt-bindings-Add-beaglecc1352/20231003-031225
base: 6269320850097903b30be8f07a5c61d9f7592393
patch link: https://lore.kernel.org/r/20231002182454.211165-3-ayushdevel1325%40gmail.com
patch subject: [PATCH v6 2/3] greybus: Add BeaglePlay Linux Driver
config: sh-allmodconfig (https://download.01.org/0day-ci/archive/20231003/202310031521.Iq3S1RE9-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20231003/202310031521.Iq3S1RE9-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/202310031521.Iq3S1RE9-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> drivers/greybus/gb-beagleplay.c:45: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
* BeaglePlay Greybus driver
drivers/greybus/gb-beagleplay.c:78: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
* Structure to represent part of HDCL frame payload data.
drivers/greybus/gb-beagleplay.c:107: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
* Consume HDLC Buffer. This function assumes that consumer lock has been acquired.
drivers/greybus/gb-beagleplay.c:127: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
* Queue HDLC data for sending. This function assumes that producer lock as been acquired.
vim +45 drivers/greybus/gb-beagleplay.c
43
44 /**
> 45 * BeaglePlay Greybus driver
46 *
47 * @sd: underlying serdev device
48 *
49 * @gb_hd: greybus host device of this driver
50 *
51 * @tx_work: hdlc transmit work
52 * @tx_producer_lock: hdlc transmit data producer lock. acquired when appending data to buffer.
53 * @tx_consumer_lock: hdlc transmit data consumer lock. acquired when sending data over uart.
54 * @tx_circ_buf: hdlc transmit circular buffer.
55 * @tx_crc: hdlc transmit crc-ccitt fcs
56 *
57 * @rx_buffer_len: length of receive buffer filled.
58 * @rx_buffer: hdlc frame receive buffer
59 * @rx_in_esc: hdlc rx flag to indicate ESC frame
60 */
61 struct gb_beagleplay {
62 struct serdev_device *sd;
63
64 struct gb_host_device *gb_hd;
65
66 struct work_struct tx_work;
67 spinlock_t tx_producer_lock;
68 spinlock_t tx_consumer_lock;
69 struct circ_buf tx_circ_buf;
70 u16 tx_crc;
71
72 u16 rx_buffer_len;
73 bool rx_in_esc;
74 u8 rx_buffer[MAX_RX_HDLC];
75 };
76
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-10-03 7:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 18:24 [PATCH v6 0/3] greybus: Add BeaglePlay Greybus Driver Ayush Singh
2023-10-02 18:24 ` [PATCH v6 1/3] dt-bindings: Add beaglecc1352 Ayush Singh
2023-10-03 8:21 ` Krzysztof Kozlowski
2023-10-03 12:09 ` Ayush Singh
2023-10-03 13:07 ` Nishanth Menon
2023-10-03 11:30 ` Nishanth Menon
2023-10-03 12:47 ` Ayush Singh
2023-10-03 13:05 ` Nishanth Menon
2023-10-02 18:24 ` [PATCH v6 2/3] greybus: Add BeaglePlay Linux Driver Ayush Singh
2023-10-03 7:40 ` kernel test robot [this message]
2023-10-03 8:25 ` Krzysztof Kozlowski
2023-10-02 18:24 ` [PATCH v6 3/3] dts: ti: k3-am625-beagleplay: Add beaglecc1352 Ayush Singh
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=202310031521.Iq3S1RE9-lkp@intel.com \
--to=lkp@intel.com \
--cc=ayushdevel1325@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=jkridner@beagleboard.org \
--cc=johan@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=vaishnav@beagleboard.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 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).