eeepc-wmi backport in Natty ?

[Corentin Chary]

On Wed, Mar 23, 2011 at 2:30 PM, Tim Gardner <tim.gardner at canonical.com> wrote:
> On 03/22/2011 01:18 PM, Seth Forshee wrote:
>>
>> Tim,
>>
>> On Mon, Mar 21, 2011 at 04:01:37PM +0000, Corentin Chary wrote:
>>>>
>>>> So, I see a pile of commits to drivers/platform/x86/eeepc-wmi.c in
>>>> linux-next. Are any of these gonna make it into the 2.6.39 merge window?
>>>> If
>>>> so, perhaps you could send a list of the commits you'd like to see added
>>>> to
>>>> Natty once they are merged in Linus' tree.
>>>
>>> Hi,
>>> They should all make it into the 2.6.39 merge window, but  "when"
>>> depends on Matthew Garett's pull request.
>>> Those I want to include to natty are all commits up to
>>> d2cb95cdd419ead71f6d00eed90c924920d5053e "eeepc-wmi: reorder device
>>> ids".
>>> After that, there are a lot of changes that you probably don't want,
>>> the module needs linux/input.h changes, and then there si the big
>>> asus-wmi split...
>>
>> I had cherry-picked these changesets on top of the natty kernel a couple
>> of weeks ago to test on a machine I've been working with. I went ahead
>> and rebased on top of the latest master and pushed it out to:
>>
>>   git://kernel.ubuntu.com/sforshee/ubuntu-natty.git eeepc-wmi-backports
>>
>> If you plan to incorporate those changes then you should just be able to
>> pull them in from there.
>
> Its good to know these commits work. However, I'd still like to wait until
> we can cherry-pick these from Linus' tree. It just reduces the amount of
> maintenance and chances for conflict with stable. We've still got a couple
> of weeks before kernel freeze.

It's now in Linus tree, so we're good.
There is only one patch missing, because I discovered the issue
yesterday. It's available here
http://git.iksaif.net/?p=acpi4asus.git;a=blobdiff;f=drivers/platform/x86/asus-wmi.c;h=832a3fd7c1c8538ef77fd26c628e0ddd2c1644d6;hp=efc776cb0c664e0c8bf19c092c0a48367d4e1043;hb=1b7ad58035d14ead17b0eb0738df9335b7ebacb7;hpb=1c05db880a0073dcad097a664525ae091eef1783
. This patch will probably be in 2.6.39-rc1, but I don't know when it
will happen.

-- 
Corentin Chary
http://xf.iksaif.net