From: Tzung-Bi Shih <tzungbi@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Benson Leung <bleung@google.com>,
Guenter Roeck <groeck@chromium.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Rob Barnes <robbarnes@google.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the chrome-platform tree
Date: Thu, 20 Jul 2023 12:51:58 +0800 [thread overview]
Message-ID: <ZLi9bpof0KwqXD7H@google.com> (raw)
In-Reply-To: <20230720124611.45b25256@canb.auug.org.au>
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 until a fix is seen.
next prev parent reply other threads:[~2023-07-20 4:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-20 2:46 linux-next: build failure after merge of the chrome-platform tree Stephen Rothwell
2023-07-20 4:51 ` Tzung-Bi Shih [this message]
2023-07-20 5:00 ` Tzung-Bi Shih
2023-07-20 15:32 ` Rob Barnes
2023-07-21 7:42 ` Tzung-Bi Shih
-- strict thread matches above, loose matches on Subject: below --
2015-10-08 2:34 Stephen Rothwell
2015-10-08 23:43 ` Olof Johansson
2015-10-09 2:14 ` Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZLi9bpof0KwqXD7H@google.com \
--to=tzungbi@kernel.org \
--cc=bleung@google.com \
--cc=dmitry.torokhov@gmail.com \
--cc=groeck@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=robbarnes@google.com \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).