From: Felipe Balbi <balbi@ti.com>
To: Mugunthan V N <mugunthanvnm@ti.com>
Cc: Felipe Balbi <balbi@ti.com>, <davem@davemloft.net>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
<netdev@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>
Subject: Re: [PATCH 1/2] drivers: net: cpsw: fix dt probe for one port ethernet
Date: Thu, 12 Dec 2013 09:44:58 -0600 [thread overview]
Message-ID: <20131212154458.GA31694@saruman.home> (raw)
In-Reply-To: <52A96F9F.7060801@ti.com>
[-- Attachment #1: Type: text/plain, Size: 719 bytes --]
Hi,
On Thu, Dec 12, 2013 at 01:41:11PM +0530, Mugunthan V N wrote:
> On Thursday 12 December 2013 09:39 AM, Felipe Balbi wrote:
> > From: Mugunthan V N <mugunthanvnm@ti.com>
> >
> > When only one port of the two port is pinned out, then dt probe is failing
> > because second port phy is not found. fixing this by checking the number of
> > slaves and breaking the loop.
> >
> > Signed-off-by: Mugunthan V N <mugunthanvnm@ti.com>
> > Signed-off-by: Felipe Balbi <balbi@ti.com>
>
> This patch is already applied to net branch and its commit id is
> 3a27bfac17fe375539c4e0a53478679645eb5ae2.
Ok, cool. Should it be backported to v3.12 stable tree ? I can see it's
applicable there too.
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2013-12-12 15:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-12 4:09 [PATCH 1/2] drivers: net: cpsw: fix dt probe for one port ethernet Felipe Balbi
2013-12-12 4:09 ` [PATCH 2/2] drivers: net: cpsw: fix for cpsw crash when build as modules Felipe Balbi
2013-12-12 18:47 ` David Miller
2013-12-12 8:11 ` [PATCH 1/2] drivers: net: cpsw: fix dt probe for one port ethernet Mugunthan V N
2013-12-12 15:44 ` Felipe Balbi [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=20131212154458.GA31694@saruman.home \
--to=balbi@ti.com \
--cc=bigeasy@linutronix.de \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=mugunthanvnm@ti.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).