From: Jason Wessel <jason.wessel@windriver.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
kgdb-bugreport@lists.sourceforge.net
Subject: Re: linux-next: Tree for December 31 (kgdb)
Date: Fri, 01 Jan 2010 23:35:04 -0600 [thread overview]
Message-ID: <4B3EDB08.6080707@windriver.com> (raw)
In-Reply-To: <20091231110747.5efc1efa.randy.dunlap@oracle.com>
Randy Dunlap wrote:
> On Thu, 31 Dec 2009 11:23:14 +1100 Stephen Rothwell wrote:
>
>
>> Hi all,
>>
>> This one has also not had the build testing *between* merges, but has had
>> all the normal build testing at the end.There may be more unbisectable
>> points in the tree then usual.
>>
>> Changes since 20091230:
>>
>> My fixes tree is again empty with the equivalent of its patch being added
>> to Linus' tree.
>>
>
>
> when CONFIG_PROC_FS is not enabled:
>
> kernel/built-in.o: In function `kdb_summary':
> kdb_main.c:(.text+0x6a413): undefined reference to `_meminfo_proc_show'
>
>
>
Fixed.
> when CONFIG_KGDB_KDB is not enabled:
>
> kernel/built-in.o: In function `kdb_dmesg':
> kdb_main.c:(.text+0x6b5c4): undefined reference to `kdb_syslog_data'
>
>
When CONFIG_KGDB_KDB is not set, it is not possible to compile
kdb_main.c. This one was actually due to compiling a kernel with
CONFIG_PRINTK=n and CONFIG_KGDB_KDB=y.
It is fixed.
> when CONFIG_KDB_KEYBOARD is not enabled:
>
> drivers/built-in.o: In function `cleanup_kgdboc':
> kgdboc.c:(.text+0x1ee2df): undefined reference to `kdb_get_kbd_char'
> drivers/built-in.o: In function `configure_kgdboc':
> kgdboc.c:(.text+0x1ee463): undefined reference to `kdb_get_kbd_char'
>
>
>
If CONFIG_KDB_KEYBOARD is not enabled there is no way to get these
functions. This one was actually due to compiling CONFIG_KDB_KEYBOARD=y
and CONFIG_VT_CONSOLE=n.
It is fixed as well.
The changes are folded into the 2 offending patches in the kdb patches
in the kgdb-next branch for proper bisecting patches.
Thanks for the report.
Jason.
prev parent reply other threads:[~2010-01-02 5:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-31 0:23 linux-next: Tree for December 31 Stephen Rothwell
2009-12-31 19:07 ` linux-next: Tree for December 31 (kgdb) Randy Dunlap
2009-12-31 19:20 ` Tony Luck
2010-01-01 1:04 ` Stephen Rothwell
2010-01-01 21:18 ` Tony Luck
2010-01-02 5:33 ` Jason Wessel
2010-01-02 11:32 ` Stephen Rothwell
2010-01-02 5:35 ` Jason Wessel [this message]
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=4B3EDB08.6080707@windriver.com \
--to=jason.wessel@windriver.com \
--cc=kgdb-bugreport@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=randy.dunlap@oracle.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).