linux-kernel - Re: linux-next: build failure after merge of the chrome-platform 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: <ZLo29pYwDhKBLM2S@google.com>
Date:   Fri, 21 Jul 2023 15:42:46 +0800
From:   Tzung-Bi Shih <tzungbi@...nel.org>
To:     Rob Barnes <robbarnes@...gle.com>
Cc:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Benson Leung <bleung@...gle.com>,
        Guenter Roeck <groeck@...omium.org>,
        Dmitry Torokhov <dmitry.torokhov@...il.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux Next Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the chrome-platform tree

On Thu, Jul 20, 2023 at 09:32:11AM -0600, Rob Barnes wrote:
> The patch to fix this issue was submitted here:
> https://lore.kernel.org/lkml/221b9a4a-275f-80a4-bba6-fb13a3beec0a@roeck-us.net/T/
> 
> However, it's looking unlikely that it will be accepted. So I think we
> should revert a6edd5f5d9cc for now. Let me know if I need to submit a
> revert patch?

No, you don't need to send a revert patch.  I'll remove it from the queue
if the symbol can't get exported for now.