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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 03 Dec 2018 14:38:26 +0200
From:   Luciano Coelho <luciano.coelho@...el.com>
To:     Kalle Valo <kvalo@...eaurora.org>,
        Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Wireless <linux-wireless@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Sara Sharon <sara.sharon@...el.com>,
        Kees Cook <keescook@...gle.com>,
        "Gustavo A. R. Silva" <gustavo@...eddedor.com>
Subject: Re: linux-next: build warnings after merge of the
 wireless-drivers-next tree

On Fri, 2018-11-30 at 09:43 +0200, Kalle Valo wrote:
> Stephen Rothwell <sfr@...b.auug.org.au> writes:
> 
> > Hi Kalle,
> > 
> > On Fri, 30 Nov 2018 06:33:47 +0200 Kalle Valo <kvalo@...eaurora.org
> > > wrote:
> > > I take it that -Wimplict-fallthrough is not enabled by default
> > > yet? So
> > > Dave and Linus won't see these warnings?
> > 
> > Correct.
> > 
> > > What I'm planning is to send a pull request to Dave today and fix
> > > these
> > > warnings in the next pull request. Does that sound good?
> > 
> > That sounds fine.
> 
> Great, thanks for the confirmation. I'll then send the pull request
> today.

Just FYI, I enabled this by default in our internal tree so we will
notice when it happens before sending the patch upstream.

--
Cheers,
Luca.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ