{"push_id":635177927,"size":2,"distinct_size":2,"ref":"refs/heads/msm_misc","head":"28cfeb12b1cc2841460b0a768e19facdb1992cd2","before":"3779e335e37d05b8c6dc970cdcc9c5c101b9e5c2","commits":[{"sha":"21760d1c54ead25cebcf1b3372b202fdd1c8c763","author":{"email":"4f433e929189a8c50d5716e271a7ceb94de7ee2a@gmail.com","name":"Brandon Berhent"},"message":"msm: pm_power_collapse remove pointless BUG_ON\nBUG_ON() is a big hammer according to Linus, and should only be used if there\nis major corruption that cannot be recovered from.\n\nWe can easily recover from the internal msm-pm cpu_count being incorrect, and\nhave no need to throw a BUG_ON.\n\nInstead of BUG_ON(), use a pr_warn and reset cpu_count to num_online_cpus()","distinct":true,"url":"https://api.github.com/repos/bbedward/ZenKernel_Shamu/commits/21760d1c54ead25cebcf1b3372b202fdd1c8c763"},{"sha":"28cfeb12b1cc2841460b0a768e19facdb1992cd2","author":{"email":"4f433e929189a8c50d5716e271a7ceb94de7ee2a@gmail.com","name":"Brandon Berhent"},"message":"msm: pm: use -fno-aggressive-loop-optimizations\nSolving a silly GCC warning with a BUG_ON is terrible practice.\nQComm needs to fix this upstream, but for now this is the quickest fix.","distinct":true,"url":"https://api.github.com/repos/bbedward/ZenKernel_Shamu/commits/28cfeb12b1cc2841460b0a768e19facdb1992cd2"}]}