From: Linu Cherian <linuc.decode@gmail.com>
To: netdev@vger.kernel.org, davem@davemloft.net
Cc: Sunil.Goutham@cavium.com, Linu Cherian <lcherian@marvell.com>
Subject: [PATCH net-next 0/4] octeontx2-af: CGX LMAC link bringup and cleanups
Date: Thu, 22 Nov 2018 17:18:33 +0530 [thread overview]
Message-ID: <20181122114837.1030-1-linuc.decode@gmail.com> (raw)
From: Linu Cherian <lcherian@marvell.com>
Patch 1: Code cleanup
Patch 2: Adds support for an unhandled hardware configuration
Patch 3: Preparatory patch for enabling cgx lmac links
Patch 4: Support for enabling cgx lmac links
Linu Cherian (4):
octeontx2-af: Misc cleanups in cgx driver
octeontx2-af: Handle non-contiguous CGX LMAC interfaces
octeontx2-af: Unregister cgx event callbacks gracefully
octeontx2-af: Bringup CGX LMAC links by default
.../net/ethernet/marvell/octeontx2/af/cgx.c | 108 ++++++++++++++++--
.../net/ethernet/marvell/octeontx2/af/cgx.h | 34 +++---
.../ethernet/marvell/octeontx2/af/cgx_fw_if.h | 2 -
.../net/ethernet/marvell/octeontx2/af/rvu.c | 26 +++--
.../net/ethernet/marvell/octeontx2/af/rvu.h | 6 +-
.../ethernet/marvell/octeontx2/af/rvu_cgx.c | 97 ++++++++++++----
.../ethernet/marvell/octeontx2/af/rvu_nix.c | 6 +-
7 files changed, 214 insertions(+), 65 deletions(-)
--
2.19.1
next reply other threads:[~2018-11-22 22:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-22 11:48 Linu Cherian [this message]
2018-11-22 11:48 ` [PATCH net-next 1/4] octeontx2-af: Misc cleanups in cgx driver Linu Cherian
2018-11-22 11:48 ` [PATCH net-next 2/4] octeontx2-af: Handle non-contiguous CGX LMAC interfaces Linu Cherian
2018-11-22 11:48 ` [PATCH net-next 3/4] octeontx2-af: Unregister cgx event callbacks gracefully Linu Cherian
2018-11-22 11:48 ` [PATCH net-next 4/4] octeontx2-af: Bringup CGX LMAC links by default Linu Cherian
2018-11-22 18:26 ` Andrew Lunn
2018-11-22 22:46 ` [EXT] " Cherian, Linu
2018-11-24 1:23 ` [PATCH net-next 0/4] octeontx2-af: CGX LMAC link bringup and cleanups 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=20181122114837.1030-1-linuc.decode@gmail.com \
--to=linuc.decode@gmail.com \
--cc=Sunil.Goutham@cavium.com \
--cc=davem@davemloft.net \
--cc=lcherian@marvell.com \
--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).