From: "Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: [ANN] -14.ucode is available
Date: Sun, 31 May 2015 18:02:46 +0000 [thread overview]
Message-ID: <1433095362.28501.9.camel@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 915 bytes --]
The new -14.ucode is already available in [1].
Since you'll need iwlwifi-next tree [2] to use it, I still don't send
the pull request to mainline linux-firmware.git. -14.ucode just finished
its validation cycle, but experience shows that lots of fixes still get
merged after the validation cycle based on feedback from the field. So
you are more than welcome to give it a try and let us know how it went.
For those who don't want to use iwlwifi-next, you can use iwlwifi's
backport tree that has been made available here [3]. You can take either
the master branch, or the Core11 branch which is the stabilization
branch that matches -14.ucode.
Thank you
[1]
https://git.kernel.org/cgit/linux/kernel/git/iwlwifi/linux-firmware.git/
[2]
https://git.kernel.org/cgit/linux/kernel/git/iwlwifi/iwlwifi-next.git/
[3]
https://git.kernel.org/cgit/linux/kernel/git/iwlwifi/backport-iwlwifi.git/
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
reply other threads:[~2015-05-31 18:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1433095362.28501.9.camel@intel.com \
--to=emmanuel.grumbach@intel.com \
--cc=linux-wireless@vger.kernel.org \
/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).