From: Sean Wang <sean.wang@mediatek.com>
To: <john@phrozen.org>, <davem@davemloft.net>
Cc: <nbd@openwrt.org>, <netdev@vger.kernel.org>,
<linux-mediatek@lists.infradead.org>, <keyhaede@gmail.com>,
Sean Wang <sean.wang@mediatek.com>
Subject: [PATCH v2 0/5] Fix warning, issue and give some enhancements
Date: Tue, 16 Aug 2016 01:51:21 +0800 [thread overview]
Message-ID: <1471283487-24113-1-git-send-email-sean.wang@mediatek.com> (raw)
This patch set fixes the following warning and issues and gives some
enhancements about RX path handling.
v1 -> v2: fix message typos and add coverletter
Sean Wang (5):
net: ethernet: mediatek: add REVMII and fix RMII mode supported by
GMAC
net: ethernet: mediatek: fix flow control settings on GMAC0 is not
being enabled properly
net: ethernet: mediatek: fix runtime warning raised by inconsistent
struct device pointers passed to DMA API
net: ethernet: mediatek: enhance RX path by reducing the frequency of
the memory barrier used
net: ethernet: mediatek: enhance RX path by aggregating more skbs
into NAPI
drivers/net/ethernet/mediatek/mtk_eth_soc.c | 70 ++++++++++++++++-----------
1 file changed, 42 insertions(+), 28 deletions(-)
--
1.7.9.5
next reply other threads:[~2016-08-15 17:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-15 17:51 Sean Wang [this message]
2016-08-15 17:51 ` [PATCH v2 1/5] net: ethernet: mediatek: add REVMII and fix RMII mode supported by GMAC Sean Wang
2016-08-15 17:51 ` [PATCH v2 2/5] net: ethernet: mediatek: fix flow control settings on GMAC0 is not being enabled properly Sean Wang
2016-08-15 17:51 ` [PATCH v2 3/5] net: ethernet: mediatek: fix runtime warning raised by inconsistent struct device pointers passed to DMA API Sean Wang
2016-08-15 17:51 ` [PATCH v2 4/5] net: ethernet: mediatek: enhance RX path by reducing the frequency of the memory barrier used Sean Wang
2016-08-15 17:51 ` [PATCH v2 5/5] net: ethernet: mediatek: enhance RX path by aggregating more skbs into NAPI Sean Wang
2016-08-15 20:50 ` [PATCH v2 0/5] Fix warning, issue and give some enhancements 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=1471283487-24113-1-git-send-email-sean.wang@mediatek.com \
--to=sean.wang@mediatek.com \
--cc=davem@davemloft.net \
--cc=john@phrozen.org \
--cc=keyhaede@gmail.com \
--cc=linux-mediatek@lists.infradead.org \
--cc=nbd@openwrt.org \
--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).