Take a look at this post. It looks like Quarx now has a 3.10 kernel booting on the Motorola Defy!
I'll see if I can work on it, I had my computer syncing the cm12 repo last night into this morning. I'll make sure I can build for my Nexus 4, then I'll see if I can work on it. I'll have to clean the dust off my old DX. ?For anyone willing to set aside some time to help just make sure you can work Google and you have a 64 bit Linux machine with a working build environment. Lollipop WILL NOT compile on a x86 system. I store my android projects in /android and further into each project's subdirectory, but do whatever you want with your directories. I have modified the cm11 local_manifest to build cm12.1 although it doesn't compile succesfully I managed a 90 minute clean build till I had an error, which is impressive since I figured it'd be much shorter than that. My local_manifest can be found on my Gdrive and should be placed in /android/CM12.1/.repo/local_manifests. Keep in mind to show hidden files within Linux you need to use ctrl+h (assuming you're using a GUI instead of terminal.)
Now to get things running hold ctrl+t to open terminal and run:
mkdir android/CM12.1 && cd android/CM12.1 && repo init -u git://github.com/CyanogenMod/android.git -b cm-12.1 && repo sync -j4
Now move local_manifest.xml where it should go and run
repo sync -j4 && lunch
(select shadow's number and hit enter)
time make otapackage -j4
time is an argument used to count how long the build took, make otapackage is essentially a build command to say "hey make it flashable," and -j# is an argument used to declare how many threads you want to use while you sync/compile.
This WON'T compile but if you edit files to get it to boot (priority #1) please share and upload to Github, collaboration is key to keeping our device alive. Thanks and good luck everyone.