DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Kumara Parameshwaran <kumaraparamesh92@gmail.com>, <dev@dpdk.org>
Cc: Kumara Parameshwaran <kparameshwar@vmware.com>, <stable@dpdk.org>,
	"Luca Boccassi" <bluca@debian.org>,
	Kevin Traynor <ktraynor@redhat.com>,
	"Christian Ehrhardt" <christian.ehrhardt@canonical.com>
Subject: Re: [PATCH v3 1/2] ethdev: define a function to get eth dev structure
Date: Tue, 1 Feb 2022 16:56:42 +0000	[thread overview]
Message-ID: <2edd4240-648d-4b1a-e814-9e3150f69650@intel.com> (raw)
In-Reply-To: <20220131143234.17945-1-kumaraparamesh92@gmail.com>

On 1/31/2022 2:32 PM, Kumara Parameshwaran wrote:
> From: Kumara Parameshwaran <kparameshwar@vmware.com>
> 
> The PMDs would need a function to access the rte_eth_devices
> global array
> 
> Cc: stable@dpdk.org
> 

Not sure if this patch is suitable for backport, since it introduces
new internal API.
But since API is internal, perhaps it is OK to get it, specially because
it is required for next patch that is a fix. Keeping the tag and leaving
the decision to LTS maintainers.

> Signed-off-by: Kumara Parameshwaran <kparameshwar@vmware.com>

Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>

  parent reply	other threads:[~2022-02-01 16:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-21  4:29 [PATCH] net/tap: Bug fix to populate fds in secondary process Kumara Parameshwaran
2022-01-24  9:47 ` Ferruh Yigit
2022-01-24 12:12 ` [PATCH v2] net/tap: " Kumara Parameshwaran
2022-01-24 12:35   ` Ferruh Yigit
2022-01-24 12:48     ` Kumara Parameshwaran
2022-01-24 12:54     ` kumaraparameshwaran rathinavel
2022-01-24 13:05       ` Ferruh Yigit
2022-01-28  9:55     ` kumaraparameshwaran rathinavel
2022-01-28 12:55       ` Ferruh Yigit
2022-01-24 12:37 ` Kumara Parameshwaran
2022-01-24 13:06   ` Ferruh Yigit
2022-01-31 14:21 ` [PATCH v3 1/2] ethdev: define a function to get eth dev structure Kumara Parameshwaran
2022-01-31 14:21   ` [PATCH v3 2/2] net/tap: fix to populate fds in secondary process Kumara Parameshwaran
2022-01-31 14:32 ` [PATCH v3 1/2] ethdev: define a function to get eth dev structure Kumara Parameshwaran
2022-01-31 14:32   ` [PATCH v3 2/2] net/tap: fix to populate fds in secondary process Kumara Parameshwaran
2022-02-01 16:57     ` Ferruh Yigit
2022-02-01 16:56   ` Ferruh Yigit [this message]
2022-02-01 17:12     ` [PATCH v3 1/2] ethdev: define a function to get eth dev structure Ferruh Yigit
2022-02-01 17:15     ` Ferruh Yigit

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=2edd4240-648d-4b1a-e814-9e3150f69650@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=bluca@debian.org \
    --cc=christian.ehrhardt@canonical.com \
    --cc=dev@dpdk.org \
    --cc=kparameshwar@vmware.com \
    --cc=ktraynor@redhat.com \
    --cc=kumaraparamesh92@gmail.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).