From: Corentin Chary <corentin.chary@gmail.com>
To: Len Brown <lenb@kernel.org>
Cc: linux-acpi@vger.kernel.org, Matthew Garrett <mjg59@srcf.ucam.org>,
Matthew Garrett <mjg@redhat.com>
Subject: Re: [PATCH 5/7] eeepc-laptop: Register as a pci-hotplug device
Date: Fri, 15 May 2009 11:31:20 +0200 [thread overview]
Message-ID: <71cd59b00905150231m5635876do8cbf44fec7d09110@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0905141129110.19537@localhost.localdomain>
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
prev parent reply other threads:[~2009-05-15 9:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1240817023-5985-1-git-send-email-corentincj@iksaif.net>
[not found] ` <1240817023-5985-2-git-send-email-corentincj@iksaif.net>
2009-05-14 15:15 ` [PATCH 1/7] eeepc-laptop: fix wlan rfkill state change during init Len Brown
[not found] ` <1240817023-5985-3-git-send-email-corentincj@iksaif.net>
2009-05-14 15:19 ` [PATCH 2/7] eeepc-laptop: report brightness control events via the input layer Len Brown
[not found] ` <1240817023-5985-4-git-send-email-corentincj@iksaif.net>
2009-05-14 15:21 ` [PATCH 3/7] eeepc-laptop: Work around rfkill firmware bug Len Brown
[not found] ` <1240817023-5985-5-git-send-email-corentincj@iksaif.net>
2009-05-14 15:23 ` [PATCH 4/7] eeepc-laptop: support for super hybrid engine (SHE) Len Brown
[not found] ` <1240817023-5985-6-git-send-email-corentincj@iksaif.net>
[not found] ` <1240817023-5985-7-git-send-email-corentincj@iksaif.net>
2009-05-14 15:27 ` [PATCH 6/7] asus-laptop: fix input keycode Len Brown
[not found] ` <1240817023-5985-8-git-send-email-corentincj@iksaif.net>
2009-05-14 15:28 ` [PATCH 7/7] eeepc-laptop: unregister_rfkill_notifier on failure Len Brown
2009-05-14 15:33 ` [PATCH 5/7] eeepc-laptop: Register as a pci-hotplug device Len Brown
2009-05-15 9:31 ` Corentin Chary [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=71cd59b00905150231m5635876do8cbf44fec7d09110@mail.gmail.com \
--to=corentin.chary@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=mjg@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox