All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Dan Williams <dcbw@redhat.com>
Cc: Tomas Winkler <tomasw@gmail.com>, JMF <tolas_feup@hotmail.com>,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH] iwlwifi: fix oops on wep key insertion
Date: Tue, 27 May 2008 20:41:00 -0400	[thread overview]
Message-ID: <20080528004100.GG7779@tuxdriver.com> (raw)
In-Reply-To: <1211896423.1746.9.camel@localhost.localdomain>

On Tue, May 27, 2008 at 09:53:43AM -0400, Dan Williams wrote:

> I've gotten maybe 1 or 2 requests for > 104/128-bit WEP key support for
> NM in 3 years.  Nice to have, but I'm not sure it's worth the extra code
> and maintenance burden?  Would be good to have somebody tell us what
> hardware (APs and cards) support this though.

I'm inclined to think that it is _not_ worth the trouble for this
particular feature.

John
-- 
John W. Linville
linville@tuxdriver.com

  reply	other threads:[~2008-05-28 12:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-27  5:13 [PATCH] iwlwifi: fix oops on wep key insertion Joonwoo Park
2008-05-27  6:41 ` Tomas Winkler
2008-05-27  7:10   ` Joonwoo Park
2008-05-27 10:58   ` JMF
2008-05-27 12:41     ` Tomas Winkler
2008-05-27 13:53       ` Dan Williams
2008-05-28  0:41         ` John W. Linville [this message]
2008-06-15 16:46           ` Joonwoo Park
2008-06-15 16:53             ` Tomas Winkler
2008-06-16  8:46               ` Johannes Berg
2008-06-16 14:30                 ` Dan Williams
2008-06-27 15:28                 ` John W. Linville
2008-06-27 16:07                   ` Dan Williams
2008-06-27 16:22                     ` Tomas Winkler
2008-06-27 18:10                       ` Dan Williams
2008-06-27 19:12                         ` Johannes Berg
2008-06-27 23:33                           ` Tomas Winkler
2008-05-28 10:14         ` JMF

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=20080528004100.GG7779@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=dcbw@redhat.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=tolas_feup@hotmail.com \
    --cc=tomasw@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.