From: Jason Wessel <jason.wessel@windriver.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: kgdb tree build failure
Date: Wed, 23 Dec 2009 21:58:52 -0600 [thread overview]
Message-ID: <4B32E6FC.40103@windriver.com> (raw)
In-Reply-To: <20091224115624.77c910d6.sfr@canb.auug.org.au>
Stephen Rothwell wrote:
> Hi Jason,
>
> Today's linux-next build (i386 defconfig) failed like this:
>
> drivers/built-in.o: In function `drm_fb_kdb_enter':
> drm_fb_helper.c:(.text+0x6567a): undefined reference to `kgdb_active'
> drivers/built-in.o: In function `drm_fb_helper_free':
> (.text+0x65ec7): undefined reference to `dbg_kms_console_ops_unregister'
> drivers/built-in.o: In function `drm_fb_helper_single_fb_probe':
> (.text+0x6645d): undefined reference to `dbg_kms_console_ops_register'
>
> Clearly, the kgdb patches need some more testing. Please remove them
> from linux-next until that is done.
>
>
All the kdb patches were dropped from kgdb-next / linux-next. All the
embedded type configs build and boot just fine. The root of the
problem was that there was a gap in testing all the various combinations
where you can builds some things as a module or somethings as a built in.
The error you reported is already fixed, but the code base will not be
resubmitted until a new round of build and boot tests are completed.
Thanks,
Jason.
next prev parent reply other threads:[~2009-12-24 3:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-24 0:56 linux-next: kgdb tree build failure Stephen Rothwell
2009-12-24 3:58 ` Jason Wessel [this message]
2009-12-24 12:18 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2010-01-04 5:42 Stephen Rothwell
2010-01-04 5:44 ` Stephen Rothwell
2010-01-04 12:55 ` Jason Wessel
2010-01-04 13:04 ` Stephen Rothwell
2009-12-24 0:16 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=4B32E6FC.40103@windriver.com \
--to=jason.wessel@windriver.com \
--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