From: David Woodhouse <dwmw2@infradead.org>
To: Ike Panhc <ike.pan@canonical.com>
Cc: Corentin Chary <corentin.chary@gmail.com>,
platform-driver-x86@vger.kernel.org, linux-acpi@vger.kernel.org,
Matthew Garrett <mjg@redhat.com>, Len Brown <len.brown@intel.com>,
Randy Dunlap <randy.dunlap@oracle.com>,
Andrew Morton <akpm@linux-foundation.org>,
Alan Cox <alan@linux.intel.com>, Thomas Renninger <trenn@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ideapad-laptop: add new driver
Date: Fri, 13 Aug 2010 10:22:00 +0100 [thread overview]
Message-ID: <1281691320.23680.480.camel@localhost> (raw)
In-Reply-To: <4C64EC01.9040103@canonical.com>
On Fri, 2010-08-13 at 14:53 +0800, Ike Panhc wrote:
> Could you point me where is the rfkill driver? Sorry I do not find it.
git://git.infradead.org/users/dwmw2/ideapad-2.6.git
http://git.infradead.org/users/dwmw2/ideapad-2.6.git
After fixing Corentin's review feedback and conferring with Matthew, I
asked Linus to pull it last night -- without the rfkill support, people
were having to reinstall Windows and use it to unblock the rfkill and
get wireless working.
http://bugs.meego.com/show_bug.cgi?id=4086
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/577114
http://forums.lenovo.com/t5/Linux-Discussion/Solution-to-rfkill-wireless-problems-w-IdeaPad-S12/td-p/224122
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
next prev parent reply other threads:[~2010-08-13 9:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-13 4:08 [PATCH] ideapad-laptop: add new driver Ike Panhc
2010-08-13 6:37 ` Corentin Chary
2010-08-13 6:37 ` Corentin Chary
2010-08-13 6:53 ` Ike Panhc
2010-08-13 7:01 ` Corentin Chary
2010-08-13 7:15 ` Ike Panhc
2010-08-13 9:22 ` David Woodhouse [this message]
2010-08-13 9:14 ` David Woodhouse
2010-08-13 9:27 ` Ike Panhc
2010-08-13 9:34 ` David Woodhouse
2010-08-14 2:56 ` Ike Panhc
2010-08-14 9:49 ` David Woodhouse
2010-08-15 2:33 ` Len Brown
2010-08-15 8:14 ` Florian Echtler
2010-08-15 8:20 ` Florian Echtler
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=1281691320.23680.480.camel@localhost \
--to=dwmw2@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=alan@linux.intel.com \
--cc=corentin.chary@gmail.com \
--cc=ike.pan@canonical.com \
--cc=len.brown@intel.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mjg@redhat.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=trenn@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.