Hi All, The 4.0 final release is in rawhide and submitted for an update for Fedora 22 now. Given the release schedules for 4.1 and F22, we're going to stick with 4.0 for F22 GA. Please stick to fixes for F22 and we'll no longer keep that branch in sync with rawhide. The 4.1 merge window is open and active upstream as well. I'll be rebasing rawhide to those kernels likely later today or tomorrow. If you have things that are landing in 4.1 that you'd like enabled, please let us know. The only major feature I'm aware of that might land is kdbus, but the jury is still out on that one.

On Tue, Apr 14, 2015 at 8:05 AM, Peter Robinson <pbrobinson(a)gmail.com&gt; wrote: > On Tue, Apr 14, 2015 at 12:51 PM, Josh Boyer <jwboyer(a)fedoraproject.org&gt; wrote: >> Hi All, >> >> The 4.0 final release is in rawhide and submitted for an update for >> Fedora 22 now. Given the release schedules for 4.1 and F22, we're >> going to stick with 4.0 for F22 GA. Please stick to fixes for F22 and >> we'll no longer keep that branch in sync with rawhide. >> >> The 4.1 merge window is open and active upstream as well. I'll be >> rebasing rawhide to those kernels likely later today or tomorrow. If >> you have things that are landing in 4.1 that you'd like enabled, >> please let us know. The only major feature I'm aware of that might >> land is kdbus, but the jury is still out on that one. > > The ACPI 5.1 patch set I believe is on it's way in for this cycle so > we'd like that for aarch64 in F-23 (possibly not in F-22 but 4.1 for > that is a while out) but I'm unsure of the impact there on x86 too, > I'd assume nothing, but happy to coordinate with you as appropriate > there. Good to know. As far as I'm aware, new ACPI code drops just go into the tree and are picked up automatically on all architectures that use them and have it enabled. I'll keep an eye out for this on aarch64 but I don't expect any impacts on x86 beyond the normal code drop kind of issues.

Hi, I took the src RPM from rawhide and compiled it in F21 x86_64..

Would this be useful to anyone other than me?

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 16.04.2015 14:12, Josh Boyer wrote: > On Thu, Apr 16, 2015 at 6:17 AM, James Harrison > <jamesaharrisonuk(a)yahoo.co.uk&gt; wrote: >> I took the src RPM from rawhide and compiled it in F21 x86_64.. > For what purpose? I do something like that to help testing a new kernel version before it hits updates-testing.

> Also, generally you don't have to rebuild the kernel just because > it is an older Fedora release. I test rawhide/F22 kernel RPMs on > top of F21 userspace daily. It might be a issue for those few that want to or have to compile modules for that kernel -- or is it possible these days to use gcc 4.9 to compile modules for a kernel that was compiled with gcc 5.0?

All I wanted to do was compile the new kernel 4 and have it running on my machine. Rather than taking the stock kernel from kernel.org, I figured the Fedora build would have patches and the correct kernel options enabled. Also having an RPM would mean easy update. I built the 4.0 kernel using GCC: 4.9.2-6 and the kernel is: 3.19.3-200.fc21.x86_64