linux-next.vger.kernel.org archive mirror
 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 July 13 (staging/usbip)
Date: Mon, 13 Jul 2009 10:06:13 -0700	[thread overview]
Message-ID: <20090713170613.GA22583@suse.de> (raw)
In-Reply-To: <20090713093443.4d3ecfb1.randy.dunlap@oracle.com>

On Mon, Jul 13, 2009 at 09:34:43AM -0700, Randy Dunlap wrote:
> On Mon, 13 Jul 2009 09:25:11 -0700 Greg KH wrote:
> 
> > On Mon, Jul 13, 2009 at 08:59:15AM -0700, Randy Dunlap wrote:
> > > On Mon, 13 Jul 2009 18:05:24 +1000 Stephen Rothwell wrote:
> > > 
> > > > Hi all,
> > > > 
> > > > Changes since 20090710:
> > > 
> > > 
> > > drivers/staging/usbip/usbip_common.c: In function 'usbip_thread':
> > > drivers/staging/usbip/usbip_common.c:386: error: implicit declaration of function 'lock_kernel'
> > > drivers/staging/usbip/usbip_common.c:390: error: implicit declaration of function 'unlock_kernel'
> > > 
> > > config attached.
> > 
> > Odd, that code has not changed at all.
> > 
> > Did we just loose the big kernel lock somehow?
> 
> I dunno.  Probably some header file cleanup thing.  :(
> 
> Looks like only linux/smp_lock.h #defines it, but a driver shouldn't
> need to #include that file IMHO.

Jean just sent me a patch fixing this, so I'll queue it up for the next
round of patches to go to Linus.

thanks,

greg k-h

  parent reply	other threads:[~2009-07-13 17:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-13  8:05 linux-next: Tree for July 13 Stephen Rothwell
2009-07-13 15:56 ` linux-next: Tree for July 13 (usb/serial/option) Randy Dunlap
2009-07-13 15:59 ` linux-next: Tree for July 13 (staging/usbip) Randy Dunlap
2009-07-13 16:25   ` Greg KH
2009-07-13 16:34     ` Randy Dunlap
2009-07-13 17:02       ` Randy Dunlap
2009-07-13 17:06       ` Greg KH [this message]
2009-07-13 18:33 ` linux-next: Tree for July 13 Robin Getz

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=20090713170613.GA22583@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 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).