linux-kernel - Re: [BUG] Re: [PATCH] brcmfmac: use ISO3166 country code and 0 rev as fallback

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: <ffe146e8-a393-2388-0f31-2bd030a75812@web.de>
Date:   Sun, 26 Sep 2021 22:20:48 +0200
From:   Soeren Moch <smoch@....de>
To:     Kalle Valo <kvalo@...eaurora.org>, Shawn Guo <shawn.guo@...aro.org>
Cc:     Rafał Miłecki <rafal@...ecki.pl>,
        Arend van Spriel <aspriel@...il.com>,
        Franky Lin <franky.lin@...adcom.com>,
        Hante Meuleman <hante.meuleman@...adcom.com>,
        Chi-hsien Lin <chi-hsien.lin@...ineon.com>,
        Wright Feng <wright.feng@...ineon.com>,
        Chung-hsien Hsu <chung-hsien.hsu@...ineon.com>,
        linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
        brcm80211-dev-list.pdl@...adcom.com,
        SHA-cyfmac-dev-list@...ineon.com,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-arm-kernel@...ts.infradead.org" 
        <linux-arm-kernel@...ts.infradead.org>,
        "linux-rockchip@...ts.infradead.org" 
        <linux-rockchip@...ts.infradead.org>
Subject: Re: [BUG] Re: [PATCH] brcmfmac: use ISO3166 country code and 0 rev as
 fallback



On 21.09.21 11:20, Kalle Valo wrote:
> Shawn Guo <shawn.guo@...aro.org> writes:
>
>>> Is this not the usual DT policy, that missing optional properties should
>>> not prevent a device to work, that old dtbs should still work when new
>>> properties are added?
>>>
>>> I'm not sure what's the best way forward. A plain revert of this patch
>>> would at least bring back wifi support for RockPro64 devices with
>>> existing dtbs. Maybe someone else has a better proposal how to proceed.
>> Go ahead to revert if we do not hear a better solution, I would say.
> Yes, please do send a revert. And remember to explain the regression in
> the commit log.
>
I sent a revert patch.

Sorry for the delay,
Soeren