netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* [PATCH] ath: wil6210: fix a bunch of kernel-doc warnings
@ 2025-11-17  2:02 Randy Dunlap
  2025-11-21 13:04 ` Simon Horman
  0 siblings, 1 reply; 3+ messages in thread
From: Randy Dunlap @ 2025-11-17  2:02 UTC (permalink / raw)
  To: netdev; +Cc: Randy Dunlap, Johannes Berg, linux-wireless

scripts/kernel-doc.py reports 51 kernel-doc warnings in wil6210.h.
Fix all kernel-doc warnings reported in wil6210.h.

Several comments are changed from "/**" to "/*" since it appears that
"/**" was used for many non-kernel-doc comments.

- add kernel-doc for missing function parameters
- add one function "Returns:"
- correct kernel-doc struct name to match actual struct name in 2 places

Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
---
Cc: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
---
 drivers/net/wireless/ath/wil6210/wil6210.h |   33 +++++++++----------
 1 file changed, 16 insertions(+), 17 deletions(-)

--- linux-next-20251114.orig/drivers/net/wireless/ath/wil6210/wil6210.h
+++ linux-next-20251114/drivers/net/wireless/ath/wil6210/wil6210.h
@@ -58,7 +58,7 @@ union wil_tx_desc;
  */
 #define WIL_MAX_VIFS 4
 
-/**
+/*
  * extract bits [@b0:@b1] (inclusive) from the value @x
  * it should be @b0 <= @b1, or result is incorrect
  */
@@ -433,7 +433,7 @@ extern struct fw_map fw_mapping[MAX_FW_M
  * @cid: CID value
  * @tid: TID value
  *
- * @cidxtid field encoded as bits 0..3 - CID; 4..7 - TID
+ * Returns: @cidxtid field encoded as bits 0..3 - CID; 4..7 - TID
  */
 static inline u8 mk_cidxtid(u8 cid, u8 tid)
 {
@@ -444,8 +444,7 @@ static inline u8 mk_cidxtid(u8 cid, u8 t
  * parse_cidxtid - parse @cidxtid field
  * @cid: store CID value here
  * @tid: store TID value here
- *
- * @cidxtid field encoded as bits 0..3 - CID; 4..7 - TID
+ * @cidxtid: field encoded as bits 0..3 - CID; 4..7 - TID
  */
 static inline void parse_cidxtid(u8 cidxtid, u8 *cid, u8 *tid)
 {
@@ -500,7 +499,7 @@ enum { /* for wil_ctx.mapped_as */
 	wil_mapped_as_page = 2,
 };
 
-/**
+/*
  * struct wil_ctx - software context for ring descriptor
  */
 struct wil_ctx {
@@ -514,7 +513,7 @@ struct wil_desc_ring_rx_swtail { /* rele
 	dma_addr_t pa;
 };
 
-/**
+/*
  * A general ring structure, used for RX and TX.
  * In legacy DMA it represents the vring,
  * In enahnced DMA it represents the descriptor ring (vrings are handled by FW)
@@ -531,7 +530,7 @@ struct wil_ring {
 	bool is_rx;
 };
 
-/**
+/*
  * Additional data for Rx ring.
  * Used for enhanced DMA RX chaining.
  */
@@ -543,7 +542,7 @@ struct wil_ring_rx_data {
 	u16 buff_size;
 };
 
-/**
+/*
  * Status ring structure, used for enhanced DMA completions for RX and TX.
  */
 struct wil_status_ring {
@@ -586,8 +585,8 @@ struct wil_net_stats {
 	u32 ft_roams; /* relevant in STA mode */
 };
 
-/**
- * struct tx_rx_ops - different TX/RX ops for legacy and enhanced
+/*
+ * struct wil_txrx_ops - different TX/RX ops for legacy and enhanced
  * DMA flow
  */
 struct wil_txrx_ops {
@@ -627,7 +626,7 @@ struct wil_txrx_ops {
 	irqreturn_t (*irq_rx)(int irq, void *cookie);
 };
 
-/**
+/*
  * Additional data for Tx ring
  */
 struct wil_ring_tx_data {
@@ -658,7 +657,7 @@ enum { /* for wil6210_priv.status */
 struct pci_dev;
 
 /**
- * struct tid_ampdu_rx - TID aggregation information (Rx).
+ * struct wil_tid_ampdu_rx - TID aggregation information (Rx).
  *
  * @reorder_buf: buffer to reorder incoming aggregated MPDUs
  * @last_rx: jiffies of last rx activity
@@ -728,7 +727,7 @@ enum wil_rekey_state {
 	WIL_REKEY_WAIT_M4_SENT = 2,
 };
 
-/**
+/*
  * struct wil_sta_info - data for peer
  *
  * Peer identified by its CID (connection ID)
@@ -741,7 +740,7 @@ struct wil_sta_info {
 	u8 mid;
 	enum wil_sta_status status;
 	struct wil_net_stats stats;
-	/**
+	/*
 	 * 20 latency bins. 1st bin counts packets with latency
 	 * of 0..tx_latency_res, last bin counts packets with latency
 	 * of 19*tx_latency_res and above.
@@ -882,7 +881,7 @@ struct wil6210_vif {
 	struct work_struct enable_tx_key_worker;
 };
 
-/**
+/*
  * RX buffer allocated for enhanced DMA RX descriptors
  */
 struct wil_rx_buff {
@@ -891,7 +890,7 @@ struct wil_rx_buff {
 	int id;
 };
 
-/**
+/*
  * During Rx completion processing, the driver extracts a buffer ID which
  * is used as an index to the rx_buff_mgmt.buff_arr array and then the SKB
  * is given to the network stack and the buffer is moved from the 'active'
@@ -1147,7 +1146,7 @@ static inline void wil_c(struct wil6210_
 	wil_w(wil, reg, wil_r(wil, reg) & ~val);
 }
 
-/**
+/*
  * wil_cid_valid - check cid is valid
  */
 static inline bool wil_cid_valid(struct wil6210_priv *wil, int cid)

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH] ath: wil6210: fix a bunch of kernel-doc warnings
  2025-11-17  2:02 [PATCH] ath: wil6210: fix a bunch of kernel-doc warnings Randy Dunlap
@ 2025-11-21 13:04 ` Simon Horman
  2025-11-22  5:26   ` Randy Dunlap
  0 siblings, 1 reply; 3+ messages in thread
From: Simon Horman @ 2025-11-21 13:04 UTC (permalink / raw)
  To: Randy Dunlap; +Cc: netdev, Johannes Berg, linux-wireless

On Sun, Nov 16, 2025 at 06:02:13PM -0800, Randy Dunlap wrote:
> scripts/kernel-doc.py reports 51 kernel-doc warnings in wil6210.h.
> Fix all kernel-doc warnings reported in wil6210.h.
> 
> Several comments are changed from "/**" to "/*" since it appears that
> "/**" was used for many non-kernel-doc comments.
> 
> - add kernel-doc for missing function parameters
> - add one function "Returns:"
> - correct kernel-doc struct name to match actual struct name in 2 places
> 
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>

...

> @@ -444,8 +444,7 @@ static inline u8 mk_cidxtid(u8 cid, u8 t
>   * parse_cidxtid - parse @cidxtid field
>   * @cid: store CID value here
>   * @tid: store TID value here
> - *
> - * @cidxtid field encoded as bits 0..3 - CID; 4..7 - TID
> + * @cidxtid: field encoded as bits 0..3 - CID; 4..7 - TID

Hi Randy,

I wonder if it would make sense to move the @cidxtid line
so it is above the @cid line. In which case the order of
the documentation of the parameters would match their order
in the subject.

But either way, this patch looks good to me.

Reviewed-by: Simon Horman <horms@kernel.org>

>   */
>  static inline void parse_cidxtid(u8 cidxtid, u8 *cid, u8 *tid)
>  {

...


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [PATCH] ath: wil6210: fix a bunch of kernel-doc warnings
  2025-11-21 13:04 ` Simon Horman
@ 2025-11-22  5:26   ` Randy Dunlap
  0 siblings, 0 replies; 3+ messages in thread
From: Randy Dunlap @ 2025-11-22  5:26 UTC (permalink / raw)
  To: Simon Horman; +Cc: netdev, Johannes Berg, linux-wireless



On 11/21/25 5:04 AM, Simon Horman wrote:
> On Sun, Nov 16, 2025 at 06:02:13PM -0800, Randy Dunlap wrote:
>> scripts/kernel-doc.py reports 51 kernel-doc warnings in wil6210.h.
>> Fix all kernel-doc warnings reported in wil6210.h.
>>
>> Several comments are changed from "/**" to "/*" since it appears that
>> "/**" was used for many non-kernel-doc comments.
>>
>> - add kernel-doc for missing function parameters
>> - add one function "Returns:"
>> - correct kernel-doc struct name to match actual struct name in 2 places
>>
>> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> 
> ...
> 
>> @@ -444,8 +444,7 @@ static inline u8 mk_cidxtid(u8 cid, u8 t
>>   * parse_cidxtid - parse @cidxtid field
>>   * @cid: store CID value here
>>   * @tid: store TID value here
>> - *
>> - * @cidxtid field encoded as bits 0..3 - CID; 4..7 - TID
>> + * @cidxtid: field encoded as bits 0..3 - CID; 4..7 - TID
> 
> Hi Randy,
> 
> I wonder if it would make sense to move the @cidxtid line
> so it is above the @cid line. In which case the order of
> the documentation of the parameters would match their order
> in the subject.

I've looked at a lot of kernel-doc comments. I prefer in-order
comments, but so many of them are out of order that I don't bother
with them.

> But either way, this patch looks good to me.
> 
> Reviewed-by: Simon Horman <horms@kernel.org>
> 
>>   */
>>  static inline void parse_cidxtid(u8 cidxtid, u8 *cid, u8 *tid)
>>  {
> 
> ...
> 

thanks.
-- 
~Randy


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2025-11-22  5:26 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-11-17  2:02 [PATCH] ath: wil6210: fix a bunch of kernel-doc warnings Randy Dunlap
2025-11-21 13:04 ` Simon Horman
2025-11-22  5:26   ` Randy Dunlap

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).