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-next 2015-08-23
Date: Tue, 25 Aug 2015 15:03:09 +0300 [thread overview]
Message-ID: <87twrn60ea.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <0BA3FCBA62E2DC44AF3030971E174FB32E827CB7@hasmsx107.ger.corp.intel.com> (Emmanuel Grumbach's message of "Sun, 23 Aug 2015 10:05:13 +0000")
"Grumbach, Emmanuel" <emmanuel.grumbach@intel.com> writes:
> one very last pull request for 4.3 before the merge windows opens. I
> hope it will make it. Let me know if you have issues with it.
>
> Thanks!
>
> The following changes since commit ecc7c518b3017821a6b26fb5fdaa548afa8ee236:
>
> iwlwifi: mvm: fix a race in D0i3 vs. Tx path (2015-08-18 10:25:26 +0300)
>
> are available in the git repository at:
>
>
> https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-next.git
> tags/iwlwifi-next-for-kalle-2015-08-23
Thanks, pulled.
--
Kalle Valo
prev parent reply other threads:[~2015-08-25 12:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-23 10:05 pull request: iwlwifi-next 2015-08-23 Grumbach, Emmanuel
2015-08-24 19:52 ` Kalle Valo
2015-08-24 19:59 ` Grumbach, Emmanuel
2015-08-24 20:00 ` [PATCH 1/6] iwlwifi: mvm: catch underflow error earlier Emmanuel Grumbach
2015-08-24 20:00 ` [PATCH 2/6] iwlwifi: mvm: update wakeup reason enum Emmanuel Grumbach
2015-08-24 20:00 ` [PATCH 3/6] iwlwifi: correctly size command string arrays Emmanuel Grumbach
2015-08-24 20:00 ` [PATCH 4/6] iwlwifi: mvm: split debug message to avoid exceeding 110 characters Emmanuel Grumbach
2015-08-24 20:00 ` [PATCH 5/6] iwlwifi: mvm: support new TX power command Emmanuel Grumbach
2015-08-24 20:00 ` [PATCH 6/6] iwlwifi: mvm: bump firmware API to 17 Emmanuel Grumbach
2015-08-25 12:03 ` Kalle Valo [this message]
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=87twrn60ea.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.