linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Jiri Kosina <jikos@kernel.org>,
	Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: 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: Tue, 04 Apr 2023 10:22:35 +0200	[thread overview]
Message-ID: <e1eb90db85ed7adad08bb99054f5cda3cb626794.camel@hadess.net> (raw)
In-Reply-To: <20230404154254.6c3be26b@canb.auug.org.au>

On Tue, 2023-04-04 at 15:42 +1000, Stephen Rothwell wrote:
> Hi all,
> 
> On Tue, 4 Apr 2023 15:40:05 +1000 Stephen Rothwell
> <sfr@canb.auug.org.au> wrote:
> > 
> > After merging the hid tree, today's linux-next build (htmldocs)
> > produced
> > this warning:
> > 
> > drivers/usb/core/message.c:1939: warning: Function parameter or
> > member 'iface' not described in 'usb_set_wireless_status'
> > drivers/usb/core/message.c:1939: warning: Excess function parameter
> > 'dev' description in 'usb_set_wireless_status'
> > 
> > Introduced by commit
> > 
> >   0a4db185f078 ("USB: core: Add API to change the wireless_status")
> 
> Also this:
> 
> include/linux/usb.h:270: warning: Function parameter or member
> 'wireless_status_work' not described in 'usb_interface'
> 

How does one reproduce those warnings?

  reply	other threads:[~2023-04-04  8:22 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2023-04-04  8:55     ` Stephen Rothwell
2023-04-04  9:18       ` Bastien Nocera
2023-04-05  1:48         ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2021-11-10  4:06 Stephen Rothwell
2021-11-10  8:17 ` Jiri Kosina
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=e1eb90db85ed7adad08bb99054f5cda3cb626794.camel@hadess.net \
    --to=hadess@hadess.net \
    --cc=benjamin.tissoires@redhat.com \
    --cc=jikos@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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).