[coreboot-gerrit] Patch merged into coreboot/master: elog: Ensure eventlog will always get initialized when configured in

[gerrit at coreboot.org]

the following patch was just integrated into master:
commit a46ee4d34d6b7ce7d47882779c7fb36270ccbda1
Author: Julius Werner <jwerner at chromium.org>
Date:   Mon Aug 8 16:18:28 2016 -0700

    elog: Ensure eventlog will always get initialized when configured in
    
    Commit 0d9cd92e (chromeos: Clean up elog handling) removed the
    individual elog_init() calls from mainboards that did them and automated
    adding certain events through the boot state machine. Unfortunately,
    the new code would sometimes not log any specific event at all, and
    thereby also never call elog_init() (through elog_add_event()) which
    adds the "System boot" event.
    
    We can assume that any board that configures the eventlog at all
    actually wants to use it, so let's just add another call to elog_init()
    to the boot state machine so we can ensure it gets called at least once.
    
    BRANCH=None
    BUG=chrome-os-partner:56001
    TEST=Booted Kevin, confirmed that eventlog code runs again.
    
    Change-Id: Ibe7bfc94b3e3d11ba881399a39f9915991c89d8c
    Signed-off-by: Julius Werner <jwerner at chromium.org>
    Reviewed-on: https://review.coreboot.org/16118
    Reviewed-by: Aaron Durbin <adurbin at chromium.org>
    Tested-by: build bot (Jenkins)


See https://review.coreboot.org/16118 for details.

-gerrit