From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ajit Khaparde <ajit.khaparde@broadcom.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 1/2] doc: update bnxt feature list
Date: Wed, 20 Nov 2019 09:41:59 +0000 [thread overview]
Message-ID: <4355c451-3cee-ac77-0655-e9c92b111330@intel.com> (raw)
In-Reply-To: <20191120042907.1030-1-ajit.khaparde@broadcom.com>
On 11/20/2019 4:29 AM, Ajit Khaparde wrote:
> Updating bnxt.ini file.
>
> Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
> ---
> doc/guides/nics/features/bnxt.ini | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/doc/guides/nics/features/bnxt.ini b/doc/guides/nics/features/bnxt.ini
> index 9721dd61d..37a99e336 100644
> --- a/doc/guides/nics/features/bnxt.ini
> +++ b/doc/guides/nics/features/bnxt.ini
> @@ -11,6 +11,7 @@ Rx interrupt = Y
> Queue start/stop = Y
> MTU update = Y
> Jumbo frame = Y
> +Scattered Rx = Y
> LRO = Y
> TSO = Y
> Promiscuous mode = Y
> @@ -37,9 +38,11 @@ Rx descriptor status = Y
> Tx descriptor status = Y
> Basic stats = Y
> Extended stats = Y
> +Stats per queue = Y
> FW version = Y
> EEPROM dump = Y
> LED = Y
> +Multiprocess aware = Y
> Linux UIO = Y
> Linux VFIO = Y
> ARMv8 = Y
>
Are these features added in this release or adding the missed features? If
adding missed features can you please add the fixes tags for backtrace?
And if new features can you please put the commit providing these features for
reference?
Thanks.
next prev parent reply other threads:[~2019-11-20 9:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-20 4:29 Ajit Khaparde
2019-11-20 4:29 ` [dpdk-dev] [PATCH 2/2] net/bnxt: fix check for null spec and mask Ajit Khaparde
2019-11-20 5:01 ` Ajit Khaparde
2019-11-20 5:02 ` [dpdk-dev] [PATCH 1/2] doc: update bnxt feature list Ajit Khaparde
2019-11-20 9:41 ` Ferruh Yigit [this message]
2019-11-20 16:55 ` Ajit Khaparde
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=4355c451-3cee-ac77-0655-e9c92b111330@intel.com \
--to=ferruh.yigit@intel.com \
--cc=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.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).