DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: Sathesh B Edara <sedara@marvell.com>
Cc: Satananda Burla <sburla@marvell.com>,
	Jerin Jacob <jerinj@marvell.com>,
	 Nalla Pradeep <pnalla@marvell.com>,
	Radha Mohan Chintakuntla <radhac@marvell.com>,
	 Veerasenareddy Burru <vburru@marvell.com>,
	dpdk-dev <dev@dpdk.org>
Subject: Re: [PATCH] net/octeontx_ep: updated ethdev ops
Date: Wed, 15 Jun 2022 22:40:19 +0530	[thread overview]
Message-ID: <CALBAE1NTaS2HQC4eoaORoRK=hgeSuEP-ukyv4BXxJZjV92Z04Q@mail.gmail.com> (raw)
In-Reply-To: <20220609151953.83802-1-sedara@marvell.com>

On Thu, Jun 9, 2022 at 8:50 PM Sathesh B Edara <sedara@marvell.com> wrote:
>
> Updated ethdev ops support for link_update(),
> stats_get() and stats_reset()

a) Split as two patches (Suggested heading)
1) net/octeontx_ep: support basic stats

2) net/octeontx_ep: support link status

b) Update doc/guides/nics/features/octeontx_ep.ini
See doc/guides/nics/features.rst

>
> Signed-off-by: Sathesh B Edara <sedara@marvell.com>

Since this is your first path, you may consider changing to  "Sathesh
Edara <sedara@marvell.com>"

> +static int
> +otx_ep_link_update(struct rte_eth_dev *eth_dev, int wait_to_complete)
> +{
> +       struct rte_eth_link link;
> +
> +       RTE_SET_USED(wait_to_complete);
> +
> +       if (!eth_dev->data->dev_started)
> +               return 0;
> +
> +       link.link_speed = RTE_ETH_SPEED_NUM_10G;

Isn't this RTE_ETH_SPEED_NUM_NONE? as its speed is "Not defined"

>

      reply	other threads:[~2022-06-15 17:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-09 15:19 Sathesh B Edara
2022-06-15 17:10 ` Jerin Jacob [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='CALBAE1NTaS2HQC4eoaORoRK=hgeSuEP-ukyv4BXxJZjV92Z04Q@mail.gmail.com' \
    --to=jerinjacobk@gmail.com \
    --cc=dev@dpdk.org \
    --cc=jerinj@marvell.com \
    --cc=pnalla@marvell.com \
    --cc=radhac@marvell.com \
    --cc=sburla@marvell.com \
    --cc=sedara@marvell.com \
    --cc=vburru@marvell.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).