From: Tyler Retzlaff <roretzla@linux.microsoft.com>
To: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"stephen@networkplumber.org" <stephen@networkplumber.org>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [PATCH] test/bpf: skip test if libpcap is unavailable
Date: Mon, 21 Mar 2022 23:11:04 -0700 [thread overview]
Message-ID: <20220322061104.GA21568@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net> (raw)
In-Reply-To: <BY5PR11MB4482EBC4C77612DB76DB6D919A169@BY5PR11MB4482.namprd11.prod.outlook.com>
On Mon, Mar 21, 2022 at 02:42:39PM +0000, Ananyev, Konstantin wrote:
>
> >
> > Signed-off-by: Tyler Retzlaff <roretzla@linux.microsoft.com>
> > ---
> > app/test/test_bpf.c | 14 ++++++++++++--
> > 1 file changed, 12 insertions(+), 2 deletions(-)
> >
> > diff --git a/app/test/test_bpf.c b/app/test/test_bpf.c
> > index 805cce6..de1fa87 100644
> > --- a/app/test/test_bpf.c
> > +++ b/app/test/test_bpf.c
> > @@ -3264,7 +3264,16 @@ struct bpf_test {
> >
> > REGISTER_TEST_COMMAND(bpf_autotest, test_bpf);
> >
> > -#ifdef RTE_HAS_LIBPCAP
> > +#ifndef RTE_HAS_LIBPCAP
> > +
> > +static int
> > +test_bpf_convert(void)
> > +{
> > + printf("BPF not supported, skipping test\n");
>
> One nit: the message above seems a bit misleading...
> Probably "LIBPCAP is not supported" or so?
> With that fixed:
> Acked-by: Konstantin Ananyev <konstantin.ananyev@intel.com>
yeah, i cut and paste the other skip function. i agree i'll tweak the
message to talk about libpcap.
>
>
> > + return TEST_SKIPPED;
> > +}
> > +
> > +#else
> > #include <pcap/pcap.h>
> >
> > static void
> > @@ -3462,5 +3471,6 @@ struct bpf_test {
> > return rc;
> > }
> >
> > -REGISTER_TEST_COMMAND(bpf_convert_autotest, test_bpf_convert);
> > #endif /* RTE_HAS_LIBPCAP */
> > +
> > +REGISTER_TEST_COMMAND(bpf_convert_autotest, test_bpf_convert);
> > --
> > 1.8.3.1
next prev parent reply other threads:[~2022-03-22 6:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 13:13 Tyler Retzlaff
2022-03-21 14:42 ` Ananyev, Konstantin
2022-03-22 6:11 ` Tyler Retzlaff [this message]
2022-03-21 16:15 ` Stephen Hemminger
2022-03-22 7:12 ` [PATCH v2] " Tyler Retzlaff
2022-03-22 11:50 ` Ananyev, Konstantin
2022-04-26 6:38 ` Tyler Retzlaff
2022-04-26 7:41 ` David Marchand
2022-04-26 7:47 ` Tyler Retzlaff
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=20220322061104.GA21568@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net \
--to=roretzla@linux.microsoft.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=konstantin.ananyev@intel.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).