From: "John W. Linville" <linville@tuxdriver.com>
To: Valdis.Kletnieks@vt.edu
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
wsl3@lrsehosting.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
alan@redhat.com, Adrian Bunk <bunk@stusta.de>
Subject: Re: Unidentified Intel wifi network card
Date: Thu, 1 Feb 2007 13:06:24 -0500 [thread overview]
Message-ID: <20070201180624.GC5408@tuxdriver.com> (raw)
In-Reply-To: <200702011600.l11G08Zs015498@turing-police.cc.vt.edu>
On Thu, Feb 01, 2007 at 11:00:08AM -0500, Valdis.Kletnieks@vt.edu wrote:
> On Thu, 01 Feb 2007 08:59:47 +1100, Herbert Xu said:
> > If this driver is still using the old digest interface, it needs to be
> > converted to use crypto_hash_*.
>
> OK, here's the more complete scoop - the *out of tree* ieee80211 tree
> hasn't been converted, but the *in tree* version has.
>
> Why did I have the out of tree version installed? Because the in-tree
> version claimed to be 1.1.3, and the out-of-tree 1.2.16. Apparently,
> the update to the version string for the in-kernel version got blocked
> someplace - the in-tree is apparently actually very close to 1.2.16.
I don't recall seeing such a patch, fwiw. The only patch I recall
refusing from that team is the one that marks ipw2100 as broken
on big-endian.
If I missed those patches, please re-send them.
Thanks,
John
--
John W. Linville
linville@tuxdriver.com
next prev parent reply other threads:[~2007-02-01 18:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-31 17:30 Unidentified Intel wifi network card Scott Lockwood
2007-01-31 17:56 ` Alan Cox
2007-01-31 18:06 ` David Hollis
2007-01-31 18:40 ` Auke Kok
2007-01-31 20:54 ` Valdis.Kletnieks
2007-01-31 21:59 ` Herbert Xu
2007-02-01 16:00 ` Valdis.Kletnieks
2007-02-01 18:06 ` John W. Linville [this message]
2007-02-01 4:02 ` Ross Vandegrift
2007-01-31 21:12 ` Kristen Accardi
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=20070201180624.GC5408@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=alan@redhat.com \
--cc=bunk@stusta.de \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=wsl3@lrsehosting.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.