From: Johannes Berg <johannes@sipsolutions.net>
To: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: updated iwlwifi 5000 uCode available
Date: Wed, 20 Apr 2011 21:04:50 +0200 [thread overview]
Message-ID: <1303326290.3619.10.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1303323806.14995.163.camel@wwguy-huron>
On Wed, 2011-04-20 at 11:23 -0700, Guy, Wey-Yi wrote:
> > The version I get from:
> >
> > wget http://www.intellinuxwireless.org/iwlwifi/downloads/iwlwifi-5000-ucode-8.83.5.1.tgz
> >
> > matches the sha1sum values listed above for the "wrongly packaged" version.
Ahrg, and it is! I sent Wey-Yi the wrong file :-(
Will fix.
johannes
next prev parent reply other threads:[~2011-04-20 19:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-20 16:24 updated iwlwifi 5000 uCode available Guy, Wey-Yi
2011-04-20 18:22 ` John W. Linville
2011-04-20 18:23 ` Guy, Wey-Yi
2011-04-20 19:04 ` Johannes Berg [this message]
2011-04-20 20:11 ` John W. Linville
2011-04-20 20:17 ` wwguy
2011-04-21 0:16 ` John W. Linville
2011-04-21 14:09 ` wwguy
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=1303326290.3619.10.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--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).