DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: dev@dpdk.org, Ferruh Yigit <ferruh.yigit@amd.com>
Subject: Re: [PATCH] doc: fix an alignment issue in bnxt NIC documentation
Date: Mon, 6 Feb 2023 09:30:52 -0800	[thread overview]
Message-ID: <CACZ4nhujN89m+_Ji6ohNHy7g_1A506tu9H-aApFNrbBuwq-kFA@mail.gmail.com> (raw)
In-Reply-To: <20230202181341.62506-1-ajit.khaparde@broadcom.com>

[-- Attachment #1: Type: text/plain, Size: 1060 bytes --]

On Thu, Feb 2, 2023 at 10:13 AM Ajit Khaparde
<ajit.khaparde@broadcom.com> wrote:
>
> The supported firmware version information was not aligned correctly.
> This patch fixes it.
>
> Fixes: b845c295cd13 ("doc: update Broadcom bnxt guide")
> Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
Patch applied dpdk-next-net-brcm. Thanks

> ---
>  doc/guides/nics/bnxt.rst | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/doc/guides/nics/bnxt.rst b/doc/guides/nics/bnxt.rst
> index 293eab8787..0b09b0c50a 100644
> --- a/doc/guides/nics/bnxt.rst
> +++ b/doc/guides/nics/bnxt.rst
> @@ -912,6 +912,7 @@ Shown below are Ethernet Network Adapters and their supported firmware versions
>  * ``BCM57500 NetXtreme-E\ |reg| Family`` ... Firmware 219.0.0 or later
>
>  Shown below are DPDK LTS releases and their supported firmware versions:
> +
>  * ``DPDK Release 19.11`` ... Firmware 219.0.103 or later
>  * ``DPDK Release 20.11`` ... Firmware 219.0.103 or later
>  * ``DPDK Release 21.11`` ... Firmware 221.0.101 or later
> --
> 2.37.1 (Apple Git-137.1)
>

[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4218 bytes --]

      reply	other threads:[~2023-02-06 17:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-02 18:13 Ajit Khaparde
2023-02-06 17:30 ` 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=CACZ4nhujN89m+_Ji6ohNHy7g_1A506tu9H-aApFNrbBuwq-kFA@mail.gmail.com \
    --to=ajit.khaparde@broadcom.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@amd.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).