linux-kernel - Re: linux-next: usb tree build failure

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090819135239.GB30892@kroah.com>
Date:	Wed, 19 Aug 2009 06:52:39 -0700
From:	Greg KH <greg@...ah.com>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Jason Wessel <jason.wessel@...driver.com>
Subject: Re: linux-next: usb tree build failure

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/