From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Greg KH <greg@kroah•com>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Andrey Konovalov <andreyknvl@google•com>,
Felipe Balbi <balbi@kernel•org>
Subject: linux-next: build warnings after merge of the usb tree
Date: Tue, 17 Mar 2020 18:57:48 +1100 [thread overview]
Message-ID: <20200317185748.085ecf7f@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 729 bytes --]
Hi all,
After merging the usb tree, today's (actually yesterday's) linux-next
build (powerpc allyesconfig) produced these warnings:
./usr/include/linux/usb/raw_gadget.h:74:12: warning: 'usb_raw_io_flags_zero' defined but not used [-Wunused-function]
74 | static int usb_raw_io_flags_zero(__u16 flags)
| ^~~~~~~~~~~~~~~~~~~~~
./usr/include/linux/usb/raw_gadget.h:69:12: warning: 'usb_raw_io_flags_valid' defined but not used [-Wunused-function]
69 | static int usb_raw_io_flags_valid(__u16 flags)
| ^~~~~~~~~~~~~~~~~~~~~~
Introduced by commit
f2c2e717642c ("usb: gadget: add raw-gadget interface")
Missing "inline" n a header file?
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-03-17 7:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-17 7:57 Stephen Rothwell [this message]
2020-03-17 13:45 ` linux-next: build warnings after merge of the usb tree Andrey Konovalov
2020-03-17 13:53 ` Greg KH
-- strict thread matches above, loose matches on Subject: below --
2020-01-07 3:30 Stephen Rothwell
2020-01-07 8:06 ` Krzysztof Kozlowski
2020-01-21 6:28 ` Stephen Rothwell
2020-01-21 7:55 ` Krzysztof Kozlowski
2017-11-02 4:10 Stephen Rothwell
2017-11-02 8:45 ` Greg KH
2011-04-14 4:18 Stephen Rothwell
2011-04-14 4:51 ` Greg KH
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=20200317185748.085ecf7f@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=andreyknvl@google$(echo .)com \
--cc=balbi@kernel$(echo .)org \
--cc=greg@kroah$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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