From: "Alim Akhtar" <alim.akhtar@samsung.com>
To: "'Randy Dunlap'" <rdunlap@infradead.org>, <linux-scsi@vger.kernel.org>
Cc: "'James E.J. Bottomley'" <James.Bottomley@HansenPartnership.com>,
"'Martin K. Petersen'" <martin.petersen@oracle.com>,
"'Avri Altman'" <avri.altman@wdc.com>,
"'Bart Van Assche'" <bvanassche@acm.org>
Subject: RE: [PATCH] scsi: ufs: ufshcd.h: fix all kernel-doc warnings
Date: Mon, 20 Jul 2026 09:21:59 +0530 [thread overview]
Message-ID: <1cab01dd17fb$1ecb8f30$5c62ad90$@samsung.com> (raw)
In-Reply-To: <20260720013759.2979593-1-rdunlap@infradead.org>
> -----Original Message-----
> From: Randy Dunlap <rdunlap@infradead.org>
> Sent: Monday, July 20, 2026 7:08 AM
> To: linux-scsi@vger.kernel.org
> Cc: Randy Dunlap <rdunlap@infradead.org>; James E.J. Bottomley
> <James.Bottomley@HansenPartnership.com>; Martin K. Petersen
> <martin.petersen@oracle.com>; Alim Akhtar <alim.akhtar@samsung.com>; Avri
> Altman <avri.altman@wdc.com>; Bart Van Assche <bvanassche@acm.org>
> Subject: [PATCH] scsi: ufs: ufshcd.h: fix all kernel-doc warnings
>
> - use the correct name for a struct in kernel-doc
> - add kernel-doc for missing struct members or correct the name
>
> Warning: ./include/ufs/ufshcd.h:201 Excess struct member 'task_tag'
> description in 'ufshcd_lrb'
> Warning: ./include/ufs/ufshcd.h:220 expecting prototype for struct
> ufs_query_resp. Prototype was for struct ufs_query_res instead
> Warning: ./include/ufs/ufshcd.h:577 struct member 'suspend_on_no_request'
> not described in 'ufs_clk_scaling'
> Warning: ./include/ufs/ufshcd.h:1269 struct member 'nortt' not described
in
> 'ufs_hba'
> Warning: ./include/ufs/ufshcd.h:1269 struct member 'trigger_eh_attr' not
> described in 'ufs_hba'
> Warning: ./include/ufs/ufshcd.h:1269 struct member 'timeout_attr' not
> described in 'ufs_hba'
> Warning: ./include/ufs/ufshcd.h:1269 struct member 'lsdb_sup' not
described in
> 'ufs_hba'
> Warning: ./include/ufs/ufshcd.h:1269 struct member 'vcc_off_delay_us' not
> described in 'ufs_hba'
> Warning: ./include/ufs/ufshcd.h:1269 Excess struct member 'desc_size'
> description in 'ufs_hba'
> Warning: ./include/ufs/ufshcd.h:1269 Excess struct member 'res'
> description in 'ufs_hba'
> Warning: ./include/ufs/ufshcd.h:1309 struct member 'sq_tail_slot' not
described
> in 'ufs_hw_queue'
> Warning: ./include/ufs/ufshcd.h:1309 Excess struct member 'sq_tp_slot'
> description in 'ufs_hw_queue'
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> ---
> Cc: "James E.J. Bottomley" <James.Bottomley@HansenPartnership.com>
> Cc: "Martin K. Petersen" <martin.petersen@oracle.com>
> Cc: Alim Akhtar <alim.akhtar@samsung.com>
> Cc: Avri Altman <avri.altman@wdc.com>
> Cc: Bart Van Assche <bvanassche@acm.org>
>
Thanks!
Reviewed-by: Alim Akhtar <alim.akhtar@samsung.com>
next prev parent reply other threads:[~2026-07-20 3:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20260720013809epcas5p2435800e514012c9cac5a62231fd8ec48@epcas5p2.samsung.com>
2026-07-20 1:37 ` [PATCH] scsi: ufs: ufshcd.h: fix all kernel-doc warnings Randy Dunlap
2026-07-20 3:51 ` Alim Akhtar [this message]
2026-07-22 18:11 ` Bart Van Assche
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='1cab01dd17fb$1ecb8f30$5c62ad90$@samsung.com' \
--to=alim.akhtar@samsung.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=avri.altman@wdc.com \
--cc=bvanassche@acm.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=rdunlap@infradead.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.