From: Laurent Pinchart <laurentp@cse-semaphore.com>
To: Sergej Stepanov <Sergej.Stepanov@ids.de>
Cc: Scott Wood <scottwood@freescale.com>,
linuxppc-dev@ozlabs.org, jgarzik@pobox.com,
netdev@vger.kernel.org
Subject: Re: [PATCH 6/9] fs_enet: Be an of_platform device when CONFIG_PPC_CPM_NEW_BINDING is set.
Date: Mon, 10 Mar 2008 12:05:08 +0100 [thread overview]
Message-ID: <200803101205.16158.laurentp@cse-semaphore.com> (raw)
In-Reply-To: <1205135421.3837.1.camel@p60365-ste>
[-- Attachment #1: Type: text/plain, Size: 789 bytes --]
On Monday 10 March 2008 08:50, Sergej Stepanov wrote:
> > Acked-by: Scott Wood <scottwood@freescale.com>, if I haven't already.
> >
> > -Scott
>
> I thought, you did it.
> Thank you.
Your documentation patch states that
"The first reg resource is the I/O port register block on which MDIO
resides. The second reg resource is the I/O port register block on
which MDC resides. If there is only one reg resource, it is used for
both MDIO and MDC."
If I'm not mistaken the code uses the first reg resource for MDC and the
second reg resource for MDIO. Which one should be fixed, the doc or the
code ?
Best regards,
--
Laurent Pinchart
CSE Semaphore Belgium
Chaussée de Bruxelles, 732A
B-1410 Waterloo
Belgium
T +32 (2) 387 42 59
F +32 (2) 387 42 75
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-03-10 11:05 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-20 22:00 [PATCH 0/9] fs enet and mdio bitbang patches Scott Wood
2007-09-20 22:01 ` [PATCH 1/9] fs_enet: Whitespace cleanup Scott Wood
2007-09-29 5:21 ` Jeff Garzik
2007-09-20 22:01 ` [PATCH 2/9] fs_enet: Include linux/string.h from linux/fs_enet_pd.h Scott Wood
2007-09-20 22:01 ` [PATCH 3/9] fs_enet: Don't share the interrupt Scott Wood
2007-09-29 5:18 ` Jeff Garzik
2007-09-20 22:01 ` [PATCH 4/9] fs_enet: mac-fcc: Eliminate __fcc-* macros Scott Wood
2007-09-20 22:01 ` [PATCH 5/9] fs_enet: Align receive buffers Scott Wood
2007-09-20 22:01 ` [PATCH 6/9] fs_enet: Be an of_platform device when CONFIG_PPC_CPM_NEW_BINDING is set Scott Wood
2007-09-21 0:08 ` Stephen Rothwell
2007-09-21 0:44 ` Scott Wood
2007-10-02 7:10 ` Esben Haabendal
2008-02-15 12:50 ` Laurent Pinchart
2008-02-15 15:38 ` Sergej Stepanov
2008-03-07 15:23 ` Laurent Pinchart
2008-03-07 16:37 ` Scott Wood
2008-03-10 7:50 ` Sergej Stepanov
2008-03-10 11:05 ` Laurent Pinchart [this message]
2008-03-10 13:17 ` Sergej Stepanov
2008-03-10 15:02 ` [PATCH v3] using mii-bitbang on different processor ports - update the booting-without-of.txt-file Sergej Stepanov
2007-09-20 22:01 ` [PATCH 7/9] Generic bitbanged MDIO library Scott Wood
2007-10-18 19:20 ` [PATCH] phy/bitbang: missing MODULE_LICENSE Randy Dunlap
2007-10-20 3:03 ` Jeff Garzik
2007-09-20 22:01 ` [PATCH 8/9] fs_enet: Convert mii-bitbang to use the generic bitbang MDIO code Scott Wood
2007-09-20 22:01 ` [PATCH 9/9] fs_enet: sparse fixes Scott Wood
-- strict thread matches above, loose matches on Subject: below --
2007-09-24 20:08 [PATCH 6/9] fs_enet: Be an of_platform device when CONFIG_PPC_CPM_NEW_BINDING is set Scott Wood
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=200803101205.16158.laurentp@cse-semaphore.com \
--to=laurentp@cse-semaphore.com \
--cc=Sergej.Stepanov@ids.de \
--cc=jgarzik@pobox.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=scottwood@freescale.com \
/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).