From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: dev@dpdk.org
Cc: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
Subject: Re: [PATCH v2] doc: update broadcom documentation
Date: Wed, 9 Nov 2022 21:00:21 -0800 [thread overview]
Message-ID: <CACZ4nhsAA4Hg6F5wsf7mFVu6LZrAyqywb6CFbMq7Zqb=4XU2Lw@mail.gmail.com> (raw)
In-Reply-To: <20221110045503.85690-1-ajit.khaparde@broadcom.com>
[-- Attachment #1: Type: text/plain, Size: 507 bytes --]
On Wed, Nov 9, 2022 at 8:55 PM Ajit Khaparde <ajit.khaparde@broadcom.com> wrote:
>
> Update Broadcom NIC documentation.
>
> Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
> Reviewed-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
>
> ---
> v1->v2:
> Updated commit message & incorrect information in the documentation.
> ---
> doc/guides/nics/bnxt.rst | 477 +++++++++++++++++++++++----------------
> 1 file changed, 283 insertions(+), 194 deletions(-)
>
Patch applied to dpdk-next-net-brcm
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4218 bytes --]
prev parent reply other threads:[~2022-11-10 5:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-10 4:55 Ajit Khaparde
2022-11-10 5:00 ` Ajit Khaparde [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='CACZ4nhsAA4Hg6F5wsf7mFVu6LZrAyqywb6CFbMq7Zqb=4XU2Lw@mail.gmail.com' \
--to=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=kalesh-anakkur.purayil@broadcom.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).