From: Aaron Conole <aconole@redhat.com>
To: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
Cc: dev@dpdk.org, thomas@monjalon.net, david.marchand@redhat.com
Subject: Re: [dpdk-dev] [PATCH 2/2] test/rib: speed up rib6 autotests
Date: Thu, 07 Nov 2019 10:22:07 -0500 [thread overview]
Message-ID: <f7t36ezd84g.fsf@dhcp-25.97.bos.redhat.com> (raw)
In-Reply-To: <c24459bfc7c06551ab8432c01c7cbe6febae72bc.1573042633.git.vladimir.medvedkin@intel.com> (Vladimir Medvedkin's message of "Wed, 6 Nov 2019 12:21:47 +0000")
Vladimir Medvedkin <vladimir.medvedkin@intel.com> writes:
> Split slow part of rib6_autotest into rib6_slow_autotest
>
> Fixes: abab6d2966dc ("test/rib: add IPv6 autotests")
>
> Signed-off-by: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
> ---
Acked-by: Aaron Conole <aconole@redhat.com>
next prev parent reply other threads:[~2019-11-07 15:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-06 12:21 [dpdk-dev] [PATCH 1/2] test/rib: speed up rib autotests Vladimir Medvedkin
2019-11-06 12:21 ` [dpdk-dev] [PATCH 2/2] test/rib: speed up rib6 autotests Vladimir Medvedkin
2019-11-07 15:22 ` Aaron Conole [this message]
2019-11-07 15:21 ` [dpdk-dev] [PATCH 1/2] test/rib: speed up rib autotests Aaron Conole
2019-11-07 16:42 ` David Marchand
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=f7t36ezd84g.fsf@dhcp-25.97.bos.redhat.com \
--to=aconole@redhat.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
--cc=vladimir.medvedkin@intel.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).