From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Daniel Thompson <daniel.thompson@linaro.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Douglas Anderson <dianders@chromium.org>
Subject: linux-next: build failure after merge of the kgdb tree
Date: Wed, 20 May 2020 00:05:24 +1000 [thread overview]
Message-ID: <20200520000524.69af8a86@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1593 bytes --]
Hi all,
After merging the kgdb tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/tty/serial/kgdboc.c:418:13: error: expected declaration specifiers or '...' before string constant
418 | early_param("ekgdboc", kgdboc_early_init);
| ^~~~~~~~~
drivers/tty/serial/kgdboc.c:418:24: error: expected declaration specifiers or '...' before 'kgdboc_early_init'
418 | early_param("ekgdboc", kgdboc_early_init);
| ^~~~~~~~~~~~~~~~~
drivers/tty/serial/kgdboc.c:546:13: error: expected declaration specifiers or '...' before string constant
546 | early_param("kgdboc_earlycon", kgdboc_earlycon_init);
| ^~~~~~~~~~~~~~~~~
drivers/tty/serial/kgdboc.c:546:32: error: expected declaration specifiers or '...' before 'kgdboc_earlycon_init'
546 | early_param("kgdboc_earlycon", kgdboc_earlycon_init);
| ^~~~~~~~~~~~~~~~~~~~
drivers/tty/serial/kgdboc.c:505:19: warning: 'kgdboc_earlycon_init' defined but not used [-Wunused-function]
505 | static int __init kgdboc_earlycon_init(char *opt)
| ^~~~~~~~~~~~~~~~~~~~
drivers/tty/serial/kgdboc.c:411:19: warning: 'kgdboc_early_init' defined but not used [-Wunused-function]
411 | static int __init kgdboc_early_init(char *opt)
| ^~~~~~~~~~~~~~~~~
Caused by commit
220995622da5 ("kgdboc: Add kgdboc_earlycon to support early kgdb using boot consoles")
I have used the kgdb tree from next-20200518 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2020-05-19 14:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 14:05 Stephen Rothwell [this message]
2020-05-19 14:58 ` linux-next: build failure after merge of the kgdb tree Doug Anderson
2020-05-19 15:52 ` Doug Anderson
-- strict thread matches above, loose matches on Subject: below --
2010-03-23 4:04 Stephen Rothwell
2010-03-25 4:43 ` Stephen Rothwell
2010-03-25 4:59 ` Dmitry Torokhov
2010-05-21 0:21 ` Stephen Rothwell
2010-05-21 0:49 ` Jason Wessel
2010-05-21 1:09 ` Stephen Rothwell
2010-05-21 1:23 ` Dmitry Torokhov
2010-05-21 1:28 ` Jason Wessel
2010-05-24 18:17 ` Dmitry Torokhov
2010-05-24 20:04 ` Jason Wessel
2010-05-24 20:34 ` Dmitry Torokhov
2010-05-24 20:50 ` Jason Wessel
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=20200520000524.69af8a86@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=daniel.thompson@linaro.org \
--cc=dianders@chromium.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;
as well as URLs for NNTP newsgroup(s).