linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Dave <kilroyd@googlemail.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Subject: Re: linux-next: wireless tree build failure
Date: Fri, 13 Feb 2009 13:24:56 -0500	[thread overview]
Message-ID: <20090213182456.GA3581@tuxdriver.com> (raw)
In-Reply-To: <4995BADE.60700@gmail.com>

On Fri, Feb 13, 2009 at 06:24:30PM +0000, Dave wrote:
> John W. Linville wrote:
> > On Thu, Feb 12, 2009 at 07:35:17PM +1100, Stephen Rothwell wrote:
> >> Today's linux-next build (powerpc allyesconfig) failed like this:
> >>
> >> net/built-in.o: In function `michael_mic':
> >> (.opd+0x3ba78): multiple definition of `michael_mic'
> >> drivers/built-in.o:(.opd+0x552a8): first defined here
> >> net/built-in.o: In function `michael_mic':
> >> net/mac80211/michael.c:58: multiple definition of `.michael_mic'
> >> drivers/built-in.o:drivers/net/wireless/orinoco/mic.c:49: first defined here
> >>
> >> Immediate cause is commit 84875201dd1150dc2c16780b944fe501d588ffba
> >> ("orinoco: Move MIC helpers into new file").
> > 
> > I'll fix this up with a patch like below...
> > 
> > John
> 
> I guess it only worked for me because I'm building modules.
> 
> Anyway, the fix needs to be slightly different:
> 
> > diff --git a/drivers/net/wireless/orinoco/mic.c b/drivers/net/wireless/orinoco/mic.c
> > index c39d9ea..8cdac75 100644
> > --- a/drivers/net/wireless/orinoco/mic.c
> > +++ b/drivers/net/wireless/orinoco/mic.c
> > @@ -16,18 +16,18 @@
> >  /********************************************************************/
> >  int orinoco_mic_init(struct orinoco_private *priv)
> >  {
> > -	priv->tx_tfm_mic = crypto_alloc_hash("michael_mic", 0, 0);
> > +	priv->tx_tfm_mic = crypto_alloc_hash("orinoco_mic", 0, 0);
> 
> That wants to remain as michael_mic, so we get the right crypto alg.
> 
> >  	if (IS_ERR(priv->tx_tfm_mic)) {
> >  		printk(KERN_DEBUG "orinoco_mic_init: could not allocate "
> > -		       "crypto API michael_mic\n");
> > +		       "crypto API orinoco_mic\n");
> 
> Since we're referring to the crypto alg, I suggest this stay the same.
> 
> >  		priv->tx_tfm_mic = NULL;
> >  		return -ENOMEM;
> >  	}
> >  
> > -	priv->rx_tfm_mic = crypto_alloc_hash("michael_mic", 0, 0);
> > +	priv->rx_tfm_mic = crypto_alloc_hash("orinoco_mic", 0, 0);
> 
> Ditto 1.
> 
> >  	if (IS_ERR(priv->rx_tfm_mic)) {
> >  		printk(KERN_DEBUG "orinoco_mic_init: could not allocate "
> > -		       "crypto API michael_mic\n");
> > +		       "crypto API orinoco_mic\n");
> 
> Ditto 2.
> 
> The rest is fine.

Right, Johannes already scolded me.  Sloppy search-n-replace... :-)

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

  reply	other threads:[~2009-02-13 18:30 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-12  8:35 linux-next: wireless tree build failure Stephen Rothwell
2009-02-12 16:16 ` John W. Linville
2009-02-12 22:07   ` Stephen Rothwell
2009-02-13 18:24   ` Dave
2009-02-13 18:24     ` John W. Linville [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-02-27  2:44 Stephen Rothwell
2009-03-23  4:39 Stephen Rothwell
2009-03-23  4:53 ` David Miller
2009-03-23  5:01   ` Yang Hongyang
2009-03-23  4:55 ` David Miller
2009-03-23  5:06   ` Yang Hongyang
2009-03-23  5:48   ` Stephen Rothwell
2009-03-23  7:59     ` David Miller
2009-03-23  8:10       ` Stephen Rothwell
2009-04-22  1:57 Stephen Rothwell
2009-04-22  8:59 ` Johannes Berg
2009-04-22 13:03   ` Stephen Rothwell
2009-04-22 13:06     ` John W. Linville
2009-04-22 13:33       ` Johannes Berg
2009-04-22 13:36         ` Matthew Garrett
2009-06-03  2:52           ` Stephen Rothwell
2009-06-15 12:21             ` Stephen Rothwell
2009-04-22 13:11     ` Johannes Berg
2009-04-28  3:28 ` Stephen Rothwell
2009-04-28 12:50   ` John W. Linville
     [not found] <20090505115455.0b147aeb.sfr@canb.auug.org.au>
2009-05-05  2:55 ` John W. Linville
2009-11-09  8:08 Stephen Rothwell
2009-11-09 13:37 ` Bartlomiej Zolnierkiewicz

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=20090213182456.GA3581@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=kilroyd@googlemail.com \
    --cc=linux-next@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).