From: Shawn Guo <shawn.guo@linaro.org>
To: "fugang.duan@freescale.com" <fugang.duan@freescale.com>,
"davem@davemloft.net" <davem@davemloft.net>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"bhutchings@solarflare.com" <bhutchings@solarflare.com>,
"stephen@networkplumber.org" <stephen@networkplumber.org>
Subject: Re: [PATCH net-next v1 2/3] ARM: imx: add FEC sleep mode callback function
Date: Wed, 7 Jan 2015 11:17:00 +0800 [thread overview]
Message-ID: <20150107031658.GB4928@dragon> (raw)
In-Reply-To: <BLUPR03MB37385464C06052A231ABF19F5460@BLUPR03MB373.namprd03.prod.outlook.com>
On Wed, Jan 07, 2015 at 02:40:33AM +0000, fugang.duan@freescale.com wrote:
> Yes, the platform code will become quite messy and tremendous.
> I agree with your thinking.
>
> But David applied the patches, how can I do it now ?
David,
Can you please drop the last two arch/arm/ patches, or revert them if
your tree is non-rebasable?
Shawn
next prev parent reply other threads:[~2015-01-07 3:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-24 9:30 [PATCH net-next v1 0/3] net: fec: add Wake-on-LAN support Fugang Duan
2014-12-24 9:30 ` [PATCH net-next v1 1/3] " Fugang Duan
2014-12-24 9:30 ` [PATCH net-next v1 2/3] ARM: imx: add FEC sleep mode callback function Fugang Duan
2015-01-06 11:48 ` Shawn Guo
2015-01-07 1:41 ` fugang.duan
2015-01-07 2:33 ` Shawn Guo
2015-01-07 2:40 ` fugang.duan
2015-01-07 3:17 ` Shawn Guo [this message]
2015-01-07 12:02 ` David Miller
2015-01-07 3:44 ` Fabio Estevam
2014-12-24 9:30 ` [PATCH net-next v1 3/3] ARM: dts: imx6qdl: enable FEC magic-packet feature Fugang Duan
2014-12-31 18:07 ` [PATCH net-next v1 0/3] net: fec: add Wake-on-LAN support David Miller
2014-12-31 19:03 ` Fabio Estevam
2014-12-31 19:20 ` David Miller
2014-12-31 19:22 ` Fabio Estevam
2015-01-04 1:39 ` fugang.duan
2015-01-06 11:21 ` Shawn Guo
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=20150107031658.GB4928@dragon \
--to=shawn.guo@linaro.org \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=fugang.duan@freescale.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.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).