All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for June 4 (staging)
Date: Thu, 4 Jun 2009 11:07:01 -0700	[thread overview]
Message-ID: <20090604180701.GA24896@suse.de> (raw)
In-Reply-To: <4A27EEB8.6030408@oracle.com>

On Thu, Jun 04, 2009 at 08:56:40AM -0700, Randy Dunlap wrote:
> Stephen Rothwell wrote:
> > Hi all,
> > 
> > Changes since 20090603:
> 
> drivers/staging/vt6655/built-in.o: In function `rotr1':
> (.text+0x1a883): multiple definition of `rotr1'
> drivers/staging/rt2860/built-in.o:(.text+0x17a9a): first defined here
> drivers/staging/vt6655/built-in.o: In function `tkip_sbox':
> (.text+0x1a850): multiple definition of `tkip_sbox'
> drivers/staging/rt2860/built-in.o:(.text+0x17a6b): first defined here
> drivers/staging/vt6655/built-in.o: In function `xor_32':
> (.text+0x1e938): multiple definition of `xor_32'
> drivers/staging/rt2860/built-in.o:(.text+0x1803c): first defined here
> drivers/staging/vt6655/built-in.o: In function `xor_128':
> (.text+0x1e910): multiple definition of `xor_128'
> drivers/staging/rt2860/built-in.o:(.text+0x18018): first defined here

Ick, more staging drivers that should not be built-in.  I'll go mess
with some Kconfig options...

thanks,

greg k-h

  reply	other threads:[~2009-06-04 18:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-04  7:56 linux-next: Tree for June 4 Stephen Rothwell
2009-06-04 15:56 ` linux-next: Tree for June 4 (staging) Randy Dunlap
2009-06-04 18:07   ` Greg KH [this message]
2009-06-04 16:47 ` [PATCH -next] eeepc: fix pci & hotplug selects Randy Dunlap

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=20090604180701.GA24896@suse.de \
    --to=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --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 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.