From: Thomas Monjalon <thomas@monjalon.net>
To: Hemant Agrawal <hemant.agrawal@nxp.com>
Cc: dev@dpdk.org, stable@dpdk.org, stephen@networkplumber.org,
longli@microsoft.com
Subject: Re: [dpdk-stable] [PATCH] ethdev: add missing buses in dev iterator
Date: Thu, 29 Apr 2021 09:56:26 +0200 [thread overview]
Message-ID: <2996064.aO63oZZxRA@thomas> (raw)
In-Reply-To: <20210429055548.12964-1-hemant.agrawal@nxp.com>
29/04/2021 07:55, Hemant Agrawal:
> This patch fixes issue with OVS 2.15 not working on
> DPAA/FSLMC based platform due to missing support for
> these busses in dev_iterate.
> This patch adds dpaa_bus and fslmc to dev iterator
> for bus arguments.
I think we should add VMBus as well.
next prev parent reply other threads:[~2021-04-29 7:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 5:55 Hemant Agrawal
2021-04-29 7:56 ` Thomas Monjalon [this message]
2021-04-29 8:01 ` [dpdk-stable] [dpdk-dev] " Hemant Agrawal
2021-05-04 12:49 ` Ferruh Yigit
2021-05-04 15:50 ` Thomas Monjalon
2021-05-04 16:34 ` Ferruh Yigit
2021-05-05 14:39 ` Xu, Rosen
2021-04-29 13:53 ` Morten Brørup
2021-04-29 13:57 ` Hemant Agrawal
2021-04-29 14:01 ` Morten Brørup
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=2996064.aO63oZZxRA@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=longli@microsoft.com \
--cc=stable@dpdk.org \
--cc=stephen@networkplumber.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).