From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 7E68DA0C4C; Sat, 25 Sep 2021 08:15:50 +0200 (CEST) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id EEA694003D; Sat, 25 Sep 2021 08:15:49 +0200 (CEST) Received: from eva.fit.vutbr.cz (eva.fit.vutbr.cz [147.229.176.14]) by mails.dpdk.org (Postfix) with ESMTP id D82F54003C for ; Sat, 25 Sep 2021 08:15:48 +0200 (CEST) Received: from roundcube.fit.vutbr.cz (spytihnev.fit.vutbr.cz [IPv6:2001:67c:1220:809:0:0:93e5:9e2]) (authenticated bits=0) by eva.fit.vutbr.cz (8.16.1/8.16.1) with ESMTPSA id 18P6FhsO070102 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sat, 25 Sep 2021 08:15:43 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=stud.fit.vutbr.cz; s=studfit; t=1632550544; bh=KRosfH5SwHkkvVOXwH7YMQX809IUr2IlRNaT/Rp3E5g=; h=Date:From:To:Cc:Subject; b=t90OEpMO4sp+BVKXHrGunEWBi9pYlPwEvzekncQPEKULJTkaDgjJUtllcySLYERQw KjXBw0MGp3d8TOcnDKXADop1HMzgiNjkeO2duTHqZn33440M7L3Unl+8mwFEP09dyU 0s5q6vkMZFb03icR2F4VNWACN+S4GlFhBnDCYtbw= MIME-Version: 1.0 Date: Sat, 25 Sep 2021 08:15:43 +0200 From: =?UTF-8?Q?Havl=C3=ADk_Martin?= To: Ferruh Yigit Cc: Thomas Monjalon , Ori Kam , Andrew Rybchenko , dev@dpdk.org, "Min Hu (Connor)" , Matan Azrad , Chas3 , Slava Ovsiienko , Jan Viktorin User-Agent: Roundcube Webmail Message-ID: X-Sender: xhavli56@stud.fit.vutbr.cz Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH 3/3] net/bonding: start ethdev prior to setting 8023ad flow X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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