From: Kalle Valo <kvalo@codeaurora.org>
To: "Grumbach\, Emmanuel" <emmanuel.grumbach@intel.com>
Cc: "linux-wireless\@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: pull request: iwlwifi-2016-02-16
Date: Tue, 16 Feb 2016 18:02:33 +0200 [thread overview]
Message-ID: <874md8tzhi.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <0BA3FCBA62E2DC44AF3030971E174FB32EA13D1A@hasmsx107.ger.corp.intel.com> (Emmanuel Grumbach's message of "Mon, 15 Feb 2016 11:57:38 +0000")
"Grumbach, Emmanuel" <emmanuel.grumbach@intel.com> writes:
> This is a pull request for 4.5. Apart from my RF-Kill fix, the patches are
> really small. My RF-Kill patch needed to move code around to avoid adding
> a forward declaration and on the way there were a few very trivial code style
> fixes, that were needed to make checkpatch happy.
>
> Let me know if you have issues, thanks!
>
>
> The following changes since commit 69c7fda40921c125eeeef6a827f6270ac6aa1baa:
>
> iwlwifi: mvm: rs: fix TPC statistics handling (2016-01-26 16:03:35 +0200)
>
> are available in the git repository at:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-fixes.git tags/iwlwifi-for-kalle-2016-02-15
Pulled, thanks.
--
Kalle Valo
next prev parent reply other threads:[~2016-02-16 16:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 11:57 pull request: iwlwifi-2016-02-16 Grumbach, Emmanuel
2016-02-15 11:59 ` [PATCH 1/5] iwlwifi: fix name of ucode loaded for 8265 series Emmanuel Grumbach
2016-02-15 11:59 ` [PATCH 2/5] iwlwifi: dvm: remove a wrong dependency on m Emmanuel Grumbach
2016-02-15 11:59 ` [PATCH 3/5] iwlwifi: mvm: don't allow sched scans without matches to be started Emmanuel Grumbach
2016-02-15 11:59 ` [PATCH 4/5] iwlwifi: pcie: fix RF-Kill vs. firmware load race Emmanuel Grumbach
2016-02-15 11:59 ` [PATCH 5/5] iwlwifi: pcie: fix erroneous return value Emmanuel Grumbach
2016-02-16 16:02 ` Kalle Valo [this message]
2016-03-18 19:52 ` pull request: iwlwifi-2016-02-16 Arend Van Spriel
2016-03-18 20:03 ` Coelho, Luciano
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=874md8tzhi.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=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).