From: Andi Kleen <andi@firstfloor.org>
To: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>
Cc: Andi Kleen <andi@firstfloor.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Andi Kleen <ak@linux.intel.com>,
"Berg, Johannes" <johannes.berg@intel.com>
Subject: Re: [PATCH] iwl3945: Fix oops at module load
Date: Tue, 9 Nov 2010 02:46:00 +0100 [thread overview]
Message-ID: <20101109014559.GA21551@basil.fritz.box> (raw)
In-Reply-To: <1289254122.12056.86.camel@wwguy-huron>
> I believe the fix already in
> http://git.kernel.org/?p=linux/kernel/git/iwlwifi/iwlwifi-2.6.git;a=summary
> commit#6e0922e0781884ff4eb3638f10a91b63b6120207
Thanks. Can that please be sent to Linus ASAP? It doesn't really
help my laptop if it's in some obscure git tree.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
next prev parent reply other threads:[~2010-11-09 1:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-08 21:54 [PATCH] iwl3945: Fix oops at module load Andi Kleen
2010-11-08 22:01 ` Berg, Johannes
2010-11-08 22:08 ` Guy, Wey-Yi
2010-11-09 1:46 ` Andi Kleen [this message]
2010-11-09 3:04 ` Guy, Wey-Yi
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=20101109014559.GA21551@basil.fritz.box \
--to=andi@firstfloor.org \
--cc=ak@linux.intel.com \
--cc=johannes.berg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=wey-yi.w.guy@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;
as well as URLs for NNTP newsgroup(s).