From: Simon Horman <horms@kernel.org>
To: Shinas Rasheed <srasheed@marvell.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
hgani@marvell.com, vimleshk@marvell.com, egallen@redhat.com,
mschmidt@redhat.com, pabeni@redhat.com, kuba@kernel.org,
davem@davemloft.net, wizhao@redhat.com, kheib@redhat.com,
konguyen@redhat.com, shenjian15@huawei.com,
Veerasenareddy Burru <vburru@marvell.com>,
Sathesh Edara <sedara@marvell.com>,
Eric Dumazet <edumazet@google.com>
Subject: Re: [PATCH net-next v6 3/4] octeon_ep: control net framework to support VF offloads
Date: Sat, 16 Dec 2023 17:48:50 +0000 [thread overview]
Message-ID: <20231216174850.GR6288@kernel.org> (raw)
In-Reply-To: <20231215181425.2681426-4-srasheed@marvell.com>
On Fri, Dec 15, 2023 at 10:14:24AM -0800, Shinas Rasheed wrote:
> Inquire firmware on supported offloads, as well as convey offloads
> enabled dynamically to firmware for the VFs. Implement control net API
> to support the same.
>
> Signed-off-by: Shinas Rasheed <srasheed@marvell.com>
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2023-12-16 17:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 18:14 [PATCH net-next v6 0/4] add PF-VF mailbox support Shinas Rasheed
2023-12-15 18:14 ` [PATCH net-next v6 1/4] octeon_ep: add PF-VF mailbox communication Shinas Rasheed
2023-12-16 17:48 ` Simon Horman
2023-12-15 18:14 ` [PATCH net-next v6 2/4] octeon_ep: PF-VF mailbox version support Shinas Rasheed
2023-12-16 17:48 ` Simon Horman
2023-12-15 18:14 ` [PATCH net-next v6 3/4] octeon_ep: control net framework to support VF offloads Shinas Rasheed
2023-12-16 17:48 ` Simon Horman [this message]
2023-12-15 18:14 ` [PATCH net-next v6 4/4] octeon_ep: support firmware notifications for VFs Shinas Rasheed
2023-12-16 17:49 ` Simon Horman
2023-12-19 11:20 ` [PATCH net-next v6 0/4] add PF-VF mailbox support 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=20231216174850.GR6288@kernel.org \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=egallen@redhat.com \
--cc=hgani@marvell.com \
--cc=kheib@redhat.com \
--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=sedara@marvell.com \
--cc=shenjian15@huawei.com \
--cc=srasheed@marvell.com \
--cc=vburru@marvell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.