[coreboot-gerrit] Patch merged into coreboot/master: efae69a elog: Fix regression that caused elog to omit "System boot" event

[gerrit at coreboot.org]

the following patch was just integrated into master:
commit efae69a4ef9455a8f2cd5afac7b3448ba298536e
Author: Julius Werner <jwerner at chromium.org>
Date:   Thu Feb 5 12:55:45 2015 -0800

    elog: Fix regression that caused elog to omit "System boot" event
    
    CL:243671 moved the initialization of elog_initialized around, which is
    now unfortunately so late that the ELOG_TYPE_BOOT event gets omitted
    because the code believes the log to be broken at that time. Good thing
    we now have a FAFT test for these things that I had of course been too
    lazy to run. -.-
    
    The real reason for moving that line was to put it after any point in
    elog_init() that could still error out. The problem is that we might add
    the "cleared" event before we try to shrink (which can fail and cause an
    error)... but those two things cannot happen at the same time, so it
    should be okay to flip them around and mark the elog as initialized in
    between.
    
    BRANCH=none
    BUG=chrome-os-partner:35940
    TEST=Ran firmware_EventLog on a Pinky, manually confirmed that I once
    again get "System boot" events.
    
    Change-Id: I12dcf4a8e47d302f6cd317194912c31db502bbaf
    Signed-off-by: Stefan Reinauer <reinauer at chromium.org>
    Original-Commit-Id: 4a1c0b861017ca25229b1042c4b37dda33e869f9
    Original-Change-Id: I4103779790e1a8a53ecabffd4316724035928ce6
    Original-Signed-off-by: Julius Werner <jwerner at chromium.org>
    Original-Reviewed-on: https://chromium-review.googlesource.com/246715
    Original-Reviewed-by: Duncan Laurie <dlaurie at chromium.org>
    Reviewed-on: http://review.coreboot.org/9503
    Tested-by: build bot (Jenkins)
    Reviewed-by: Julius Werner <jwerner at chromium.org>
    Reviewed-by: Patrick Georgi <pgeorgi at google.com>


See http://review.coreboot.org/9503 for details.

-gerrit