From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: dpdk-dev <dev@dpdk.org>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>,
JP Lee <jongpil.lee@broadcom.com>,
Kovacevic Marko <marko.kovacevic@intel.com>
Subject: Re: [dpdk-dev] [PATCH v5] doc: update bnxt guide
Date: Wed, 20 May 2020 18:16:48 -0700 [thread overview]
Message-ID: <CACZ4nhsm9HRejHbJmJfDHTkF-5sD5KCzrU9TmMYi61xH4w7V+A@mail.gmail.com> (raw)
In-Reply-To: <20200520200353.33174-1-ajit.khaparde@broadcom.com>
On Wed, May 20, 2020 at 1:04 PM Ajit Khaparde <ajit.khaparde@broadcom.com>
wrote:
> - Update list of supported adapters.
> - Update list of supported features.
> - Add some details to describe the features.
> - Remove obsolete limitations.
> - Fix and update links.
>
> Signed-off-by: JP Lee <jongpil.lee@broadcom.com>
> Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
> Acked-by: Kovacevic Marko <marko.kovacevic@intel.com>
> ---
> v1->v2: Some lines were too long in v1. Made then shorter. Checked for
> typos.
> v2->v3: Removed list of extended stats.
> v3->v4: Removed an irrelevant line.
> v4->v5: Shorten the long lines further.
>
Applied to dpdk-next-net-brcm. Thanks
>
>
next prev parent reply other threads:[~2020-05-21 1:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 22:03 [dpdk-dev] [PATCH] " Ajit Khaparde
2020-05-05 16:58 ` Ajit Khaparde
2020-05-06 8:57 ` Ferruh Yigit
2020-05-06 16:09 ` Ajit Khaparde
2020-05-13 9:08 ` Ferruh Yigit
2020-05-14 10:39 ` Kovacevic, Marko
2020-05-15 21:56 ` [dpdk-dev] [PATCH v2] " Ajit Khaparde
2020-05-18 9:34 ` Ferruh Yigit
2020-05-18 17:38 ` [dpdk-dev] [PATCH v3] " Ajit Khaparde
2020-05-18 17:58 ` [dpdk-dev] [PATCH v4] " Ajit Khaparde
2020-05-18 22:04 ` Ajit Khaparde
2020-05-19 8:15 ` Ferruh Yigit
2020-05-20 20:03 ` [dpdk-dev] [PATCH v5] " Ajit Khaparde
2020-05-21 1:16 ` Ajit Khaparde [this message]
2020-05-21 13:51 ` Ferruh Yigit
2020-05-23 3:53 ` 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=CACZ4nhsm9HRejHbJmJfDHTkF-5sD5KCzrU9TmMYi61xH4w7V+A@mail.gmail.com \
--to=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jongpil.lee@broadcom.com \
--cc=marko.kovacevic@intel.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).