<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On 3 November 2014 17:13, Koen Kooi <span dir="ltr"><<a href="mailto:koen@dominion.thruhere.net" target="_blank">koen@dominion.thruhere.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Most likely not because we already have meta-aarch64 for the toolchain and kernel support. But aside from that, the past few *years* it wasn't a problem to get aarch64 related patches merged into OE-core, so why is there suddenly such a problem now?<br></blockquote><div><br></div><div>Because oe-core was frozen and we were only taking serious fixes. Now there's a number of related patches that can and should be bundled up so they can be tested as a whole.</div><div> <br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
Furthermore, this libpng patch isn't strictly an aarch64 patch, it fixes a previous commit that should have been flagged in review as being wrong for using double qualifiers in a bogus way. So why did the culprit go in and the fix submitted 3 days later not?</blockquote></div></div><div class="gmail_extra"><br>That patch in particular? Because humans are not infallible. FWIW, this is in my MUT now.<br></div><div class="gmail_extra"><br></div><div class="gmail_extra">Ross</div></div>