From: Greg KH <greg@kroah.com>
To: Andrey Konovalov <andreyknvl@google.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Felipe Balbi <balbi@kernel.org>
Subject: Re: linux-next: build warnings after merge of the usb tree
Date: Tue, 17 Mar 2020 14:53:16 +0100 [thread overview]
Message-ID: <20200317135316.GB1360714@kroah.com> (raw)
In-Reply-To: <CAAeHK+zvcvxxxGKEhBm3t8rWoyMMEoGYJPpaW3-3sk4__PYJJg@mail.gmail.com>
On Tue, Mar 17, 2020 at 02:45:56PM +0100, Andrey Konovalov wrote:
> On Tue, Mar 17, 2020 at 8:57 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > 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?
>
> Hi Stephen,
>
> Yes, same issue as reported here:
> https://github.com/ClangBuiltLinux/linux/issues/934
>
> Thanks for the report!
>
> Greg, should I send a new version with the fix right now, or is it OK
> to wait until we get comments from Felipe/Alan and then send a new
> version?
Please send a fix for what is in my tree, I can't rebase it.
thanks,
greg k-h
next prev parent reply other threads:[~2020-03-17 13:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-17 7:57 linux-next: build warnings after merge of the usb tree Stephen Rothwell
2020-03-17 13:45 ` Andrey Konovalov
2020-03-17 13:53 ` Greg KH [this message]
-- 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=20200317135316.GB1360714@kroah.com \
--to=greg@kroah.com \
--cc=andreyknvl@google.com \
--cc=balbi@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).