From: Shinas Rasheed <srasheed@marvell.com>
To: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <hgani@marvell.com>, <vimleshk@marvell.com>, <egallen@redhat.com>,
<mschmidt@redhat.com>, <pabeni@redhat.com>, <horms@kernel.org>,
<kuba@kernel.org>, <davem@davemloft.net>, <wizhao@redhat.com>,
<konguyen@redhat.com>, Shinas Rasheed <srasheed@marvell.com>
Subject: [PATCH net-next v2 0/2] support OCTEON CN98 devices
Date: Tue, 28 Nov 2023 20:53:46 -0800 [thread overview]
Message-ID: <20231129045348.2538843-1-srasheed@marvell.com> (raw)
Implement device unload control net API required for CN98
devices and add support in driver for the same.
Changes:
V2:
- Changed dev_info print to dev_dbg in device_remove API
V1: https://lore.kernel.org/all/20231127162135.2529363-1-srasheed@marvell.com/
Shinas Rasheed (2):
octeon_ep: implement device unload control net API
octeon_ep: support OCTEON CN98 devices
.../ethernet/marvell/octeon_ep.rst | 1 +
.../marvell/octeon_ep/octep_cn9k_pf.c | 24 +++++++++++++++----
.../marvell/octeon_ep/octep_ctrl_net.c | 16 ++++++++++++-
.../marvell/octeon_ep/octep_ctrl_net.h | 11 +++++++++
.../ethernet/marvell/octeon_ep/octep_main.c | 4 ++++
.../ethernet/marvell/octeon_ep/octep_main.h | 1 +
.../marvell/octeon_ep/octep_regs_cn9k_pf.h | 4 ++++
7 files changed, 56 insertions(+), 5 deletions(-)
--
2.25.1
next reply other threads:[~2023-11-29 4:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 4:53 Shinas Rasheed [this message]
2023-11-29 4:53 ` [PATCH net-next v2 1/2] octeon_ep: implement device unload control net API Shinas Rasheed
2023-11-29 4:53 ` [PATCH net-next v2 2/2] octeon_ep: support OCTEON CN98 devices Shinas Rasheed
2023-12-01 7:20 ` [PATCH net-next v2 0/2] " patchwork-bot+netdevbpf
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=20231129045348.2538843-1-srasheed@marvell.com \
--to=srasheed@marvell.com \
--cc=davem@davemloft.net \
--cc=egallen@redhat.com \
--cc=hgani@marvell.com \
--cc=horms@kernel.org \
--cc=konguyen@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mschmidt@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=vimleshk@marvell.com \
--cc=wizhao@redhat.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®