netdev - Re: pull-request: wireless-next-2022-03-11

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]

Message-ID: <20220314113738.640ea10b@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com>
Date:   Mon, 14 Mar 2022 11:37:38 -0700
From:   Jakub Kicinski <kuba@...nel.org>
To:     Kalle Valo <kvalo@...nel.org>
Cc:     Johannes Berg <johannes@...solutions.net>, netdev@...r.kernel.org,
        linux-wireless@...r.kernel.org
Subject: Re: pull-request: wireless-next-2022-03-11

On Mon, 14 Mar 2022 20:21:53 +0200 Kalle Valo wrote:
> Jakub Kicinski <kuba@...nel.org> writes:
> 
> > On Fri, 11 Mar 2022 17:06:25 -0800 Jakub Kicinski wrote:  
> >> Seems to break clang build.  
> >
> > No, sorry just some new warnings with W=1, I think.  
> 
> I have not installed clang yet. You don't happen to have the warnings
> stored someplace? I checked the patchwork tests and didn't see anything
> there.

Yeah.. patchwork build thing can't resolve conflicts. I wish there was
a way to attach a resolution to the PR so that the bot can use it :S

I was guessing what happened based on the result of the first thing
that got built after wireless-next was pulled but that thing itself
didn't build, hence my confusion. 

I say - don't worry about it. The non-W=1 build is clean which is what
matters the most.