All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Paul Chavent <Paul.Chavent@onera.fr>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: 3.10.4-rt1 : too many arguments to function 'phy_connect'
Date: Mon, 12 Aug 2013 13:12:36 +0200	[thread overview]
Message-ID: <20130812111236.GD23040@linutronix.de> (raw)
In-Reply-To: <52088F6B.8080707@onera.fr>

* Paul Chavent | 2013-08-12 09:31:55 [+0200]:

>Hi.
Hi Paul,

>When i compile this version (3.10.4-rt1) for typical da850 (arm omap)
>config i get this error :
>
>  CC      drivers/net/ethernet/ti/davinci_emac.o
>drivers/net/ethernet/ti/davinci_emac.c: In function 'emac_dev_open':
>drivers/net/ethernet/ti/davinci_emac.c:1604:9: error: too many
>arguments to function 'phy_connect'
>         PHY_INTERFACE_MODE_MII);
>         ^
>In file included from drivers/net/ethernet/ti/davinci_emac.c:56:0:
>include/linux/phy.h:522:21: note: declared here
> struct phy_device * phy_connect(struct net_device *dev, const char
>*bus_id,
>                     ^
>
>There are some suspect lines in the patch that add an extra argument
>to the phy_connect function without modifying its signature.
>
>The compilation complete if i remove this extra arg (but the kernel
>don't start, i will check my config for this point).

The series files has a bunch of cpsw patches. For the next -rt release
I'm going to remove all of them as they were only required for the v3.8
release were I backported the cpsw driver. If you drop them, cpsw will
compile. After quick testing I've seen that the cpsw wasn't running nice
but did not crash / hang the system. That is something that should be
investigated.

>Regards.
>
>Paul.

Sebastian

  reply	other threads:[~2013-08-12 11:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-12  7:31 3.10.4-rt1 : too many arguments to function 'phy_connect' Paul Chavent
2013-08-12 11:12 ` Sebastian Andrzej Siewior [this message]
2013-08-28 15:28 ` Paul Gortmaker

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=20130812111236.GD23040@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=Paul.Chavent@onera.fr \
    --cc=linux-rt-users@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 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.