From: Geoff Levand <geoff@infradead.org>
To: David S. Miller <davem@davemloft.net>, Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, linuxppc-dev@lists.ozlabs.org
Subject: [PATCH v3 0/2] DMA fixes for PS3 gelic network driver
Date: Sun, 11 Jul 2021 04:15:25 +0000 [thread overview]
Message-ID: <cover.1625976141.git.geoff@infradead.org> (raw)
Hi Dave, Jakub,
This set of patches fixes various DMA related problems in the PS3 gelic
network driver and adds better error checking and improved message logging.
Please consider.
Changes from v2:
Rebase to latest net-next.
Changes from v1:
Split the v1 series into two, one series with powerpc changes, and one series
with gelic network driver changes.
-Geoff
The following changes since commit 5e437416ff66981d8154687cfdf7de50b1d82bfc:
Merge branch 'dsa-mv88e6xxx-topaz-fixes' (2021-07-01 11:51:36 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/geoff/ps3-linux.git for-merge-dma-net
for you to fetch changes up to ffb7b2f4ac085986f563131e3851e07393cd514f:
net/ps3_gelic: Cleanups, improve logging (2021-07-10 20:42:42 -0700)
----------------------------------------------------------------
Geoff Levand (2):
net/ps3_gelic: Add gelic_descr structures
net/ps3_gelic: Cleanups, improve logging
drivers/net/ethernet/toshiba/ps3_gelic_net.c | 968 +++++++++++++++------------
drivers/net/ethernet/toshiba/ps3_gelic_net.h | 24 +-
2 files changed, 557 insertions(+), 435 deletions(-)
--
2.25.1
next reply other threads:[~2021-07-11 4:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-11 4:15 Geoff Levand [this message]
2021-07-11 4:15 ` [PATCH v3 1/2] net/ps3_gelic: Add gelic_descr structures Geoff Levand
2021-07-11 14:03 ` Christophe Leroy
2021-07-17 22:36 ` Geoff Levand
2021-07-11 4:15 ` [PATCH v3 2/2] net/ps3_gelic: Cleanups, improve logging Geoff Levand
2021-07-11 14:10 ` Christophe Leroy
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=cover.1625976141.git.geoff@infradead.org \
--to=geoff@infradead.org \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linuxppc-dev@lists.ozlabs.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).