linux-kernel - Re: [PATCH 3/3]x86_64: early_printk for early debug port support

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]

Date:	Tue, 22 May 2007 12:43:35 -0700
From:	"Yinghai Lu" <yhlu.kernel@...il.com>
To:	"Andrew Morton" <akpm@...ux-foundation.org>
Cc:	"Andi Kleen" <ak@...e.de>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	"Greg KH" <gregkh@...e.de>, "Bjorn Helgaas" <bjorn.helgaas@...com>,
	"Vivek Goyal" <vgoyal@...ibm.com>,
	"linux kernel mailing list" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 3/3]x86_64: early_printk for early debug port support

On 5/22/07, Andrew Morton <akpm@...ux-foundation.org> wrote:
> OK, I went through the exercise of removing all the unused-symbol warnings
> which DBGP_DEBUG=0 produces and guess what?  None of the code which you've
> added does anything!  It all has to be moved inside DBGP_DEBUG to avoid
> unused-symbol warnings.  It's all a big no-op if DBGP_DEBUG=0.  I suspect
> you did all your test and devel with DBGP_DEBUG=1, then turned DBGP_DEBUG
> off and shipped the code without retesting?

Thanks. will format and test again. also will use KMail to mail it out.

YH
-
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/