From: Greg KH <greg@kroah.com>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
devel@linuxdriverproject.org,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [GIT PATCH] STAGING patches for .39
Date: Thu, 17 Mar 2011 13:04:48 -0700 [thread overview]
Message-ID: <20110317200448.GA17827@kroah.com> (raw)
In-Reply-To: <20110317125538.791c26d9.rdunlap@xenotime.net>
On Thu, Mar 17, 2011 at 12:55:38PM -0700, Randy Dunlap wrote:
> On Wed, 16 Mar 2011 19:02:12 -0700 Greg KH wrote:
>
> > On Wed, Mar 16, 2011 at 06:52:39PM -0700, Greg KH wrote:
> > > On Wed, Mar 16, 2011 at 05:34:08PM -0700, Linus Torvalds wrote:
> > > > On Wed, Mar 16, 2011 at 5:32 PM, Linus Torvalds
> > > > <torvalds@linux-foundation.org> wrote:
> > > > >
> > > > > The one with inifinite errors was vt6655.
> > > >
> > > > vt6656 had same/similar issues. In fact, maybe it's simply because I
> > > > built both of them in, and get infinite "multiple definitions" because
> > > > they are the same driver with small differences?
> > >
> > > Ah, probably, if they are both built into the kernel that might happen
> > > due to the global symbols in them. Actually that's odd, Randy's usual
> > > 'randconfig' tester usually catches these, I'll make the Kconfig files
> > > force them to be modules to keep this from happening in the future.
> >
> > Yes, that looks like the problem, as building them as modules in your
> > tree right now works just fine.
> >
> > This patch below should solve your build issue, let me know if it
> > doesn't.
>
> Thanks for the patch. You had suggested 1-2 months ago that someone do
> this, so I was waiting to see if someone would actually do it.
Ah, sorry about that, I forgot about it.
> I was hoping that a staging developer would do it (not the staging
> maintainer).
Heh, well, these drivers are just "placeholders" as the "real" in-kernel
drivers are being developed for this hardware, so I don't expect to see
much, if any development happening on them.
thanks,
greg k-h
next prev parent reply other threads:[~2011-03-17 20:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 21:03 [GIT PATCH] STAGING patches for .39 Greg KH
[not found] ` <1300309804-3756-1-git-send-email-gregkh@suse.de>
2011-03-16 21:03 ` [PATCH 584/961] staging: brcm80211: Fix memory leak after kmalloc failure Greg Kroah-Hartman
2011-03-17 0:19 ` [GIT PATCH] STAGING patches for .39 Linus Torvalds
2011-03-17 0:28 ` Greg KH
2011-03-17 0:32 ` Linus Torvalds
2011-03-17 0:34 ` Linus Torvalds
2011-03-17 1:52 ` Greg KH
2011-03-17 2:02 ` Greg KH
2011-03-17 19:55 ` Randy Dunlap
2011-03-17 20:04 ` Greg KH [this message]
2011-03-17 20:17 ` Randy Dunlap
2011-03-17 1:51 ` Greg KH
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=20110317200448.GA17827@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=devel@linuxdriverproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=torvalds@linux-foundation.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