From: Jouni Malinen <jouni.malinen@atheros.com>
To: Gabor Juhos <juhosg@openwrt.org>
Cc: "John W. Linville" <linville@tuxdriver.com>,
"ath9k-devel@lists.ath9k.org" <ath9k-devel@lists.ath9k.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [ath9k-devel] [PATCH 0/2] ath9k: fix compile errors
Date: Fri, 6 Mar 2009 12:29:33 +0200 [thread overview]
Message-ID: <1236335373.16873.1.camel@jm-desktop> (raw)
In-Reply-To: <1236329859-17911-1-git-send-email-juhosg@openwrt.org>
On Fri, 2009-03-06 at 00:57 -0800, Gabor Juhos wrote:
> This set will correct two compilation errors in master-2009-03-04
> of wireless-testing.
Thanks for fixing these and the no-RFKILL build issue! Looks like I
should try to get a build setup for testing ahb.c build myself..
- Jouni
next prev parent reply other threads:[~2009-03-06 10:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-06 8:57 [PATCH 0/2] ath9k: fix compile errors Gabor Juhos
2009-03-06 8:57 ` [PATCH 1/2] ath9k: fix compile error in ahb.c Gabor Juhos
2009-03-06 8:57 ` [PATCH 2/2] ath9k: fix compile error in debug.c Gabor Juhos
2009-03-06 10:29 ` Jouni Malinen [this message]
2009-03-06 17:54 ` [ath9k-devel] [PATCH 0/2] ath9k: fix compile errors Gabor Juhos
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=1236335373.16873.1.camel@jm-desktop \
--to=jouni.malinen@atheros.com \
--cc=ath9k-devel@lists.ath9k.org \
--cc=juhosg@openwrt.org \
--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).