mirror of
https://github.com/LineageOS/android_kernel_samsung_msm8226.git
synced 2026-09-28 00:00:22 +02:00
Kevin F. Haggerty
983729ba91
* This principally was identified when the R recovery started issuing reboot commands such as "userrequested,recovery" or "userrequested,fastboot". While it's not 100% clear that userrequested is supposed to be followed by a reboot *source* as opposed to a target, it illuminated the fact that our kernel gets stuck rebooting to the same target/reason when an unknown command is issued. * It seems much more logical to normal people that the kernel go ahead and reboot to the "normal" (read: Android system) target when the one passed to the kernel isn't known, as opposed to getting stuck in something like recovery forever. Change-Id: Id63a31c9855b72955b89694ecac522e6569d84ac Signed-off-by: Kevin F. Haggerty <haggertk@lineageos.org>