From: Marcin Wojtas <mw@semihalf.com>
To: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org
Cc: davem@davemloft.net, linux@arm.linux.org.uk,
sebastian.hesselbarth@gmail.com, andrew@lunn.ch,
jason@lakedaemon.net, thomas.petazzoni@free-electrons.com,
gregory.clement@free-electrons.com,
ezequiel.garcia@free-electrons.com, nadavh@marvell.com,
alior@marvell.com, mw@semihalf.com, jaz@semihalf.com,
tn@semihalf.com
Subject: [PATCH net 0/3] Marvell Armada 375 mvpp2 fixes
Date: Thu, 3 Dec 2015 15:20:48 +0100 [thread overview]
Message-ID: <1449152451-2939-1-git-send-email-mw@semihalf.com> (raw)
Hi,
During my work on mvneta driver I revised mvpp2, and it occurred that the
initial version of Marvell Armada 375 SoC comprised bugs around
DMA-unmapping in both ingress and egress paths - not all buffers were
umapped in TX path and none(!) in RX. Three patches that I send fix
this situation.
Any feedback would be welcome.
Best regards,
Marcin Wojtas
Marcin Wojtas (3):
net: mvpp2: fix missing DMA region unmap in egress processing
net: mvpp2: fix buffers' DMA handling on RX path
net: mvpp2: fix refilling BM pools in RX path
drivers/net/ethernet/marvell/mvpp2.c | 52 +++++++++++++++++++++++-------------
1 file changed, 33 insertions(+), 19 deletions(-)
--
1.8.3.1
next reply other threads:[~2015-12-03 14:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-03 14:20 Marcin Wojtas [this message]
2015-12-03 14:20 ` [PATCH net 1/3] net: mvpp2: fix missing DMA region unmap in egress processing Marcin Wojtas
2015-12-03 14:20 ` [PATCH net 2/3] net: mvpp2: fix buffers' DMA handling on RX path Marcin Wojtas
2015-12-03 14:20 ` [PATCH net 3/3] net: mvpp2: fix refilling BM pools in " Marcin Wojtas
2015-12-04 20:01 ` [PATCH net 0/3] Marvell Armada 375 mvpp2 fixes 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=1449152451-2939-1-git-send-email-mw@semihalf.com \
--to=mw@semihalf.com \
--cc=alior@marvell.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=ezequiel.garcia@free-electrons.com \
--cc=gregory.clement@free-electrons.com \
--cc=jason@lakedaemon.net \
--cc=jaz@semihalf.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nadavh@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=thomas.petazzoni@free-electrons.com \
--cc=tn@semihalf.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
all inboxes | Powered by JetHome®