From: "Xu, HailinX" <hailinx.xu@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
Chas Williams <chas3@att.com>,
"Min Hu (Connor)" <humin29@huawei.com>,
"Richardson, Bruce" <bruce.richardson@intel.com>,
Chengwen Feng <fengchengwen@huawei.com>
Subject: RE: [PATCH v2] test/bonding: fix active backup rx test
Date: Wed, 22 Jan 2025 06:09:48 +0000 [thread overview]
Message-ID: <MW4PR11MB591283D59B782407183530819FE12@MW4PR11MB5912.namprd11.prod.outlook.com> (raw)
In-Reply-To: <20241213171713.13266-2-stephen@networkplumber.org>
> -----Original Message-----
> From: Stephen Hemminger <stephen@networkplumber.org>
> Sent: Saturday, December 14, 2024 1:17 AM
> To: dev@dpdk.org
> Cc: Stephen Hemminger <stephen@networkplumber.org>; stable@dpdk.org;
> Chas Williams <chas3@att.com>; Min Hu (Connor) <humin29@huawei.com>;
> Richardson, Bruce <bruce.richardson@intel.com>; Chengwen Feng
> <fengchengwen@huawei.com>
> Subject: [PATCH v2] test/bonding: fix active backup rx test
>
> The test had incorrect assumptions about how active backup should work.
> When in active backup mode, the secondary (not primary) ports should be
> ignored. The test was always broken since initially written but earlier bug was
> masking the part of the test which tested non-primary ports.
>
> Bugzilla ID: 1589
> Fixes: 112ce3917674 ("test/bonding: fix loop on members")
> Cc: stable@dpdk.org
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> ---
>
Tested-by: Hailin Xu <hailinx.xu@intel.com>
prev parent reply other threads:[~2025-01-22 6:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 1:51 [PATCH] " Stephen Hemminger
2024-12-13 6:57 ` lihuisong (C)
2024-12-13 16:56 ` Stephen Hemminger
2024-12-16 1:50 ` lihuisong (C)
2024-12-13 17:17 ` [PATCH v2] " Stephen Hemminger
2024-12-16 1:53 ` lihuisong (C)
2025-01-22 6:09 ` Xu, HailinX [this message]
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=MW4PR11MB591283D59B782407183530819FE12@MW4PR11MB5912.namprd11.prod.outlook.com \
--to=hailinx.xu@intel.com \
--cc=bruce.richardson@intel.com \
--cc=chas3@att.com \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=humin29@huawei.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).