From: David Miller <davem@davemloft.net>
To: avorontsov@ru.mvista.com
Cc: linuxppc-dev@ozlabs.org, afleming@freescale.com,
Joakim.Tjernlund@transmode.se, netdev@vger.kernel.org
Subject: Re: [PATCH] ucc_geth: Fix build breakage caused by a merge
Date: Tue, 24 Mar 2009 12:07:02 -0700 (PDT) [thread overview]
Message-ID: <20090324.120702.232678762.davem@davemloft.net> (raw)
In-Reply-To: <20090324153734.GA8276@oksana.dev.rtsoft.ru>
From: Anton Vorontsov <avorontsov@ru.mvista.com>
Date: Tue, 24 Mar 2009 18:37:34 +0300
> This patch fixes following build error:
>
> CC ucc_geth.o
> ucc_geth.c: In function 'ucc_geth_probe':
> ucc_geth.c:3644: error: implicit declaration of function 'uec_mdio_bus_name'
> make[2]: *** [ucc_geth.o] Error 1
>
> Signed-off-by: Anton Vorontsov <avorontsov@ru.mvista.com>
Applied, thanks Anton.
prev parent reply other threads:[~2009-03-24 19:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 13:15 make sure ucc_geth.c fixed-link support still works in net-next Kumar Gala
2009-03-24 15:37 ` [PATCH] ucc_geth: Fix build breakage caused by a merge Anton Vorontsov
2009-03-24 19:07 ` David Miller [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=20090324.120702.232678762.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Joakim.Tjernlund@transmode.se \
--cc=afleming@freescale.com \
--cc=avorontsov@ru.mvista.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
/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).