From: Thomas Monjalon <thomas.monjalon-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
To: "Doherty,
Declan" <declan.doherty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org
Subject: Re: [PATCH 0/2] link bonding unit test fix
Date: Fri, 01 Aug 2014 17:21:06 +0200 [thread overview]
Message-ID: <1648009.TlCDtWYl7N@xps13> (raw)
In-Reply-To: <E115CCD9D858EF4F90C690B0DCB4D89721C35052-kPTMFJFq+rELt2AQoY/u9bfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-07-22 10:57, De Lara Guarch, Pablo:
> From: dev [mailto:dev-bounces-VfR2kkLFssw@public.gmane.org] On Behalf Of Declan Doherty
> >
> > fix for link bonding unit tests which are failing due to change introduced in
> > rte_eth_dev_configure which now explicitly checks in pmd supports link status
> > chnage interrupts.
> >
> > Also adds some common test macros to the test application for unit testing
> >
> > Declan Doherty (2):
> > test app:
> > bond: unit test suite fix
>
> Acked-by: Pablo de Lara <pablo.de.lara.guarch-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Applied for version 1.7.1.
> I would add that it may be a good idea to implement some of the changes made
> in this unit test in other ones (use the new macros).
Yes, it's cleaner with macros.
It would be a good idea to translate existing unit tests like Declan did.
Thanks
--
Thomas
prev parent reply other threads:[~2014-08-01 15:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-21 14:52 [PATCH 0/2] link bonding unit test fix Declan Doherty
[not found] ` <1405954337-28488-1-git-send-email-declan.doherty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2014-07-21 14:52 ` [PATCH 1/2] test app: Declan Doherty
2014-07-21 14:52 ` [PATCH 2/2] bond: unit test suite fix Declan Doherty
2014-07-22 10:57 ` [PATCH 0/2] link bonding unit test fix De Lara Guarch, Pablo
[not found] ` <E115CCD9D858EF4F90C690B0DCB4D89721C35052-kPTMFJFq+rELt2AQoY/u9bfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-08-01 15:21 ` Thomas Monjalon [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=1648009.TlCDtWYl7N@xps13 \
--to=thomas.monjalon-pdr9zngts4eavxtiumwx3w@public.gmane.org \
--cc=declan.doherty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.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).