Pull the reboot START logging out of job.reboot; the reboot END logging is
queued up by methods external to job.reboot (i.e. kernel.boot) and so the
START logging should be run from there as well; otherwise it's not possible
to call job.reboot properly without having to first queue up your own END
logging. The default should just work.
Risk: Low
Visibility: Code changes only; should have the same user-visible behaviour.
Signed-off-by: John Admanski <jadmanski@google.com>
git-svn-id: http://test.kernel.org/svn/autotest/trunk@2316 592f7852-d20e-0410-864c-8624ca9c26a4
3 files changed