From: sashiko-bot@kernel.org
To: "Randy Dunlap" <rdunlap@infradead.org>
Cc: linux-usb@vger.kernel.org
Subject: Re: [PATCH v2] USB: ohci: ohci_pdriver.h: fix missing kernel-doc comments
Date: Tue, 03 Nov 2026 01:49:15 +0000 [thread overview]
Message-ID: <sashiko-outbox-194438@kernel.org> (raw)
In-Reply-To: <20261103014710.2451967-1-rdunlap@infradead.org>
> Convert comments to kernel-doc format to avoid kernel-doc warnings:
>
> Warning: include/linux/usb/ohci_pdriver.h:32 struct member 'power_on'
> not described in 'usb_ohci_pdata'
> Warning: include/linux/usb/ohci_pdriver.h:32 struct member 'power_off'
> not described in 'usb_ohci_pdata'
> Warning: include/linux/usb/ohci_pdriver.h:32 struct member 'power_suspend'
> not described in 'usb_ohci_pdata'
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261103014710.2451967-1-rdunlap@infradead.org?part=1
prev parent reply other threads:[~2026-11-03 1:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 1:47 [PATCH v2] USB: ohci: ohci_pdriver.h: fix missing kernel-doc comments Randy Dunlap
2026-11-03 1:49 ` sashiko-bot [this message]
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=sashiko-outbox-194438@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=sashiko-reviews@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