-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 10/27/14, 9:39 PM, Alexander Graf wrote: > Hi kernel gurus, > > There were quite a good number of bug fixes and necessary features > in post-3.16 as well as some patches that are missing upstream to > make arm64 a shiny out of the box experience. > > I would like to shove the patches below into our openSUSE-13.2 > branch. I have a properly trimmed down (and adjusted) version of > the changes below based on 3.18 and an untested variant on top of > 3.17. > > What is the strategy with 13.2 going to be? Are we going to uprev > the kernel for it? Is it going to jump to 3.17, so should I push > the changes here into the 13.2 branch the stable branch and the > master branch? Or would master and 13.2 suffice? > > Also, if you think the changes below are too intrusive, please let > me know. I've tried to double-check that they basically only touch > arm64 specific code paths with a few shared ppc blocks. But the > likelyhood for x86 breakage is low: >
I suppose the first question is for the ARM folks: Do you have any need/intention of keeping the kABI stable? If so, then a lot of this patchset won't fly. - -Jeff - -- Jeff Mahoney SUSE Labs -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.19 (Darwin) iQIcBAEBAgAGBQJUUBN6AAoJEB57S2MheeWyjXoP/1CZuV0UzOkw1YgSNIXzuMfr y7cDiUbcoFL3rbVqtmVY9LVHGrlMy0UcXsNCDKx9VZzADSUn+ejyHSJkk67wpliY uZ9DprN9T2R79CHzVMJiMS8s2op5qBXbC3XsXkjtZmXhbroDYmWt2JbVzf50lHDl BWsTZlTGw52n1a669pY3WTkfHmqgK5xxfnEsROFfJ2Bxg3RpFeyFvQP0MSudAmxC QwJ97xSk2xe+wsA4NCa6Lfo3x6bJiD8hE0Mk6/N//0s3NYQ9GaIeUz6oDrCh186d oEg9+VQ2SozW4g9Zxt/DV+JK/8GWKCLhL/KvzMQnN7wrWS5fdLkGFTwRAZhjZoog tLXj2klfZYfG0z1MLnc+d89AX6SzUjS6YpmOi4AoBDUtyEkfXC/T5toaqHB2/JLq yjtkclYThnpysavj/WXtptMYUDqvJJu/T0Dnr3074kmr5TeoSJ6jOQ2Py/nfoyOd w8CR3BYZmjgVSPNdjMItmXq2IJ9pjOEWbdAyRmfzWswZBo07Jsz859DxHz2r9ARf ZAlEf8H0Eb+b2+M4a6xryMbAavk5k9QkK6XoWaE9d6G6x3oAFwVo14BbIGbCJwnh DzxCJ2P9YmyT4kbju4BrKgDZfkOlLVQE4BgSG3o/lFMtdYKiVu3EHVpF+6FX/VBC 69xjhNIb/UtF3T+yjvfg =Tg0e -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
