linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Harvey Harrison <harvey.harrison@gmail.com>
Cc: Randy Dunlap <randy.dunlap@oracle.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	David Miller <davem@davemloft.net>,
	linux-next@vger.kernel.org, Julius Volz <juliusv@google.com>,
	Simon Horman <horms@verge.net.au>, Greg KH <gregkh@suse.de>,
	Hannes Reinecke <hare@suse.de>
Subject: Re: linux-next: net tree build failure (depca)
Date: Mon, 15 Sep 2008 11:59:17 -0700	[thread overview]
Message-ID: <20080915185917.GB32003@kroah.com> (raw)
In-Reply-To: <1221425376.6397.1.camel@brick>

On Sun, Sep 14, 2008 at 01:49:36PM -0700, Harvey Harrison wrote:
> On Sat, 2008-09-13 at 08:04 -0700, Randy Dunlap wrote:
> > Also this one on i386:
> > 
> > drivers/net/depca.c:404: error: implicit declaration of function 'depca_common_remove'
> > drivers/net/depca.c:1602: error: static declaration of 'depca_common_remove' follows non-static declaration
> > drivers/net/depca.c:404: error: previous implicit declaration of 'depca_common_remove' was here
> > make[2]: *** [drivers/net/depca.o] Error 1
> > 
> 
> I'd already sent a patch for that to those responsible:
> 
> From: Harvey Harrison <harvey.harrison@gmail.com>
> Subject: [PATCH] net: compile fix depca.c
> 
> Adding accessors to the ->driver_data field missed a forward
> declaration that is needed to compile.

Merged in, thanks.

greg k-h

  reply	other threads:[~2008-09-15 19:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-13  5:03 linux-next: net tree build failure Stephen Rothwell
2008-09-13  6:24 ` David Miller
2008-09-13  9:42   ` Stephen Rothwell
2008-09-13 15:04 ` linux-next: net tree build failure (depca) Randy Dunlap
2008-09-14 20:49   ` Harvey Harrison
2008-09-15 18:59     ` Greg KH [this message]
2008-09-15  0:54 ` linux-next: net tree build failure Simon Horman

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=20080915185917.GB32003@kroah.com \
    --to=greg@kroah.com \
    --cc=davem@davemloft.net \
    --cc=gregkh@suse.de \
    --cc=hare@suse.de \
    --cc=harvey.harrison@gmail.com \
    --cc=horms@verge.net.au \
    --cc=juliusv@google.com \
    --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).