All of lore.kernel.org
 help / color / mirror / Atom feed
From: Igor Grinberg <grinberg@compulab.co.il>
To: Cyril Chemparathy <cyril@ti.com>
Cc: netdev@vger.kernel.org,
	davinci-linux-open-source@linux.davincidsp.com,
	linux-omap@vger.kernel.org, nsekhar@ti.com, srk@ti.com
Subject: Re: [PATCH 2/8] davinci: add mdio platform devices
Date: Tue, 03 Aug 2010 17:06:50 +0300	[thread overview]
Message-ID: <4C58227A.4080502@compulab.co.il> (raw)
In-Reply-To: <1280842313-3743-3-git-send-email-cyril@ti.com>

On 08/03/10 16:31, Cyril Chemparathy wrote:
> This patch adds mdio platform devices on SoCs that have the necessary
> hardware.  Clock lookup entries (aliases) have also been added, so that the
> MDIO and EMAC drivers can independently enable/disable a shared underlying
> clock.  Further, the EMAC MMR region has been split down into separate MDIO
> and EMAC regions.
>
> Signed-off-by: Cyril Chemparathy <cyril@ti.com>
> ---
>  arch/arm/mach-davinci/devices-da8xx.c       |   29 +++++++++++++++++++++++++-
>  arch/arm/mach-davinci/dm365.c               |   22 +++++++++++++++++++-
>  arch/arm/mach-davinci/dm644x.c              |   22 +++++++++++++++++++-
>  arch/arm/mach-davinci/dm646x.c              |   22 +++++++++++++++++++-
>  arch/arm/mach-davinci/include/mach/dm365.h  |    1 +
>  arch/arm/mach-davinci/include/mach/dm644x.h |    1 +
>  arch/arm/mach-davinci/include/mach/dm646x.h |    1 +
>  7 files changed, 93 insertions(+), 5 deletions(-)
>   

Shouldn't arch/arm/mach-omap2/board-am3517evm.c be on your list?
I think it should, or else it will be broken by:
[PATCH 5/8] netdev: cleanup unused davinci mdio emac code

-- 
Regards,
Igor.


  reply	other threads:[~2010-08-03 14:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-03 13:31 [PATCH 0/8] split out emac cpdma and mdio for reuse Cyril Chemparathy
2010-08-03 13:31 ` [PATCH 1/8] netdev: separate out davinci mdio controller code Cyril Chemparathy
2010-08-03 23:29   ` Ramirez Luna, Omar
     [not found]   ` <27F9C60D11D683428E133F85D2BB4A53043F3C8C2A@dlee03.ent.ti.com>
2010-08-04  0:44     ` Cyril Chemparathy
2010-08-03 13:31 ` [PATCH 2/8] davinci: add mdio platform devices Cyril Chemparathy
2010-08-03 14:06   ` Igor Grinberg [this message]
2010-08-03 14:32     ` Cyril Chemparathy
2010-08-04  6:58       ` Igor Grinberg
2010-08-03 13:31 ` [PATCH 3/8] netdev: switch davinci emac to new mdio driver Cyril Chemparathy
2010-08-03 13:31 ` [PATCH 4/8] davinci: cleanup unused davinci mdio arch code Cyril Chemparathy
2010-08-03 13:31 ` [PATCH 5/8] netdev: cleanup unused davinci mdio emac code Cyril Chemparathy
2010-08-03 13:31 ` [PATCH 6/8] netdev: separate out davinci cpdma controller code Cyril Chemparathy
2010-08-03 23:30   ` Ramirez Luna, Omar
     [not found]   ` <27F9C60D11D683428E133F85D2BB4A53043F3C8C2B@dlee03.ent.ti.com>
2010-08-04  0:46     ` Cyril Chemparathy
2010-08-03 13:31 ` [PATCH 7/8] netdev: switch davinci emac to new cpdma layer Cyril Chemparathy
2010-08-03 13:31 ` [PATCH 8/8] netdev: cleanup unused davinci emac cpdma code Cyril Chemparathy
2010-08-26 18:39 ` [PATCH 0/8] split out emac cpdma and mdio for reuse Kevin Hilman

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=4C58227A.4080502@compulab.co.il \
    --to=grinberg@compulab.co.il \
    --cc=cyril@ti.com \
    --cc=davinci-linux-open-source@linux.davincidsp.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nsekhar@ti.com \
    --cc=srk@ti.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 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.