From: "Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>
To: "kvalo@codeaurora.org" <kvalo@codeaurora.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"ebiederm@xmission.com" <ebiederm@xmission.com>
Subject: Re: [PATCH net-next 0/2] build fixes for iwlwifi
Date: Sat, 7 Mar 2015 17:48:38 +0000 [thread overview]
Message-ID: <1425750517.20750.2.camel@egrumbacBox> (raw)
In-Reply-To: <87r3t11d4r.fsf@kamboji.qca.qualcomm.com>
T24gU2F0LCAyMDE1LTAzLTA3IGF0IDA5OjI3ICswMjAwLCBLYWxsZSBWYWxvIHdyb3RlOg0KDQoN
CmViaWVkZXJtQHhtaXNzaW9uLmNvbTxtYWlsdG86ZWJpZWRlcm1AeG1pc3Npb24uY29tPiAoRXJp
YyBXLiBCaWVkZXJtYW4pIHdyaXRlczoNCg0KPiBkcml2ZXJzL25ldC93aXJlbGVzL2l3bHdpZmkv
bXZtIGZhaWxzIHRvIGJ1aWxkIGZvciBtZSBvbg0KPiBuZXQtbmV4dC4NCj4NCj4gRXJpYyBXLiBC
aWVkZXJtYW4gKDIpOg0KPiAgICAgICBpd2x3aWZpOiBtdm06IEZpeCB0aGUgYnVpbGQgb2YgbXZt
L21hYy1jdHh0LmMgd2l0aCBkZWJ1Z2ZzIGRpc2FibGVkDQo+ICAgICAgIGl3bHdpZmk6IG12bTog
Rml4IHRoZSBidWlsZCBvZiBtdm0vcGh5LWN0eHQuYyB3aXRoIGRlYnVnZnMgZGlzYWJsZWQNCg0K
RW1tYW51ZWwsIGFyZSB5b3Ugb2sgd2l0aCB0aGVzZT8gQ2FuIEkgYXBwbHkgdGhlbT8NCg0KDQoN
CkkganVzdCBzZW50IGEgcHVsbCByZXF1ZXN0IHdpdGggdGhlIHByb3BlciBmaXhlcy4NClNvcnJ5
Lg0K
prev parent reply other threads:[~2015-03-07 17:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 17:08 pull-request: wireless-drivers-next 2015-03-06 Kalle Valo
2015-03-06 20:46 ` David Miller
2015-03-07 7:18 ` Kalle Valo
2015-03-07 2:35 ` [PATCH net-next 0/2] build fixes for iwlwifi Eric W. Biederman
2015-03-07 2:36 ` [PATCH 1/2] iwlwifi: mvm: Fix the build of mvm/mac-ctxt.c with debugfs disabled Eric W. Biederman
2015-03-07 2:37 ` [PATCH net-next 2/2] iwlwifi: mvm: Fix the build of mvm/phy-ctxt.c " Eric W. Biederman
2015-03-07 7:27 ` [PATCH net-next 0/2] build fixes for iwlwifi Kalle Valo
2015-03-07 17:48 ` Grumbach, Emmanuel [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=1425750517.20750.2.camel@egrumbacBox \
--to=emmanuel.grumbach@intel.com \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@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).