{"push_id":624607264,"size":1,"distinct_size":1,"ref":"refs/heads/cm-12.1","head":"7324c317da49c0c89534b23f1abb95de43e991c0","before":"a73a753e149768ec3bbc40b91f330e06008e12c0","commits":[{"sha":"7324c317da49c0c89534b23f1abb95de43e991c0","author":{"email":"b702a20f0628efd8f619b9c92a0cb3de4b542e20@hotmail.com","name":"UpInTheAir"},"message":"CHROMIUM: clocksource: allow clocksources to be selected earlier during boot [Andrew Bresticker]\n\nGlobal and per-CPU timers ought to be initialized once SMP initialization\nis complete.  Although the clocksources associated with these timers may\nnot be registered until later in the boot process, they should be ready\nto go once registered.  We'd like to stop using the super low-resolution\nboot clocksource (jiffies) as soon as possible since devices may rely on\naccurate timekeeping while being brought up during boot, so move\nclocksource_done_booting() to arch_initcall time so that we can switch\nto a higher-resolution clocksrouce earlier in the boot process.\n\nTEST=Pit and Lumpy both still boot reliably.  Boot time on Pit improves\nconsiderably:\nBefore: [    3.032967] VFS: Mounted root ...\nAfter:  [    1.855936] VFS: Mounted root ...\nLumpy boot time improves very slightly:\nBefore: [    1.786347] VFS: Mounted root ...\nAfter:  [    1.754297] VFS: Mounted root ...\n\nSigned-off-by: Andrew Bresticker <abrestic@chromium.org>\nReviewed-by: Sonny Rao <sonnyrao@chromium.org>\nReviewed-by: Sameer Nanda <snanda@chromium.org>\nSigned-off-by: Luis Cruz <ljc2491@gmail.com>\nSigned-off-by: Pranav Vashi <neobuddy89@gmail.com>","distinct":true,"url":"https://api.github.com/repos/sigma-1/kernel_samsung_lt03wifi/commits/7324c317da49c0c89534b23f1abb95de43e991c0"}]}