public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Benson Leung <bleung@google•com>,
	Guenter Roeck <groeck@chromium•org>,
	Dmitry Torokhov <dmitry.torokhov@gmail•com>
Cc: Rob Barnes <robbarnes@google•com>,
	Tzung-Bi Shih <tzungbi@kernel•org>,
	Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
	Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: build failure after merge of the chrome-platform tree
Date: Thu, 20 Jul 2023 12:46:11 +1000	[thread overview]
Message-ID: <20230720124611.45b25256@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 421 bytes --]

Hi all,

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.

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

             reply	other threads:[~2023-07-20  2:46 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-20  2:46 Stephen Rothwell [this message]
2023-07-20  4:51 ` linux-next: build failure after merge of the chrome-platform tree Tzung-Bi Shih
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=20230720124611.45b25256@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=bleung@google$(echo .)com \
    --cc=dmitry.torokhov@gmail$(echo .)com \
    --cc=groeck@chromium$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=robbarnes@google$(echo .)com \
    --cc=tzungbi@kernel$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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