From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"kernelci.org bot" <bot@kernelci.org>,
Dmitry Safonov <dima@arista.com>
Subject: linux-next: build failure after merge of Linus' tree
Date: Mon, 20 Apr 2020 21:35:19 +1000 [thread overview]
Message-ID: <20200420213519.3c5ee143@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 436 bytes --]
Hi all,
[reported by the kernelci.org bot]
For some time, building Linus' tree, the linux-next build (mips
mtx1_defconfig) fails like this:
ERROR: modpost: "sysrq_toggle_support" [drivers/tty/serial/serial_core.ko] undefined!
ERROR: modpost: "sysrq_mask" [drivers/tty/serial/serial_core.ko] undefined!
Caused by commit
68af43173d3f ("serial/sysrq: Add MAGIC_SYSRQ_SERIAL_SEQUENCE")
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-04-20 11:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-20 11:35 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-02-03 1:59 linux-next: build failure after merge of Linus' tree Stephen Rothwell
2025-02-03 2:56 ` Jens Axboe
2024-09-26 0:04 Stephen Rothwell
2024-09-26 7:36 ` Alice Ryhl
2024-09-26 8:13 ` Stephen Rothwell
2024-09-26 8:24 ` Miguel Ojeda
2024-09-26 12:49 ` Sedat Dilek
2024-09-26 12:58 ` Miguel Ojeda
2024-09-26 14:44 ` Sedat Dilek
2024-09-26 14:57 ` Miguel Ojeda
2016-08-08 1:58 Stephen Rothwell
2016-08-08 15:37 ` Doug Ledford
2016-08-08 21:53 ` Stephen Rothwell
2016-08-08 23:30 ` Doug Ledford
2016-08-08 23:59 ` Stephen Rothwell
2016-08-09 8:54 ` Leon Romanovsky
2016-08-09 12:45 ` Doug Ledford
2015-10-07 22:44 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=20200420213519.3c5ee143@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=bot@kernelci.org \
--cc=dima@arista.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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