linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jiri Kosina <jikos@kernel.org>
To: "Stephen Rothwell" <sfr@canb.auug.org.au>,
	"Thomas Weißschuh" <linux@weissschuh.net>
Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build warning after merge of the hid tree
Date: Wed, 10 Nov 2021 09:17:42 +0100 (CET)	[thread overview]
Message-ID: <nycvar.YFH.7.76.2111100915550.12554@cbobk.fhfr.pm> (raw)
In-Reply-To: <20211110150639.7db57ae2@canb.auug.org.au>

On Wed, 10 Nov 2021, Stephen Rothwell wrote:

> Hi all,
> 
> After merging the hid tree, today's linux-next build (htmldocs) produced
> this warning:
> 
> include/linux/mod_devicetable.h:909: warning: Function parameter or member 'guid' not described in 'ishtp_device_id'
> 
> Introduced by commit
> 
>   fa443bc3c1e4 ("HID: intel-ish-hid: add support for MODULE_DEVICE_TABLE()")
> 
> I also notice that there is a @context description, but no field.

Thanks for spotting it. The kerneldoc is clearly wrong there both on the 
'guid' member name, and also the description (mind the '36 char' part, 
where it should have been '16 char' instead).

Thomas, could you please send me a fixup patch for that?

Thanks,

-- 
Jiri Kosina
SUSE Labs


  reply	other threads:[~2021-11-10  8:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-10  4:06 linux-next: build warning after merge of the hid tree Stephen Rothwell
2021-11-10  8:17 ` Jiri Kosina [this message]
2021-11-10 12:16 ` [PATCH] mod_devicetable: fix kdocs for ishtp_device_id Thomas Weißschuh
2021-11-10 12:20   ` Jiri Kosina
  -- strict thread matches above, loose matches on Subject: below --
2023-04-04  5:40 linux-next: build warning after merge of the hid tree Stephen Rothwell
2023-04-04  5:42 ` Stephen Rothwell
2023-04-04  8:22   ` Bastien Nocera
2023-04-04  8:55     ` Stephen Rothwell
2023-04-04  9:18       ` Bastien Nocera
2023-04-05  1:48         ` Stephen Rothwell
2012-07-02  2:14 Stephen Rothwell
2012-07-03  9:22 ` Jiri Kosina
2012-04-30  4:05 Stephen Rothwell
2012-04-30  8:42 ` Jiri Kosina
2012-03-29  0:51 Stephen Rothwell
2012-03-30  8:45 ` Jiri Kosina

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=nycvar.YFH.7.76.2111100915550.12554@cbobk.fhfr.pm \
    --to=jikos@kernel.org \
    --cc=benjamin.tissoires@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linux@weissschuh.net \
    --cc=sfr@canb.auug.org.au \
    /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).