From: Thomas Monjalon <thomas@monjalon.net>
To: Jie Wang <jie1x.wang@intel.com>,
dev@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>
Cc: andrew.rybchenko@oktetlabs.ru, xiaoyun.li@intel.com,
stevex.yang@intel.com, stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH v9 1/3] ethdev: add an API to get device configuration info
Date: Mon, 04 Oct 2021 13:26:09 +0200 [thread overview]
Message-ID: <3623843.L9BjcLBxff@thomas> (raw)
In-Reply-To: <1772aad6-538a-eebc-c584-00a6d4db6c77@intel.com>
04/10/2021 13:22, Ferruh Yigit:
> On 9/26/2021 10:20 AM, Jie Wang wrote:
> > This patch adds a new API "rte_eth_dev_conf_info_get()" to help users get
> > device configuration info.
> >
> > Cc: stable@dpdk.org
> >
>
> Since this is a new API, I think we can request it to be backported.
We cannot.
> > Signed-off-by: Jie Wang <jie1x.wang@intel.com>
>
> <...>
>
> > @@ -247,6 +247,9 @@ EXPERIMENTAL {
> > rte_mtr_meter_policy_delete;
> > rte_mtr_meter_policy_update;
> > rte_mtr_meter_policy_validate;
> > +
> > + # added in 21.11
> > + rte_eth_dev_conf_info_get;
>
> Not sure about the 'info' part in the API, what about 'rte_eth_dev_conf_get()'?
+1
next prev parent reply other threads:[~2021-10-04 11:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210827081740.365037-1-jie1x.wang@intel.com>
[not found] ` <20210926092055.495322-1-jie1x.wang@intel.com>
2021-09-26 9:20 ` Jie Wang
2021-10-04 11:22 ` Ferruh Yigit
2021-10-04 11:26 ` Thomas Monjalon [this message]
2021-10-04 11:35 ` Ferruh Yigit
2021-09-26 9:20 ` [dpdk-stable] [PATCH v9 2/3] doc: update release notes for new API Jie Wang
2021-10-04 11:22 ` Ferruh Yigit
2021-10-04 11:26 ` Thomas Monjalon
2021-09-26 9:20 ` [dpdk-stable] [PATCH v9 3/3] app/testpmd: fix testpmd doesn't show RSS hash offload Jie Wang
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=3623843.L9BjcLBxff@thomas \
--to=thomas@monjalon.net \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jie1x.wang@intel.com \
--cc=stable@dpdk.org \
--cc=stevex.yang@intel.com \
--cc=xiaoyun.li@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).