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.
Thanks.
josh
On Tue, Apr 14, 2015 at 12:51 PM, Josh Boyer jwboyer@fedoraproject.org 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.
Peter
On Tue, Apr 14, 2015 at 8:05 AM, Peter Robinson pbrobinson@gmail.com wrote:
On Tue, Apr 14, 2015 at 12:51 PM, Josh Boyer jwboyer@fedoraproject.org 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.
josh
On 04/14/2015 06:53 AM, Josh Boyer wrote:
On Tue, Apr 14, 2015 at 8:05 AM, Peter Robinson pbrobinson@gmail.com wrote:
On Tue, Apr 14, 2015 at 12:51 PM, Josh Boyer jwboyer@fedoraproject.org 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.
As co-author of those patches, the last I heard we were in linux-next, and could possibly be merged into 4.1; there may be some push back that would cause it to be delayed to 4.2, but that's uncertain.
The patches themselves should have no effect on any other architecture that uses ACPI; they haven't yet, but I'm just paranoid enough to think it's not impossible :).
Hi, I took the src RPM from rawhide and compiled it in F21 x86_64..
Would this be useful to anyone other than me?
Best regards, James Harrison
-------------------------------------------- On Tue, 14/4/15, Josh Boyer jwboyer@fedoraproject.org wrote:
Subject: 4.0 final, 4.1 merge window, and us To: "Kernel Fedora" kernel@lists.fedoraproject.org Cc: "arm" arm@lists.fedoraproject.org Date: Tuesday, 14 April, 2015, 12:51
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.
Thanks.
josh _______________________________________________ kernel mailing list kernel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kernel
On Thu, Apr 16, 2015 at 6:17 AM, James Harrison jamesaharrisonuk@yahoo.co.uk wrote:
Hi, I took the src RPM from rawhide and compiled it in F21 x86_64..
For what purpose?
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.
Would this be useful to anyone other than me?
I guess the answer to that depends on why you rebuilt it.
josh
-----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@yahoo.co.uk 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?
Cu knurd
On Fri, Apr 17, 2015 at 08:44:20AM +0200, Thorsten Leemhuis wrote:
-----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@yahoo.co.uk 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.
You could pull it out of koji too though.
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?
Right, that's why I asked James why he rebuilt things. Out of tree modules would require a rebuild against whatever kernel version you have locally. As far as I know, you still have to have matching compiler versions between your kernel and modules.
Aside from that, I can't think of any major reason to rebuild unless you're modifying the code (or you think there's a compiler bug).
josh
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
Aside from that, I can't think of any major reason to rebuild unless
you're modifying the code (or you think there's a compiler bug). No bugs/not modifying any code. Just curious to see if the new kernel would run on my machine. James
On Friday, 17 April 2015, 12:47, Josh Boyer jwboyer@fedoraproject.org wrote:
On Fri, Apr 17, 2015 at 08:44:20AM +0200, Thorsten Leemhuis wrote:
-----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@yahoo.co.uk 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.
You could pull it out of koji too though.
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?
Right, that's why I asked James why he rebuilt things. Out of tree modules would require a rebuild against whatever kernel version you have locally. As far as I know, you still have to have matching compiler versions between your kernel and modules.
Aside from that, I can't think of any major reason to rebuild unless you're modifying the code (or you think there's a compiler bug).
josh _______________________________________________ kernel mailing list kernel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/kernel
On Fri, 2015-04-17 at 14:18 +0000, James Harrison wrote:
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
If your goal is to have 4.0 running on Fedora 21, pulling it from koji should work fine. If you would rather have it without debug turned on, you can get it from:
http://fedoraproject.org/wiki/RawhideKernelNodebug
Justin
On Fri, 2015-04-17 at 10:21 -0500, Justin M. Forbes wrote:
On Fri, 2015-04-17 at 14:18 +0000, James Harrison wrote:
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
If your goal is to have 4.0 running on Fedora 21, pulling it from koji should work fine. If you would rather have it without debug turned on, you can get it from:
http://fedoraproject.org/wiki/RawhideKernelNodebug
Justin
Actually, a bit of a thinko there. You are wanting 4.0, not 4.1. Sorry for the confusion.
Justin
kernel@lists.fedoraproject.org
-
Al Stone -
James Harrison -
Josh Boyer -
Justin Forbes -
Peter Robinson -
Thorsten Leemhuis