Re: [PATCH 1/7] eeepc-laptop: fix wlan rfkill state change during init

Re: [PATCH 1/7] eeepc-laptop: fix wlan rfkill state change during init

[Len Brown]

applied

thanks,
Len Brown, Intel Open Source Technology Center

Re: [PATCH 2/7] eeepc-laptop: report brightness control events via the input layer

[Len Brown]

applied

thanks,
Len Brown, Intel Open Source Technology Center

Re: [PATCH 3/7] eeepc-laptop: Work around rfkill firmware bug

[Len Brown]

applied

thanks,
Len Brown, Intel Open Source Technology Center

Re: [PATCH 4/7] eeepc-laptop: support for super hybrid engine (SHE)

[Len Brown]

applied

thanks,
Len Brown, Intel Open Source Technology Center

Re: [PATCH 6/7] asus-laptop: fix input keycode

[Len Brown]

applied

thanks,
Len Brown, Intel Open Source Technology Center

Re: [PATCH 7/7] eeepc-laptop: unregister_rfkill_notifier on failure

[Len Brown]

applied

thanks,
Len Brown, Intel Open Source Technology Center

Re: [PATCH 5/7] eeepc-laptop: Register as a pci-hotplug device

[Len Brown]

applied to acpi-test

If it is common, then we should push for .30.
If it is not common, then since it is larger
than most -rc5 bugfixes, I'd prefer to wait for .31,
even though it is driver specific.

please advise.

thanks,
Len Brown, Intel Open Source Technology Center

Re: [PATCH 5/7] eeepc-laptop: Register as a pci-hotplug device

[Corentin Chary]

On Thu, May 14, 2009 at 5:33 PM, Len Brown <lenb@kernel.org> wrote:
> applied to acpi-test
>
> If it is common, then we should push for .30.
> If it is not common, then since it is larger
> than most -rc5 bugfixes, I'd prefer to wait for .31,
> even though it is driver specific.
>
> please advise.
>
> thanks,
> Len Brown, Intel Open Source Technology Center
>
>

The bug is only triggered with specific configuration and kernel
parameters (pciehp force=1).
The patch is too large, I think we should wait for .31.

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