From: David Miller <davem@davemloft.net>
To: l.stach@pengutronix.de
Cc: netdev@vger.kernel.org, Frank.Li@freescale.com,
shawn.guo@linaro.org, festevam@gmail.com
Subject: Re: [PATCH 0/3] URGENT for 3.9: net: fec: revert NAPI introduction
Date: Thu, 25 Apr 2013 15:14:29 -0400 (EDT) [thread overview]
Message-ID: <20130425.151429.1439168768104456280.davem@davemloft.net> (raw)
In-Reply-To: <1366893854.4139.17.camel@weser.hi.pengutronix.de>
From: Lucas Stach <l.stach@pengutronix.de>
Date: Thu, 25 Apr 2013 14:44:14 +0200
> The only way to reliably fix all the failures I'm seeing is really
> reverting the changes, as done with this series. So David please
> consider taking the reverts, even while they are a bit intrusive, they
> are the only way to get a 3.9 release out of the door with a working FEC
> driver.
You'll need to formally resubmit it.
next prev parent reply other threads:[~2013-04-25 19:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 14:36 [PATCH 0/3] URGENT for 3.9: net: fec: revert NAPI introduction Lucas Stach
2013-04-19 14:36 ` [PATCH 1/3] Revert "net: fec: fix missing napi_disable call" Lucas Stach
2013-04-19 14:36 ` [PATCH 2/3] Revert "net: fec: put tx to napi poll function to fix dead lock" Lucas Stach
2013-04-19 14:36 ` [PATCH 3/3] Revert "net: fec: add napi support to improve proformance" Lucas Stach
2013-04-19 17:38 ` [PATCH 0/3] URGENT for 3.9: net: fec: revert NAPI introduction David Miller
2013-04-25 12:44 ` Lucas Stach
2013-04-25 19:14 ` David Miller [this message]
2013-04-19 18:22 ` Fabio Estevam
2013-04-19 18:26 ` David Miller
2013-04-19 20:05 ` Fabio Estevam
2013-04-20 12:35 ` Frank Li
2013-04-22 8:56 ` Lucas Stach
2013-04-22 9:17 ` Frank Li
2013-04-25 12:31 ` Lucas Stach
2013-04-25 14:45 ` Frank Li
2013-04-25 14:57 ` Lucas Stach
2013-04-27 7:12 ` Frank Li
2013-04-25 12:37 ` Lucas Stach
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=20130425.151429.1439168768104456280.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Frank.Li@freescale.com \
--cc=festevam@gmail.com \
--cc=l.stach@pengutronix.de \
--cc=netdev@vger.kernel.org \
--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).