All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Alek Du <alek.du@intel.com>, Jacob Pan <jacob.jun.pan@intel.com>
Subject: Re: linux-next: build failure after merge of the final tree (usb tree related)
Date: Thu, 17 Jun 2010 10:25:16 -0700	[thread overview]
Message-ID: <20100617172515.GA20453@kroah.com> (raw)
In-Reply-To: <20100617145331.7bbefc4a.sfr@canb.auug.org.au>

On Thu, Jun 17, 2010 at 02:53:31PM +1000, Stephen Rothwell wrote:
> Hi Greg,
> 
> After merging the final tree, today's linux-next build (powerpc
> allyesconfig) failed like this:
> 
> In file included from drivers/usb/host/ehci-hcd.c:113:
> drivers/usb/host/ehci-dbg.c: In function 'debug_lpm_write':
> drivers/usb/host/ehci-dbg.c:992: error: implicit declaration of function 'copy_from_user'
> 
> Caused by commit a3c0b4b257eeaefe4e6c8fbf5ddfe674242f1b9e ("USB: EHCI:
> EHCI 1.1 addendum: preparation").  Presumably a missing include of
> linux/uaccess.h ...
> 
> I applied this patch for today:

thanks, I've merged your fix in with the main patch so this problem will
not show up, and pushed the updated patches out.

thanks,

greg k-h

  reply	other threads:[~2010-06-17 17:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-17  4:53 linux-next: build failure after merge of the final tree (usb tree related) Stephen Rothwell
2010-06-17 17:25 ` Greg KH [this message]
2010-06-17 22:34   ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2012-10-23  4:13 Stephen Rothwell
2012-10-23  4:22 ` Greg KH
2010-04-30  6:05 Stephen Rothwell
2010-04-30  6:22 ` Heikki Krogerus
2010-05-03  4:57   ` Stephen Rothwell
2010-05-03 17:13     ` Greg KH
2010-05-03 17:35       ` Greg KH
2010-05-03 18:02         ` Greg KH
2010-05-03 22:40           ` Stephen Rothwell

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=20100617172515.GA20453@kroah.com \
    --to=greg@kroah.com \
    --cc=alek.du@intel.com \
    --cc=jacob.jun.pan@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.