From: "Arend van Spriel" <arend@broadcom.com>
To: "Seth Forshee" <seth.forshee@canonical.com>
Cc: linux-wireless@vger.kernel.org,
"Brett Rudley" <brudley@broadcom.com>,
"Roland Vossen" <rvossen@broadcom.com>,
"Franky (Zhenhui) Lin" <frankyl@broadcom.com>,
"Kan Yan" <kanyan@broadcom.com>
Subject: Re: brcmsmac problems in wireless-testing
Date: Wed, 30 May 2012 22:51:35 +0200 [thread overview]
Message-ID: <4FC68857.3020902@broadcom.com> (raw)
In-Reply-To: <20120530204729.GF30697@thinkpad-t410>
On 05/30/2012 10:47 PM, Seth Forshee wrote:
> Bah, I managed to screw up the format of the headers somehow. Fixed the
> subject.
>
I noticed ;-)
next prev parent reply other threads:[~2012-05-30 20:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-30 20:25 Seth Forshee
2012-05-30 20:47 ` brcmsmac problems in wireless-testing Seth Forshee
2012-05-30 20:51 ` Arend van Spriel [this message]
2012-05-30 20:49 ` brcmsmac connection stalls (was Re: ) Arend van Spriel
2012-05-30 21:05 ` Seth Forshee
2012-05-30 21:23 ` Arend van Spriel
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=4FC68857.3020902@broadcom.com \
--to=arend@broadcom.com \
--cc=brudley@broadcom.com \
--cc=frankyl@broadcom.com \
--cc=kanyan@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=rvossen@broadcom.com \
--cc=seth.forshee@canonical.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).