linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Gavin McCullagh <gmccullagh@gmail.com>
Cc: Larry Finger <larry.finger@lwfinger.net>,
	wireless <linux-wireless@vger.kernel.org>
Subject: Re: [Fwd: [AirForce One 54g] working]
Date: Mon, 17 Sep 2007 12:07:18 +0200	[thread overview]
Message-ID: <1190023638.4563.0.camel@localhost> (raw)
In-Reply-To: <20070917100515.GD1455@gmail.com>

On Mo, 2007-09-17 at 11:05 +0100, Gavin McCullagh wrote:

> I'll have to have a look when I get home, but I didn't apply any patches, I
> simply downloaded the wireless-dev tree from git.kernel.org.  

Ok, thanks. I expect that somehow I introduced a bug with mac address
filtering and crypto.

johannes


      reply	other threads:[~2007-09-17 10:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-16 22:31 [Fwd: [AirForce One 54g] working] Larry Finger
2007-09-17  9:54 ` Johannes Berg
2007-09-17 10:05   ` Gavin McCullagh
2007-09-17 10:07     ` Johannes Berg [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=1190023638.4563.0.camel@localhost \
    --to=johannes@sipsolutions.net \
    --cc=gmccullagh@gmail.com \
    --cc=larry.finger@lwfinger.net \
    --cc=linux-wireless@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).