From: Jerin Jacob <jerinjacobk@gmail.com>
To: Manish Chopra <manishc@marvell.com>
Cc: Jerin Jacob <jerinj@marvell.com>,
Ferruh Yigit <ferruh.yigit@intel.com>, dpdk-dev <dev@dpdk.org>,
Igor Russkikh <irusskikh@marvell.com>,
Rasesh Mody <rmody@marvell.com>,
GR-Everest-DPDK-Dev <GR-Everest-DPDK-Dev@marvell.com>
Subject: Re: [dpdk-dev] [PATCH 6/6] doc/guides: update qede features list
Date: Fri, 26 Jun 2020 10:25:13 +0530 [thread overview]
Message-ID: <CALBAE1MHUp=XkCRcDpk70g8=c6GUfbsUp-qdf+Fi7PGSyNoyLA@mail.gmail.com> (raw)
In-Reply-To: <20200609194207.24328-7-manishc@marvell.com>
On Wed, Jun 10, 2020 at 1:15 AM Manish Chopra <manishc@marvell.com> wrote:
>
> Add SR-IOV PF entry in supported features
>
> Signed-off-by: Manish Chopra <manishc@marvell.com>
> Signed-off-by: Igor Russkikh <irusskikh@marvell.com>
> Signed-off-by: Rasesh Mody <rmody@marvell.com>
> ---
> doc/guides/nics/features/qede.ini | 1 +
> doc/guides/nics/qede.rst | 2 +-
Please squash to the appropriate patch where this support gets added.
No other comments for this series for my side.
> 2 files changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/doc/guides/nics/features/qede.ini b/doc/guides/nics/features/qede.ini
> index 20c90e626..030f5606b 100644
> --- a/doc/guides/nics/features/qede.ini
> +++ b/doc/guides/nics/features/qede.ini
> @@ -18,6 +18,7 @@ Multicast MAC filter = Y
> RSS hash = Y
> RSS key update = Y
> RSS reta update = Y
> +SR-IOV = Y
> VLAN filter = Y
> Flow control = Y
> Flow API = Y
> diff --git a/doc/guides/nics/qede.rst b/doc/guides/nics/qede.rst
> index 5b2f86895..3306fabaa 100644
> --- a/doc/guides/nics/qede.rst
> +++ b/doc/guides/nics/qede.rst
> @@ -34,7 +34,7 @@ Supported Features
> - VLAN offload - Filtering and stripping
> - N-tuple filter and flow director (limited support)
> - NPAR (NIC Partitioning)
> -- SR-IOV VF
> +- SR-IOV PF and VF
> - GRE Tunneling offload
> - GENEVE Tunneling offload
> - VXLAN Tunneling offload
> --
> 2.17.1
>
prev parent reply other threads:[~2020-06-26 4:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 19:42 [dpdk-dev] [PATCH 0/6] qede: SR-IOV PF driver support Manish Chopra
2020-06-09 19:42 ` [dpdk-dev] [PATCH 1/6] net/qede: define PCI config space specific osals Manish Chopra
2020-06-26 4:53 ` Jerin Jacob
2020-07-09 15:05 ` [dpdk-dev] [EXT] " Manish Chopra
2020-07-09 16:11 ` Jerin Jacob
2020-07-09 22:28 ` Manish Chopra
2020-07-10 5:03 ` Jerin Jacob
2020-06-09 19:42 ` [dpdk-dev] [PATCH 2/6] net/qede: configure VFs on hardware Manish Chopra
2020-06-09 19:42 ` [dpdk-dev] [PATCH 3/6] net/qede: add infrastructure support for VF load Manish Chopra
2020-06-09 19:42 ` [dpdk-dev] [PATCH 4/6] net/qede: initialize VF MAC and link Manish Chopra
2020-06-09 19:42 ` [dpdk-dev] [PATCH 5/6] net/qede: add VF FLR support Manish Chopra
2020-06-09 19:42 ` [dpdk-dev] [PATCH 6/6] doc/guides: update qede features list Manish Chopra
2020-06-26 4:55 ` Jerin Jacob [this message]
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='CALBAE1MHUp=XkCRcDpk70g8=c6GUfbsUp-qdf+Fi7PGSyNoyLA@mail.gmail.com' \
--to=jerinjacobk@gmail.com \
--cc=GR-Everest-DPDK-Dev@marvell.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=irusskikh@marvell.com \
--cc=jerinj@marvell.com \
--cc=manishc@marvell.com \
--cc=rmody@marvell.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;
as well as URLs for NNTP newsgroup(s).