mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jason Wessel <jason.wessel@windriver.com>
Subject: Re: linux-next: usb tree build failure
Date: Wed, 19 Aug 2009 06:52:39 -0700	[thread overview]
Message-ID: <20090819135239.GB30892@kroah.com> (raw)
In-Reply-To: <20090819183402.77be5c3b.sfr@canb.auug.org.au>

On Wed, Aug 19, 2009 at 06:34:02PM +1000, Stephen Rothwell wrote:
> Hi Greg,
> 
> Today's linux-next build (x86_64 allmodconfig) failed like this:
> 
> arch/x86/built-in.o: In function `setup_early_printk':
> early_printk.c:(.init.text+0x159de): undefined reference to `early_dbgp_init'
> early_printk.c:(.init.text+0x159f9): undefined reference to `early_dbgp_console'
> 
> Caused by commit 77f162cc16ff4bff1adefe47dbe48ab6b2d9247b ("USB: ehci
> early_printk: split ehci debug driver from early_printk.c").
> 
> I have reverted that commit for today (along with commits
> 37e541af790703d66ba88cf3a71b5ae97654b753 ("USB: early_printk: insert cr
> prior to nl as needed"), 71c0553ae63d2738a126d4f5b37730dfaa7a2fd7 ("USB:
> ehci-dbgp: Execute early BIOS hand off"),
> 3f038d06f259fd02142aaaaa47addfb4934d4faa ("USB: early_printk: EHCI debug
> controller initialization delays") and
> f6ee359e79de27b46213f8b5293251a26bc22b1e ("USB: ehci-dbgp: stability
> improvements and external re-init") that depended on it).

Ick.  Jason, what happened here?  It builds on i386 :)

thanks,

greg k-h

  reply	other threads:[~2009-08-19 13:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-19  8:34 Stephen Rothwell
2009-08-19 13:52 ` Greg KH [this message]
2009-08-19 23:45   ` Greg KH
2009-08-19 23:58     ` Stephen Rothwell
2010-02-02  6:10 Stephen Rothwell
2010-02-02 13:53 ` Greg KH
2010-02-02 22:33   ` 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=20090819135239.GB30892@kroah.com \
    --to=greg@kroah.com \
    --cc=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
Powered by JetHome