All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
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 March 13 (PCI patch)
Date: Thu, 13 Mar 2008 15:02:38 -0700	[thread overview]
Message-ID: <20080313220238.GA404@kroah.com> (raw)
In-Reply-To: <20080313100235.89cf2508.randy.dunlap@oracle.com>

On Thu, Mar 13, 2008 at 10:02:35AM -0700, Randy Dunlap wrote:
> On Thu, 13 Mar 2008 17:35:06 +1100 Stephen Rothwell wrote:
> 
> > Hi all,
> > 
> > I have created today's linux-next tree at
> > git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git
> > (tar balls at
> > http://www.kernel.org/pub/linux/kernel/people/sfr/linux-next/).
> 
> ---
> 
> From: Randy Dunlap <randy.dunlap@oracle.com>
> 
> access.c uses udelay() so needs to #include delay.h.
> 
> next-20080313/drivers/pci/access.c:167: error: implicit declaration of function 'udelay'
> make[3]: *** [drivers/pci/access.o] Error 1
> make[2]: *** [drivers/pci] Error 2
> make[1]: *** [drivers] Error 2
> make[1]: *** Waiting for unfinished jobs....
> make: *** [sub-make] Error 2
> 
> Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
> ---
>  drivers/pci/access.c |    1 +
>  1 file changed, 1 insertion(+)
> 
> --- next-20080313.orig/drivers/pci/access.c
> +++ next-20080313/drivers/pci/access.c
> @@ -1,3 +1,4 @@
> +#include <linux/delay.h>
>  #include <linux/pci.h>
>  #include <linux/module.h>
>  #include <linux/sched.h>

Thanks, I've merged this with the offending patch so there are no build
errors.

greg k-h

      reply	other threads:[~2008-03-13 22:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-13  6:35 linux-next: Tree for March 13 Stephen Rothwell
2008-03-13 10:31 ` Geert Uytterhoeven
2008-03-14  2:44   ` Stephen Rothwell
2008-03-13 17:02 ` linux-next: Tree for March 13 (PCI patch) Randy Dunlap
2008-03-13 22:02   ` Greg KH [this message]

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=20080313220238.GA404@kroah.com \
    --to=greg@kroah.com \
    --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.