From: Joe Perches <joe@perches.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: davem@davemloft.net, Frank.Li@freescale.com,
netdev@vger.kernel.org,
Fabio Estevam <fabio.estevam@freescale.com>
Subject: Re: [PATCH] fec: Fix PHC device log
Date: Sat, 13 Apr 2013 10:10:24 -0700 [thread overview]
Message-ID: <1365873024.2358.7.camel@joe-AO722> (raw)
In-Reply-To: <CAOMZO5DfOXxZ5pgvgxgaKXgP0_XMvrfTUdMqMhMDFPLb4ZtsVQ@mail.gmail.com>
On Sat, 2013-04-13 at 13:54 -0300, Fabio Estevam wrote:
> On Sat, Apr 13, 2013 at 1:49 PM, Joe Perches <joe@perches.com> wrote:
>
> > Maybe better as:
> > netdev_info(ndev, "registered PHC device %d\n", fep->dev_id);
>
> In this case I get:
>
> fec 2188000.ethernet (unregistered net_device): registered PHC device 0
Everything in fec_probe between the alloc_etherdev
and register_netdev would get that, but the actual
registered netdev name perhaps is not guaranteed to
be fep->dev_id.
prev parent reply other threads:[~2013-04-13 17:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-13 16:38 [PATCH] fec: Fix PHC device log Fabio Estevam
2013-04-13 16:49 ` Joe Perches
2013-04-13 16:54 ` Fabio Estevam
2013-04-13 17:10 ` Joe Perches [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=1365873024.2358.7.camel@joe-AO722 \
--to=joe@perches.com \
--cc=Frank.Li@freescale.com \
--cc=davem@davemloft.net \
--cc=fabio.estevam@freescale.com \
--cc=festevam@gmail.com \
--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).