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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CA+Dqm31A6GNOpXB00X0aRd5TOpDgRAuTNh0Ce5YKm5EN+15gyg@mail.gmail.com>
Date:   Thu, 20 Jul 2023 09:32:11 -0600
From:   Rob Barnes <robbarnes@...gle.com>
To:     Tzung-Bi Shih <tzungbi@...nel.org>
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

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?

On Wed, Jul 19, 2023 at 11:00 PM Tzung-Bi Shih <tzungbi@...nel.org> wrote:
>
> On Thu, Jul 20, 2023 at 12:46:11PM +1000, Stephen Rothwell wrote:
> > After merging the chrome-platform tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> >
> > ERROR: modpost: "emergency_sync" [drivers/platform/chrome/cros_ec_lpcs.ko] undefined!
> >
> > Caused by commit
> >
> >   a6edd5f5d9cc ("platform/chrome: cros_ec_lpc: Emergency sync filesystem on EC panic")
> >
> > I have used the chrome-platform tree from next-20230719 for today.
>
> Thanks for reporting.  I have dropped the commit from chrome-platform for-next
> branch.