linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: ddaney.cavm@gmail.com
Cc: sfr@canb.auug.org.au, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, paul.gortmaker@windriver.com,
	rdunlap@xenotime.net, linux-next@vger.kernel.org,
	linuxppc-dev@lists.ozlabs.org, bjorn@mork.no
Subject: Re: [PATCH] net: of/phy: fix build error when phylib is built as a module
Date: Fri, 11 May 2012 18:03:28 -0400 (EDT)	[thread overview]
Message-ID: <20120511.180328.1412689186292656882.davem@davemloft.net> (raw)
In-Reply-To: <4FAD532E.401@gmail.com>

From: David Daney <ddaney.cavm@gmail.com>
Date: Fri, 11 May 2012 10:58:06 -0700

> On 05/11/2012 08:47 AM, Bj=F8rn Mork wrote:
>> CONFIG_OF_MDIO is tristate and will be m if PHYLIB is m.  Use
>> IS_ENABLED macro to prevent build error:
>>
>>   ERROR: "of_mdio_find_bus" [drivers/net/phy/mdio-mux.ko] undefined!=

>>
>> Reported-by: Randy Dunlap<rdunlap@xenotime.net>
>> Cc: David Daney<david.daney@cavium.com>
>> Signed-off-by: Bj=F8rn Mork<bjorn@mork.no>
> =

> I was able to reproduce the failure, and this patch both fixes it and=

> seems correct, so...
> =

> Acked-by: David Daney<david.daney@cavium.com>

Applied.

  reply	other threads:[~2012-05-11 22:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20120510192635.c6f3a55196bbf65f13956e44@canb.auug.org.au>
     [not found] ` <4FAC35E2.4060900@xenotime.net>
2012-05-11  2:36   ` linux-next: Tree for May 10 (net/phy) Paul Gortmaker
2012-05-11  2:43     ` David Miller
2012-05-11 15:47       ` [PATCH] net: of/phy: fix build error when phylib is built as a module Bjørn Mork
2012-05-11 17:58         ` David Daney
2012-05-11 22:03           ` David Miller [this message]
2012-05-11 21:24         ` David Miller
2012-05-11 23:50         ` Randy Dunlap
2012-05-11 16:14       ` linux-next: Tree for May 10 (net/phy) David Daney

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=20120511.180328.1412689186292656882.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=bjorn@mork.no \
    --cc=ddaney.cavm@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=netdev@vger.kernel.org \
    --cc=paul.gortmaker@windriver.com \
    --cc=rdunlap@xenotime.net \
    --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).