Re: [opensuse-kernel] [RFC] arm64 backports for 3.16

Am 28.10.2014 um 23:06 schrieb Jeff Mahoney :

-----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.

I don't think it makes sense to have a stable kabi on something that runs on 0 platforms ;). People won't be able to tell the difference, because the unpatched kernel wouldn't run on anything and we'd have to make the patched one the minimum version people compile against. Alex -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org