patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Lance Richardson <lance.richardson@broadcom.com>
Cc: Somnath Kotur <somnath.kotur@broadcom.com>,
	dpdk-dev <dev@dpdk.org>,  dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH] net/bnxt: fix PCI per-function stats
Date: Tue, 22 Sep 2020 16:54:33 -0700	[thread overview]
Message-ID: <CACZ4nhvMWp-OsnWJcGzyTngtth9G5219i0Jhs+w7KU1j3wdZBA@mail.gmail.com> (raw)
In-Reply-To: <20200921174549.269401-1-lance.richardson@broadcom.com>

On Mon, Sep 21, 2020 at 10:45 AM Lance Richardson <
lance.richardson@broadcom.com> wrote:

> Fix to use correct value offset for PCI function stats.
>
> Fixes: 5f9374de2a3a ("net/bnxt: add PCI function stats to extended stats")
>
> Reviewed-by: Ajit Kumar Khaparde <ajit.khaparde@broadcom.com>
> Cc: stable@dpdk.org
> Cc: ajit.khaparde@broadcom.com
>
> Signed-off-by: Lance Richardson <lance.richardson@broadcom.com>
>
Applied to dpdk-next-net-brcm. Thanks


> ---
>  drivers/net/bnxt/bnxt_stats.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/bnxt/bnxt_stats.c b/drivers/net/bnxt/bnxt_stats.c
> index 8df6922f52..cb7756d54f 100644
> --- a/drivers/net/bnxt/bnxt_stats.c
> +++ b/drivers/net/bnxt/bnxt_stats.c
> @@ -643,7 +643,8 @@ int bnxt_dev_xstats_get_op(struct rte_eth_dev *eth_dev,
>         for (i = 0; i < RTE_DIM(bnxt_func_stats_strings); i++) {
>                 xstats[count].id = count;
>                 xstats[count].value =
> -               rte_le_to_cpu_64(((uint64_t *)&func_qstats)[i]);
> +                       rte_le_to_cpu_64(*(uint64_t *)((char
> *)&func_qstats +
> +
> bnxt_func_stats_strings[i].offset));
>                 count++;
>         }
>
> --
> 2.25.1
>
>

      reply	other threads:[~2020-09-22 23:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-21 17:45 Lance Richardson
2020-09-22 23:54 ` 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=CACZ4nhvMWp-OsnWJcGzyTngtth9G5219i0Jhs+w7KU1j3wdZBA@mail.gmail.com \
    --to=ajit.khaparde@broadcom.com \
    --cc=dev@dpdk.org \
    --cc=lance.richardson@broadcom.com \
    --cc=somnath.kotur@broadcom.com \
    --cc=stable@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).