netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: shawn.guo@freescale.com
Cc: LW@KARO-electronics.de, shawn.guo@linaro.org,
	netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	patches@linaro.org
Subject: Re: [PATCH 3/4] net/fec: set phy_speed to the optimal frequency 2.5 MHz
Date: Tue, 20 Sep 2011 15:11:11 -0400 (EDT)	[thread overview]
Message-ID: <20110920.151111.456825259983009921.davem@davemloft.net> (raw)
In-Reply-To: <20110920081438.GB28389@S2100-06.ap.freescale.net>

From: Shawn Guo <shawn.guo@freescale.com>
Date: Tue, 20 Sep 2011 16:14:39 +0800

> I should have done that before sending this patch.  I'm working home
> these days and have not got the chance get into the lab.  Yes, I
> should have sent this patch as an RFC at least.  Sorry about this,
> and thank you for pointing this out.
> 
> Will drop this patch from the v2 of the series.

As mentioned you need to respin this anyways against net-next

  reply	other threads:[~2011-09-20 19:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-18 11:54 [PATCH 0/4] add fec support for imx6q Shawn Guo
2011-09-18 11:54 ` [PATCH 1/4] net/fec: change phy-reset-gpio request warning to debug message Shawn Guo
2011-09-18 11:54 ` [PATCH 2/4] net/fec: fix fec1 check in fec_enet_mii_init() Shawn Guo
2011-09-18 11:54 ` [PATCH 3/4] net/fec: set phy_speed to the optimal frequency 2.5 MHz Shawn Guo
2011-09-19 22:39   ` Troy Kisky
2011-09-20  2:57     ` Shawn Guo
2011-09-20 20:05       ` Troy Kisky
2011-09-20 20:10         ` Troy Kisky
2011-09-20  7:50   ` Lothar Waßmann
2011-09-20  8:14     ` Shawn Guo
2011-09-20 19:11       ` David Miller [this message]
2011-09-18 11:54 ` [PATCH 4/4] net/fec: add imx6q enet support Shawn Guo
2011-09-18 18:09   ` Francois Romieu
2011-09-19  9:08     ` Shawn Guo
2011-09-20 19:08 ` [PATCH 0/4] add fec support for imx6q David Miller

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=20110920.151111.456825259983009921.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=LW@KARO-electronics.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=netdev@vger.kernel.org \
    --cc=patches@linaro.org \
    --cc=shawn.guo@freescale.com \
    --cc=shawn.guo@linaro.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).