7 Jun
2017
7 Jun
'17
3:47 a.m.
On 22 May 2017 at 11:48, Tom Rini trini@konsulko.com wrote:
In the case where a new build only decreases sizes and does not increase any size we still want to report what functions have been dropped when doing a bloat comparison.
Cc: Simon Glass sjg@chromium.org Signed-off-by: Tom Rini trini@konsulko.com
This is important when doing Kconfig migrations and a given target has only decreased in size, we want to know what was dropped so we can see what needs to be re-enabled.
tools/buildman/builder.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Reviewed-by: Simon Glass sjg@chromium.org
Applied to u-boot-dm, thanks!