Netdev List
 help / color / mirror / Atom feed
From: Michael Wu <flamingice@sourmilk.net>
To: Brandon Craig Rhodes <brandon@rhodesmill.org>
Cc: netdev@vger.kernel.org
Subject: Re: TKIP encryption should allocate enough tailroom
Date: Tue, 16 Jan 2007 22:50:36 -0500	[thread overview]
Message-ID: <200701162250.42731.flamingice@sourmilk.net> (raw)
In-Reply-To: <87bqky759v.fsf@ten22.rhodesmill.org>

[-- Attachment #1: Type: text/plain, Size: 707 bytes --]

On Tuesday 16 January 2007 21:31, Brandon Craig Rhodes wrote:
> The attached patch, if applied to kernel 2.6.18, solves both problems.
> I am not very familiar with the conventions of kernel networking code,
> so there may be better ways of fixing this; but the patch should
> illustrate the general idea, and perhaps provides others in my unhappy
> situation with stable WPA connections until someone can provide a more
> authorized patch.
>
Please read <http://linux.yyz.us/patch-format.html>. You should CC 
linville@tuxdriver.com as he is the maintainer of 802.11 things and can push 
your patch upstream. Also, you should have a '\n' at the end of the new 
printks.

Thanks,
-Michael Wu

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2007-01-17  3:51 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-17  2:31 TKIP encryption should allocate enough tailroom Brandon Craig Rhodes
2007-01-17  3:39 ` Mitchell Blank Jr
2007-01-17  3:34   ` Brandon Craig Rhodes
2007-01-17  6:34     ` Herbert Xu
2007-01-17  7:18       ` Herbert Xu
2007-01-17  3:50 ` Michael Wu [this message]
2007-01-17 16:46 ` Brandon Craig Rhodes
2007-01-17 17:23   ` Larry Finger
2007-01-17 17:38     ` Brandon Craig Rhodes
2007-01-18 13:16   ` Pekka Pietikainen
2007-01-18 13:55     ` Brandon Craig Rhodes
2007-01-19 12:23       ` Pekka Pietikainen

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=200701162250.42731.flamingice@sourmilk.net \
    --to=flamingice@sourmilk.net \
    --cc=brandon@rhodesmill.org \
    --cc=netdev@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