From: Luca Coelho <luca@coelho.fi>
To: kvalo <kvalo@codeaurora.org>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
"Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>
Subject: pull-request: iwlwifi-next 2016-07-11
Date: Mon, 11 Jul 2016 14:25:22 +0300 [thread overview]
Message-ID: <1468236322.25088.114.camel@coelho.fi> (raw)
[-- Attachment #1: Type: text/plain, Size: 1238 bytes --]
Hi Kalle,
I have one more patch intended for 4.8. I had forgotten to bump the FW
API version that our driver is now able to load. I hope there is still
time to get it included for 4.8.
Let me know if everything's fine (or not). :)
Luca.
The following changes since commit 6f482e37b75d4e56cdb9b56ae7057f3ce67097bc:
iwlwifi: move iwl_drv to be shared across transports (2016-07-06 10:37:44 +0300)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-next.git tags/iwlwifi-next-for-kalle-2016-07-11
for you to fetch changes up to ad38844b8e00c8d33eb1d1ffb49b945e6a985e13:
iwlwifi: mvm: bump MAX firmware API for mvm devices (2016-07-11 14:15:38 +0300)
----------------------------------------------------------------
* bump firmware version to load newer firmwares
----------------------------------------------------------------
Luciano Coelho (1):
iwlwifi: mvm: bump MAX firmware API for mvm devices
drivers/net/wireless/intel/iwlwifi/iwl-7000.c | 4 ++--
drivers/net/wireless/intel/iwlwifi/iwl-8000.c | 4 ++--
drivers/net/wireless/intel/iwlwifi/iwl-9000.c | 2 +-
3 files changed, 5 insertions(+), 5 deletions(-)
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next reply other threads:[~2016-07-11 11:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 11:25 Luca Coelho [this message]
2016-07-18 19:47 ` pull-request: iwlwifi-next 2016-07-11 Kalle Valo
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=1468236322.25088.114.camel@coelho.fi \
--to=luca@coelho.fi \
--cc=emmanuel.grumbach@intel.com \
--cc=kvalo@codeaurora.org \
--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