Re: [2.6.35-rc5] hp-wmi patch missed .35 merge window, requestingaddition to next rc

[Stefan Bader]

On 09/23/2010 10:37 AM, Thomas Renninger wrote:
> Hi,
> 
> I didn't know about this one.
> Can people please add me to CC list on hp-wmi specific bug
> reports (for existing and new ones), thanks.
> 
> On Wednesday 22 September 2010 04:08:16 Andrew Morton wrote:
>> (cc's added)
>> The suggestion is that mainline's
>> 751ae808f6b29803228609f51aa1ae057f5c576e ("x86 platform drivers: hp-wmi
>> Reorder event id processing") be backported into 2.6.35.x to fix the
>> post-2.6.32 regression described in
>> https://bugzilla.kernel.org/show_bug.cgi?id=15344
> Hmm, the bug is still in "open" state, there is no statement that anything
> is found yet fixing the issue.
> 
> Could you please update the bug report if you verified and are sure
> the patch helps.
> 
> The patch is a cleanup, has some functional change, but should
> do things correctly now. As long as no special case was handled
> by always calling:
> hp_wmi_get_entry_by_scancode(eventcode);
> even it was not a hotkey event, this is a straight forward fix and
> if no one else complains, you have my vote for adding this to
> stable kernel(s).
> 
> about:
>> if this patch doesn't make it into .35 my laptop
>> will be doing this for its (10.10) entire lifetime.
> Isn't Ubuntu following stable 2.6.35.X kernels and you would get this with
> an update if it's pushed into stable kernels?
> I expect they do follow and there is no need to hurry?
> 
Yes, we do follow 2.6.35.y updates at least for a few months after release. So
there should be no particular need to hurry. At least if it gets to Greg before
he stops caring about .35.

-Stefan

>      Thomas
> --
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/