linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
	Jason Wessel <jason.wessel@windriver.com>
Cc: 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: Thu, 31 Dec 2009 11:07:47 -0800	[thread overview]
Message-ID: <20091231110747.5efc1efa.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20091231112314.a51e160b.sfr@canb.auug.org.au>

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'


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_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'



---
~Randy

  reply	other threads:[~2009-12-31 19:08 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 ` Randy Dunlap [this message]
2009-12-31 19:20   ` linux-next: Tree for December 31 (kgdb) 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

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=20091231110747.5efc1efa.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=jason.wessel@windriver.com \
    --cc=kgdb-bugreport@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --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).