From: Grant Likely <grant.likely@secretlab•ca>
To: Benjamin Herrenschmidt <benh@kernel•crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs•org>,
David Miller <davem@davemloft•net>
Subject: Re: Build error
Date: Tue, 31 Mar 2009 14:52:22 -0600 [thread overview]
Message-ID: <fa686aa40903311352x1683ab55rada5f77458013864@mail.gmail.com> (raw)
In-Reply-To: <1238455136.17330.12.camel@pasglop>
On Mon, Mar 30, 2009 at 5:18 PM, Benjamin Herrenschmidt
<benh@kernel•crashing.org> wrote:
> On Mon, 2009-03-30 at 17:59 +0400, Anton Vorontsov wrote:
>> On Mon, Mar 30, 2009 at 08:51:38AM -0500, Kumar Gala wrote:
>> >
>> > On Mar 29, 2009, at 10:25 PM, Benjamin Herrenschmidt wrote:
>> >
>> >> My next branch (after merging from you):
>> >>
>> >> ERROR: "fsl_pq_mdio_bus_name" [drivers/net/gianfar_driver.ko]
>> >> undefined!
>> >>
>> >> I'll ask Linus to pull anyway though.
>> >>
>> >> Cheers,
>> >> Ben.
>> >
>> > I believe this is fixed in net-next (and possible linus has already
>> > pulled that in.)
>>
>> FWIW, I can't reproduce the issue neither in benh/powerpc.git `next'
>> branch nor in `merge' branch...
>
> Ah .. .weird :-)
>
> Oh well, I'll see if it still happens after I pull back from Linus (who
> merged all our stuff) and if it does, I'll send you my .config.
It is triggered when the driver is built as a module. I'm going to
post the fix right now.
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
prev parent reply other threads:[~2009-03-31 20:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-30 3:25 Build error Benjamin Herrenschmidt
2009-03-30 13:51 ` Kumar Gala
2009-03-30 13:59 ` Anton Vorontsov
2009-03-30 23:18 ` Benjamin Herrenschmidt
2009-03-31 20:41 ` Segher Boessenkool
2009-03-31 20:54 ` Grant Likely
2009-03-31 20:57 ` Anton Vorontsov
2009-03-31 20:52 ` Grant Likely [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=fa686aa40903311352x1683ab55rada5f77458013864@mail.gmail.com \
--to=grant.likely@secretlab$(echo .)ca \
--cc=benh@kernel$(echo .)crashing.org \
--cc=davem@davemloft$(echo .)net \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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