From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jiri Kosina <jikos@kernel.org>,
Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: Bastien Nocera <hadess@hadess.net>,
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, 4 Apr 2023 15:42:54 +1000 [thread overview]
Message-ID: <20230404154254.6c3be26b@canb.auug.org.au> (raw)
In-Reply-To: <20230404154005.449800c3@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 709 bytes --]
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'
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2023-04-04 5:43 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 [this message]
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
-- 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=20230404154254.6c3be26b@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=benjamin.tissoires@redhat.com \
--cc=hadess@hadess.net \
--cc=jikos@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.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.