linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matt Porter <mporter@ti.com>
To: Paul Walmsley <paul@pwsan.com>
Cc: Yegor Yefremov <yegor_sub1@visionsystems.de>,
	Tony Lindgren <tony@atomide.com>, Ilya Yanok <yanok@emcraft.com>,
	linux-omap@vger.kernel.org, sasha_d@emcraft.com
Subject: Re: [PATCH] OMAP3: clock3xxx_data: change EMAC clocks aliases
Date: Thu, 9 Feb 2012 16:03:54 -0500	[thread overview]
Message-ID: <20120209210354.GC30410@h56-17.vpn.ti.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1202091314320.6698@utopia.booyaka.com>

On Thu, Feb 09, 2012 at 01:20:50PM -0700, Paul Walmsley wrote:
> Hi Matt
> 
> On Thu, 9 Feb 2012, Matt Porter wrote:
> 
> > Thanks Paul.
> > 
> > Any chance we can see it in 3.3 fixes? It's the only thing preventing 
> > the emac and thus nfsroot from working in 3.3 for these systems.
> 
> Did EMAC work on previous versions of Linux for those systems? i.e., does 
> this patch fix a regression?

It's been broken since at least 2.6.37 (predating my time working with
these parts) when the MDIO driver was split out from the EMAC driver. As
it was so long ago, I won't try to classify this as fixing a regression
since most likely something else was broken in that timeframe. :) Thanks
for the clarification.

-Matt

      reply	other threads:[~2012-02-09 21:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-20 23:27 [PATCH] OMAP3: clock3xxx_data: change EMAC clocks aliases Ilya Yanok
2012-02-06  8:27 ` Yegor Yefremov
2012-02-09 19:09   ` Matt Porter
2012-02-09 19:45     ` Paul Walmsley
2012-02-09 20:11       ` Matt Porter
2012-02-09 20:20         ` Paul Walmsley
2012-02-09 21:03           ` Matt Porter [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=20120209210354.GC30410@h56-17.vpn.ti.com \
    --to=mporter@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=sasha_d@emcraft.com \
    --cc=tony@atomide.com \
    --cc=yanok@emcraft.com \
    --cc=yegor_sub1@visionsystems.de \
    /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).