From: "John W. Linville" <linville@tuxdriver.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: orinoco: fix broken make allyesconfig due to multiple defs of michael_mic
Date: Fri, 13 Feb 2009 08:17:39 -0500 [thread overview]
Message-ID: <20090213131725.GA3792@tuxdriver.com> (raw)
In-Reply-To: <1234509680.1327.30.camel@johannes.local>
On Fri, Feb 13, 2009 at 08:21:20AM +0100, Johannes Berg wrote:
> I don't think the fix is correct:
>
> - priv->tx_tfm_mic = crypto_alloc_hash("michael_mic", 0, 0);
> + priv->tx_tfm_mic = crypto_alloc_hash("orinoco_mic", 0, 0);
>
> that'll never find anything. Renaming the function name was a good plan,
> but not changing the string here :)
Good point... :-) I'll fix it up some more...
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2009-02-13 13:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-13 7:21 orinoco: fix broken make allyesconfig due to multiple defs of michael_mic Johannes Berg
2009-02-13 13:17 ` John W. Linville [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=20090213131725.GA3792@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=johannes@sipsolutions.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).