Can some, please, apply the following patch to the fedora kernel? http://marc.info/?l=linux-kernel&m=133072333922354&w=2 . It sets the NumLock state on the keyboard according to the data in the bios.
On Sat, Mar 3, 2012 at 9:41 AM, Joshua C. joshuacov@googlemail.com wrote:
Can some, please, apply the following patch to the fedora kernel? http://marc.info/?l=linux-kernel&m=133072333922354&w=2 . It sets the NumLock state on the keyboard according to the data in the bios.
It'll got into F17/rawhide when it makes it into Linus' tree. If you get it into the stable release, it will wind up in F15/F16 relatively soon.
That should be sufficient, shouldn't it? At the least I'd like to wait for it to wind up in Linus' tree.
josh
2012/3/3 Josh Boyer jwboyer@gmail.com:
On Sat, Mar 3, 2012 at 9:41 AM, Joshua C. joshuacov@googlemail.com wrote:
Can some, please, apply the following patch to the fedora kernel? http://marc.info/?l=linux-kernel&m=133072333922354&w=2 . It sets the NumLock state on the keyboard according to the data in the bios.
It'll got into F17/rawhide when it makes it into Linus' tree. If you get it into the stable release, it will wind up in F15/F16 relatively soon.
That should be sufficient, shouldn't it? At the least I'd like to wait for it to wind up in Linus' tree.
josh
This could take ages, couldn't it? You know that I have absolutely no influence what goes and when into his tree. In that case I could have saved myself writing this (and the first) email!
On Sat, 2012-03-03 at 19:31 +0100, Joshua C. wrote:
2012/3/3 Josh Boyer jwboyer@gmail.com:
On Sat, Mar 3, 2012 at 9:41 AM, Joshua C. joshuacov@googlemail.com wrote:
Can some, please, apply the following patch to the fedora kernel? http://marc.info/?l=linux-kernel&m=133072333922354&w=2 . It sets the NumLock state on the keyboard according to the data in the bios.
It'll got into F17/rawhide when it makes it into Linus' tree. If you get it into the stable release, it will wind up in F15/F16 relatively soon.
That should be sufficient, shouldn't it? At the least I'd like to wait for it to wind up in Linus' tree.
josh
This could take ages, couldn't it? You know that I have absolutely no influence what goes and when into his tree. In that case I could have saved myself writing this (and the first) email!
I don't know about ages, the patch has been acked, and looks likely to make the 3.4 merge window. I does seem rather low risk, but it is more a feature than a bug fix at this point, and might have some difficulty making it into the stable series. The functionality it provides is nice to have, but not something that is critical for us to pick up in the Fedora tree before it makes upstream. This isn't to say that we don't like the patch, or don't agree with it. Simply that we certainly prefer that features go through upstream first.
Justin
2012/3/3 Justin M. Forbes jforbes@redhat.com:
On Sat, 2012-03-03 at 19:31 +0100, Joshua C. wrote:
2012/3/3 Josh Boyer jwboyer@gmail.com:
On Sat, Mar 3, 2012 at 9:41 AM, Joshua C. joshuacov@googlemail.com wrote:
Can some, please, apply the following patch to the fedora kernel? http://marc.info/?l=linux-kernel&m=133072333922354&w=2 . It sets the NumLock state on the keyboard according to the data in the bios.
It'll got into F17/rawhide when it makes it into Linus' tree. If you get it into the stable release, it will wind up in F15/F16 relatively soon.
That should be sufficient, shouldn't it? At the least I'd like to wait for it to wind up in Linus' tree.
josh
This could take ages, couldn't it? You know that I have absolutely no influence what goes and when into his tree. In that case I could have saved myself writing this (and the first) email!
I don't know about ages, the patch has been acked, and looks likely to make the 3.4 merge window. I does seem rather low risk, but it is more a feature than a bug fix at this point, and might have some difficulty making it into the stable series. The functionality it provides is nice to have, but not something that is critical for us to pick up in the Fedora tree before it makes upstream. This isn't to say that we don't like the patch, or don't agree with it. Simply that we certainly prefer that features go through upstream first.
Justin
I see
2012/3/3 Joshua C. joshuacov@googlemail.com:
2012/3/3 Justin M. Forbes jforbes@redhat.com:
On Sat, 2012-03-03 at 19:31 +0100, Joshua C. wrote:
2012/3/3 Josh Boyer jwboyer@gmail.com:
On Sat, Mar 3, 2012 at 9:41 AM, Joshua C. joshuacov@googlemail.com wrote:
Can some, please, apply the following patch to the fedora kernel? http://marc.info/?l=linux-kernel&m=133072333922354&w=2 . It sets the NumLock state on the keyboard according to the data in the bios.
It'll got into F17/rawhide when it makes it into Linus' tree. If you get it into the stable release, it will wind up in F15/F16 relatively soon.
That should be sufficient, shouldn't it? At the least I'd like to wait for it to wind up in Linus' tree.
josh
This could take ages, couldn't it? You know that I have absolutely no influence what goes and when into his tree. In that case I could have saved myself writing this (and the first) email!
I don't know about ages, the patch has been acked, and looks likely to make the 3.4 merge window. I does seem rather low risk, but it is more a feature than a bug fix at this point, and might have some difficulty making it into the stable series. The functionality it provides is nice to have, but not something that is critical for us to pick up in the Fedora tree before it makes upstream. This isn't to say that we don't like the patch, or don't agree with it. Simply that we certainly prefer that features go through upstream first.
Justin
I see
The commit b2d0b7a061bfddd27155c7dcd53f365d9dc0c7c3 has been merged into master. Can you pull this now in f16?
kernel@lists.fedoraproject.org
-
Josh Boyer -
Joshua C. -
Justin Forbes