From: Kalle Valo <kvalo@qca.qualcomm.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Pull request: ath6kl 20111001
Date: Mon, 3 Oct 2011 14:02:29 +0300 [thread overview]
Message-ID: <4E899645.5060708@qca.qualcomm.com> (raw)
In-Reply-To: <4E86E7A9.9070909@qca.qualcomm.com>
Hi again John,
On 10/01/2011 01:12 PM, Kalle Valo wrote:
> here's a pretty big pull request from ath6kl.git. I was supposed to send
> this already earlier, but I wanted to have a fix for an important TCP
> corruption bug first. Even there are quite a few changes, I still ask
> you to consider this for the 3.2 release. It has received extensive
> testing and we have fixed a bunch of bugs from the current version in
> wireless-next.
Actually I had to do an update to the pull request and add the commit
below to make it properly compile on ARM.
commit 62c83ac4d6bcfa6a116c8f1c8ace05cb3933a4f1
Author: Kalle Valo <kvalo@qca.qualcomm.com>
Date: Mon Oct 3 13:44:40 2011 +0300
ath6kl: include vmalloc.h in debug.c
I just pushed that change to github to the same for-linville branch.
Also I noticed that while compiling ath6kl for beagleboard I need this:
diff --git a/include/linux/of.h b/include/linux/of.h
index 9180dc5..219c29d 100644
--- a/include/linux/of.h
+++ b/include/linux/of.h
@@ -17,6 +17,7 @@
*/
#include <linux/types.h>
#include <linux/bitops.h>
+#include <linux/errno.h>
#include <linux/kref.h>
#include <linux/mod_devicetable.h>
#include <linux/spinlock.h>
But I'll send that to the device tree maintainers.
Kalle
prev parent reply other threads:[~2011-10-03 11:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-01 10:12 Pull request: ath6kl 20111001 Kalle Valo
2011-10-03 11:02 ` 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=4E899645.5060708@qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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).