All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: werner <w.landgraf@ru.ru>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.37-rc3 problems
Date: Mon, 22 Nov 2010 11:47:36 -0800	[thread overview]
Message-ID: <20101122194736.GA29830@kroah.com> (raw)
In-Reply-To: <20101121211311.05963007.randy.dunlap@oracle.com>

On Sun, Nov 21, 2010 at 09:13:11PM -0800, Randy Dunlap wrote:
> On Sun, 21 Nov 2010 20:56:26 -0800 Randy Dunlap wrote:
> 
> > On Sun, 21 Nov 2010 20:35:20 -0800 Greg KH wrote:
> > 
> > > On Sun, Nov 21, 2010 at 11:20:40PM -0400, werner wrote:
> > > > 2.6.37-rc3 problems
> > > >
> > > > easycap_main.c lines 4251,4 : implicit declaration lock-kernel   ,  
> > > > unlock_kernel
> > > >
> > > > (compilation error)
> > > 
> > > Either disable this driver from your .config, or enable the BKL in your
> > > .config.  I have a pending patch to get to Linus to fix this Kconfig
> > > issue for this driver.
> > 
> > The build error happens even when CONFIG_BKL=y.  In fact, that's the only
> > way to enable EASYCAP, since EASYCAP depends on BKL.
> 
> OTOH, adding <linux/smp_lock.h> to easycap.h fixes the build.

Ah, nice.  Someone want to send me a patch?  :)

thanks,

greg k-h

  reply	other threads:[~2010-11-22 19:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-22  3:20 2.6.37-rc3 problems werner
2010-11-22  4:35 ` Greg KH
2010-11-22  4:56   ` Randy Dunlap
2010-11-22  5:13     ` Randy Dunlap
2010-11-22 19:47       ` Greg KH [this message]
2010-11-22 20:12         ` [PATCH] staging: easycap needs smp_lock.h, fixes build error Randy Dunlap
2010-11-30 14:44           ` werner
2010-11-30 14:57             ` Greg KH
2010-11-30 22:17               ` werner

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=20101122194736.GA29830@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=w.landgraf@ru.ru \
    /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.