From: "Havlík Martin" <xhavli56@stud.fit.vutbr.cz>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Thomas Monjalon <thomas@monjalon.net>, Ori Kam <orika@nvidia.com>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
dev@dpdk.org, "Min Hu (Connor)" <humin29@huawei.com>,
Matan Azrad <matan@nvidia.com>, Chas3 <chas3@att.com>,
Slava Ovsiienko <viacheslavo@nvidia.com>,
Jan Viktorin <viktorin@cesnet.cz>
Subject: Re: [dpdk-dev] [PATCH 3/3] net/bonding: start ethdev prior to setting 8023ad flow
Date: Sat, 25 Sep 2021 08:15:43 +0200 [thread overview]
Message-ID: <d401ac9a2f405cac4a01d3c411a0d34a@stud.fit.vutbr.cz> (raw)
Hello,
as Jan stated before, I have started the discussion afresh:
[PATCH 0/4] doc: update RTE flow rule and bonding related info
https://www.mail-archive.com/dev@dpdk.org/msg214517.html
Now, [Patch 1] didn't really move anywhere, but it connects to [Patch
2], where a device capability was agreed to be a sensible solution. I,
at the time, didn't think myself knowledgeable enough to add it, however
since no one took the initiative, I'll have a look and see if I can
manage it (any help appreciated).
[Patch 3] got acked and [Patch 4] informing on a bug didn't gather any
attention, it seems.
I would be glad to resolve this patchset, even if just some changes,
that were agreed on, will be applied.
Martin
[Patch 1] https://www.mail-archive.com/dev@dpdk.org/msg214518.html
[Patch 2] https://www.mail-archive.com/dev@dpdk.org/msg214519.html
[Patch 3] https://www.mail-archive.com/dev@dpdk.org/msg214520.html
[Patch 4] https://www.mail-archive.com/dev@dpdk.org/msg214521.html
next reply other threads:[~2021-09-25 6:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-25 6:15 Havlík Martin [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-06-22 9:25 [dpdk-dev] [PATCH 0/3] net/bonding: make dedicated queues work with mlx5 Martin Havlik
2021-06-22 9:25 ` [dpdk-dev] [PATCH 3/3] net/bonding: start ethdev prior to setting 8023ad flow Martin Havlik
2021-06-23 7:04 ` Min Hu (Connor)
2021-06-24 11:57 ` Havlík Martin
2021-07-04 15:18 ` Matan Azrad
2021-07-07 15:54 ` Jan Viktorin
2021-07-11 8:49 ` Ori Kam
2021-07-11 21:45 ` Jan Viktorin
2021-07-12 13:07 ` Ori Kam
2021-07-13 8:18 ` Havlík Martin
2021-07-13 9:26 ` Andrew Rybchenko
2021-07-13 11:06 ` Jan Viktorin
2021-07-13 17:17 ` Ori Kam
2021-07-14 15:00 ` Jan Viktorin
2021-07-15 13:58 ` Thomas Monjalon
2021-08-24 13:18 ` Ferruh Yigit
2021-08-26 10:15 ` Jan Viktorin
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=d401ac9a2f405cac4a01d3c411a0d34a@stud.fit.vutbr.cz \
--to=xhavli56@stud.fit.vutbr.cz \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=chas3@att.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=humin29@huawei.com \
--cc=matan@nvidia.com \
--cc=orika@nvidia.com \
--cc=thomas@monjalon.net \
--cc=viacheslavo@nvidia.com \
--cc=viktorin@cesnet.cz \
/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).