From: David Miller <davem@davemloft.net>
To: peppe.cavallaro@st.com
Cc: netdev@vger.kernel.org, bhutchings@solarflare.com
Subject: Re: [net-next.git 0/6 (V5)] stmmac: remove dead code for STMMAC_TIMER and add new mitigation schema
Date: Mon, 26 Nov 2012 17:23:03 -0500 (EST) [thread overview]
Message-ID: <20121126.172303.1672761221381936338.davem@davemloft.net> (raw)
In-Reply-To: <1353921046-5121-1-git-send-email-peppe.cavallaro@st.com>
From: Giuseppe CAVALLARO <peppe.cavallaro@st.com>
Date: Mon, 26 Nov 2012 10:10:40 +0100
> These patch series remove the STMMAC_TIMER option no longer updated
> and never used and add a new mitigation schema.
> Having removed the Timer opt, this has made the driver slim.
> On top of this work, it has been easier to introduce the new
> mitigation schema based on HW RX-watchdog (available in new cores).
> In fact, 3.50 and newer cores have an HW RX-Watchdog that can be used for
> mitigating the Rx-interrupts and first results look promising.
All applied to net-next
prev parent reply other threads:[~2012-11-26 22:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-26 9:10 [net-next.git 0/6 (V5)] stmmac: remove dead code for STMMAC_TIMER and add new mitigation schema Giuseppe CAVALLARO
2012-11-26 9:10 ` [net-next.git 1/6] stmmac: remove dead code for STMMAC_TIMER support Giuseppe CAVALLARO
2012-11-26 9:10 ` [net-next.git 2/6 (V3)] stmmac: add the initial tx coalesce schema Giuseppe CAVALLARO
2012-11-26 9:10 ` [net-next.git 3/6 (V4)] stmmac: add Rx watchdog support to mitigate the DMA irqs Giuseppe CAVALLARO
2012-11-26 9:10 ` [net-next.git 4/6 (V2)] stmmac: get/set coalesce parameters via ethtool Giuseppe CAVALLARO
2012-11-26 9:10 ` [net-next.git 5/6] stmmac: update the doc with new IRQ mitigation Giuseppe CAVALLARO
2012-11-26 9:10 ` [net-next.git 6/6] stmmac: update the driver version to Nov_2012 Giuseppe CAVALLARO
2012-11-26 22:23 ` David Miller [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=20121126.172303.1672761221381936338.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bhutchings@solarflare.com \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.com \
/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).