From: Nico -telmich- Schottelius <nico-linux-ipw3945-devel@schottelius.org>
To: "Luo, Ximin" <ximin.luo@intel.com>
Cc: "ipw3945-devel@lists.sourceforge.net"
<ipw3945-devel@lists.sourceforge.net>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>
Subject: Re: [ipw3945-devel] next-20081125: call trace for iwlagn (rfkill switch on)
Date: Fri, 28 Nov 2008 08:53:08 +0100 [thread overview]
Message-ID: <20081128075308.GE5413@denkbrett.schottelius.org> (raw)
In-Reply-To: <AFAB8585072C7E48BC5C6F9C87F9B7970214D75A@pdsmsx502.ccr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 570 bytes --]
Luo, Ximin [Fri, Nov 28, 2008 at 03:03:23PM +0800]:
> Maybe you can the download the latest driver which had fixed this issue.
> You can get the information from http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1800
You are not (yet?) preparing a git repo for inclusion into linux-next, do you?
I just found http://www.intellinuxwireless.org/repos/mac80211.git and
http://www.intellinuxwireless.org/repos/iwlwifi.git
Do I (still) need both repos? Is running "make patch_kernel" for mac802.11
still up-to-date for patching linux-next based?
Sincerly,
Nico
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-11-28 7:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-28 6:38 next-20081125: call trace for iwlagn (rfkill switch on) Nico -telmich- Schottelius
2008-11-28 7:03 ` [ipw3945-devel] " Luo, Ximin
2008-11-28 7:53 ` Nico -telmich- Schottelius [this message]
2008-11-28 8:06 ` Zheng, Jeff
2008-12-04 11:23 ` Nico -telmich- Schottelius
2008-12-05 0:48 ` Luo, Ximin
2008-12-05 6:17 ` reinette chatre
2008-12-05 6:30 ` Luo, Ximin
2008-12-01 18:39 ` reinette chatre
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=20081128075308.GE5413@denkbrett.schottelius.org \
--to=nico-linux-ipw3945-devel@schottelius.org \
--cc=ipw3945-devel@lists.sourceforge.net \
--cc=linux-next@vger.kernel.org \
--cc=ximin.luo@intel.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