From: Kalle Valo <kvalo@codeaurora.org>
To: "Grumbach\, Emmanuel" <emmanuel.grumbach@intel.com>
Cc: "torvalds\@linux-foundation.org" <torvalds@linux-foundation.org>,
"linux-wireless\@vger.kernel.org"
<linux-wireless@vger.kernel.org>
Subject: Re: pull request: iwlwifi 2015-01-15
Date: Mon, 19 Jan 2015 09:53:01 +0200 [thread overview]
Message-ID: <871tmr6wbm.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1421612183.26502.1.camel@egrumbacBox> (Emmanuel Grumbach's message of "Sun, 18 Jan 2015 20:16:23 +0000")
"Grumbach, Emmanuel" <emmanuel.grumbach@intel.com> writes:
> One single patch in there, but since it hit Linus's system, and we are
> in -rc5 already, I didn't want to wait until more stuff accumulates.
> This is a patch for the bug that Linus reported. Let me know if you
> have issues!
Thanks, pulled.
--
Kalle Valo
prev parent reply other threads:[~2015-01-19 7:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-18 20:16 pull request: iwlwifi 2015-01-15 Grumbach, Emmanuel
2015-01-18 20:18 ` [PATCH] iwlwifi: mvm: abort scheduled scan upon RFKILL Emmanuel Grumbach
2015-01-18 22:14 ` Arend van Spriel
2015-01-19 5:57 ` Grumbach, Emmanuel
2015-01-19 7:53 ` 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=871tmr6wbm.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@codeaurora.org \
--cc=emmanuel.grumbach@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=torvalds@linux-foundation.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).