From: "Yigit, Ferruh" <ferruh.yigit@linux.intel.com>
To: kkanas@marvell.com, dev@dpdk.org, Chas Williams <chas3@att.com>
Cc: declan.doherty@intel.com
Subject: Re: [dpdk-dev] [PATCH 1/2] test/bonding: fix LSC related test cases
Date: Tue, 8 Oct 2019 19:48:36 +0100 [thread overview]
Message-ID: <59bfdf11-79dc-a50a-afbb-d3a217f60ea2@linux.intel.com> (raw)
In-Reply-To: <20190823081659.27793-1-kkanas@marvell.com>
On 8/23/2019 9:16 AM, kkanas@marvell.com wrote:
> From: Krzysztof Kanas <kkanas@marvell.com>
>
> On rare situation test_link_bonding test case fail due to timespec
> tv_nsec overflow, which causes pthread_cond_timedwait to return EINVAL
> and test to fail.
>
> Fixes: 76d29903f5f5 ("bond: support link status interrupt")
> Cc: declan.doherty@intel.com
>
> Signed-off-by: Krzysztof Kanas <kkanas@marvell.com>
For series,
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>
Series applied to dpdk-next-net/master, thanks.
prev parent reply other threads:[~2019-10-08 18:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 8:16 kkanas
2019-08-23 8:16 ` [dpdk-dev] [PATCH 2/2] test/bonding: fix LSC timeout unit kkanas
2019-10-08 18:48 ` Yigit, Ferruh [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=59bfdf11-79dc-a50a-afbb-d3a217f60ea2@linux.intel.com \
--to=ferruh.yigit@linux.intel.com \
--cc=chas3@att.com \
--cc=declan.doherty@intel.com \
--cc=dev@dpdk.org \
--cc=kkanas@marvell.com \
/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).