From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
USB list <linux-usb@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: linux/mod_devicetable.h: fix kernel-doc missing notation for typec_device_id
Date: Tue, 4 Sep 2018 10:40:34 +0300 [thread overview]
Message-ID: <20180904074034.GG15112@kuha.fi.intel.com> (raw)
On Mon, Sep 03, 2018 at 12:51:59PM -0700, Randy Dunlap wrote:
> From: Randy Dunlap <rdunlap@infradead.org>
>
> Fix kernel-doc warning for missing struct member description:
>
> ../include/linux/mod_devicetable.h:763: warning: Function parameter or member 'driver_data' not described in 'typec_device_id'
>
> Fixes: 8a37d87d72f0c ("usb: typec: Bus type for alternate modes")
>
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Reviewed-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
> ---
> include/linux/mod_devicetable.h | 1 +
> 1 file changed, 1 insertion(+)
>
> --- lnx-419-rc2.orig/include/linux/mod_devicetable.h
> +++ lnx-419-rc2/include/linux/mod_devicetable.h
> @@ -754,6 +754,7 @@ struct tb_service_id {
> * struct typec_device_id - USB Type-C alternate mode identifiers
> * @svid: Standard or Vendor ID
> * @mode: Mode index
> + * @driver_data: Driver specific data
> */
> struct typec_device_id {
> __u16 svid;
>
Thanks,
next reply other threads:[~2018-09-04 7:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-04 7:40 Heikki Krogerus [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-09-03 19:51 linux/mod_devicetable.h: fix kernel-doc missing notation for typec_device_id Randy Dunlap
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=20180904074034.GG15112@kuha.fi.intel.com \
--to=heikki.krogerus@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--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 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).