Bug 3415

Summary:	Only print kernel_configcheck warnings with a verbose setting
Product:	[Yocto Project Subprojects] Kernel	Reporter:	Darren Hart <dvhart>
Component:	kernel-tooling	Assignee:	Bruce Ashfield <bruce.ashfield>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Medium	CC:	yp.kernel.watcher, yp.watcher
Version:	1.3
Target Milestone:	1.4 M4
Hardware:	x86
OS:	Multiple
Whiteboard:
OS type for building Yocto:	---	Type of Regression:	---
Verified:		Documentation change:	---

Description Darren Hart 2012-11-13 18:29:09 UTC

The various complaints from kernel_configcheck now appear much more significant than they really are with the knotty2 interface. These would be better suited to a debug log, or when someone runs something like:

$ bitbake linux-yocto -c kernel_configcheck -f -DDD

Which we could advocate as being an integral step in the creation of a new BSP. Once released though, those warnings cause more confusion than the issues they report warrant.

Comment 1 Bruce Ashfield 2013-01-18 16:58:29 UTC

Implementation is complete. Will send out early in M4.

Comment 2 Bruce Ashfield 2013-02-05 16:03:40 UTC

kernel-yocto: make configuration audit details debug only

The details of the kernel configuration audit are typically a
debug action, so should be moved to bb.debug(). But in order
to maintain visibility of the results, a reference to the log
file is provided in the standard message.

(From OE-Core rev: 9ab80ad88d34622a81670cdc45cc3275fc3ebabe)

Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>