From: Bob Copeland <me@bobcopeland.com>
To: Pavel Roskin <proski@gnu.org>
Cc: linville@tuxdriver.com, ath5k-devel@lists.ath5k.org,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH 2.6.31] ath5k: temporarily disable crypto for AP mode
Date: Tue, 25 Aug 2009 16:58:39 -0400 [thread overview]
Message-ID: <b6c5339f0908251358r7693deefid2a0f738eb508e1f@mail.gmail.com> (raw)
In-Reply-To: <1251232252.9398.2.camel@mj>
On Tue, Aug 25, 2009 at 4:30 PM, Pavel Roskin<proski@gnu.org> wrote:
>>
>> Pavel, this ok with you for now?
>
> Sorry for delay. I don't have time to test it, but I have no specific
> objections.
Thanks, for the update. It already went to Linus I believe.
I did spend enough time looking at the root problem to decide that
fixing it won't be too hard, but I also saw some questionable logic
in the original code that wants a cleanup, I can post patches soon.
--
Bob Copeland %% www.bobcopeland.com
prev parent reply other threads:[~2009-08-25 20:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-14 1:57 [PATCH 2.6.31] ath5k: temporarily disable crypto for AP mode Bob Copeland
2009-08-25 20:30 ` Pavel Roskin
2009-08-25 20:58 ` Bob Copeland [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=b6c5339f0908251358r7693deefid2a0f738eb508e1f@mail.gmail.com \
--to=me@bobcopeland.com \
--cc=ath5k-devel@lists.ath5k.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=proski@gnu.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