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] [thread-next>] [day] [month] [year] [list]
Message-ID: <604ee91b52c79c575bb0ac0849f504be354bf404.camel@sipsolutions.net>
Date:   Fri, 27 May 2022 11:23:10 +0200
From:   Johannes Berg <johannes@...solutions.net>
To:     Kalle Valo <kvalo@...nel.org>,
        Sudip Mukherjee <sudipm.mukherjee@...il.com>
Cc:     Gregory Greenman <gregory.greenman@...el.com>,
        Luca Coelho <luciano.coelho@...el.com>,
        "David S. Miller" <davem@...emloft.net>,
        Jakub Kicinski <kuba@...nel.org>,
        Paolo Abeni <pabeni@...hat.com>,
        linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
        linux-kernel@...r.kernel.org, torvalds@...ux-foundation.org
Subject: Re: mainline build failure due to c1918196427b ("iwlwifi: pcie:
 simplify MSI-X cause mapping")

On Fri, 2022-05-27 at 12:20 +0300, Kalle Valo wrote:
> 
> iwlwifi: pcie: rename CAUSE macro
> 
> https://patchwork.kernel.org/project/linux-wireless/patch/20220523220300.682be2029361.I283200b18da589a975a284073dca8ed001ee107a@changeid/
> 
> It's marked as accepted but I don't know where it's applied to, Gregory?

Gregory picked it up to our internal tree.

> This is failing the build, should Linus apply the fix directly to his
> tree?

I had previous asked Jakub if he wanted to do that, but he didn't (yet).
I don't know what's the best course of action right now...

No objections to it taking any kind of fast path though :)

johannes

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ