{"push_id":2764434672,"size":2,"distinct_size":2,"ref":"refs/heads/oreo-m6-2","head":"546e3f034a1bfde0a03f3a00082ae1e7561e6df8","before":"898dae785a9a5cfb58e2062638d5ee954bac377c","commits":[{"sha":"0b62d39b90f92f05dc31d59f0a152cc59e7f4e64","author":{"name":"Kevin Hao","email":"7b5c7263b051e4f30fdb05a718aacc347c3275cd@gmail.com"},"message":"arm64: kill off the libgcc dependency\n\nThe arm64 kernel builds fine without the libgcc. Actually it should not\nbe used at all in the kernel. The following are the reasons indicated\nby Russell King:\n\n  Although libgcc is part of the compiler, libgcc is built with the\n  expectation that it will be running in userland - it expects to link\n  to a libc.  That's why you can't build libgcc without having the glibc\n  headers around.\n\n  [...]\n\n  Meanwhile, having the kernel build the compiler support functions that\n  it needs ensures that (a) we know what compiler support functions are\n  being used, (b) we know the implementation of those support functions\n  are sane for use in the kernel, (c) we can build them with appropriate\n  compiler flags for best performance, and (d) we remove an unnecessary\n  dependency on the build toolchain.\n\nSigned-off-by: Kevin Hao <haokexin@gmail.com>\nAcked-by: Will Deacon <will.deacon@arm.com>\nSigned-off-by: Catalin Marinas <catalin.marinas@arm.com>","distinct":true,"url":"https://api.github.com/repos/mortezadadgar/bullhead/commits/0b62d39b90f92f05dc31d59f0a152cc59e7f4e64"},{"sha":"546e3f034a1bfde0a03f3a00082ae1e7561e6df8","author":{"name":"mortezadadgar","email":"758c33313807b59ca7c04a1b06f46eec4f52c52f@gmail.com"},"message":"arm64/Makefile: Add optimization flags for crypto+crc","distinct":true,"url":"https://api.github.com/repos/mortezadadgar/bullhead/commits/546e3f034a1bfde0a03f3a00082ae1e7561e6df8"}]}
{"actor":{"display_login":"mortezadadgar"}}