linux-kernel - Re: linux-next: build warnings after merge of the usb tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20200317135316.GB1360714@kroah.com>
Date:   Tue, 17 Mar 2020 14:53:16 +0100
From:   Greg KH <greg@...ah.com>
To:     Andrey Konovalov <andreyknvl@...gle.com>
Cc:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Felipe Balbi <balbi@...nel.org>
Subject: Re: linux-next: build warnings after merge of the usb tree

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@...b.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