From: David Marchand <david.marchand@redhat.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev <dev@dpdk.org>, Luca Boccassi <bluca@debian.org>
Subject: Re: [PATCH v5] test/bpf_convert: do not require DNS lookup
Date: Tue, 16 Nov 2021 14:31:30 +0100 [thread overview]
Message-ID: <CAJFAV8zz9VGSRaNZq=cvQtWQgn9CnC088wyjrRkR4Kk-E7vv5A@mail.gmail.com> (raw)
In-Reply-To: <20211115232956.118682-1-stephen@networkplumber.org>
On Tue, Nov 16, 2021 at 12:30 AM Stephen Hemminger
<stephen@networkplumber.org> wrote:
>
> These tests were using strings with hostname (dpdk.org) and this makes
> test code do a DNS lookup. In container environment used for OpenSuse
> build, DNS is unavailable. Replace dpdk.org with an IPv4 address
> reserved for documentation (RFC5737) and use IPv6 in one example
> (RFC3849). Actual addresses don't matter for this test which is
> validating that code generated in classic BPF can be successfully
> converted to eBPF.
Fixes: 2eccf6afbea9 ("bpf: add function to convert classic BPF to DPDK BPF")
>
> Signed-off-by: Stephen Hemminger <stephen@networkplumber.org>
> Acked-by: Luca Boccassi <bluca@debian.org>
Applied, thanks.
--
David Marchand
prev parent reply other threads:[~2021-11-16 13:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-09 21:04 [dpdk-dev] [PATCH] " Stephen Hemminger
2021-11-09 22:50 ` Luca Boccassi
2021-11-10 15:22 ` Thomas Monjalon
2021-11-10 16:18 ` [PATCH v2] " Stephen Hemminger
2021-11-14 23:39 ` Luca Boccassi
2021-11-24 18:51 ` Luca Boccassi
2021-11-15 3:41 ` Kalesh Anakkur Purayil
2021-11-15 23:23 ` [PATCH v3] " Stephen Hemminger
2021-11-15 23:29 ` [PATCH v4] " Stephen Hemminger
2021-11-15 23:29 ` [PATCH v5] " Stephen Hemminger
2021-11-16 13:31 ` David Marchand [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='CAJFAV8zz9VGSRaNZq=cvQtWQgn9CnC088wyjrRkR4Kk-E7vv5A@mail.gmail.com' \
--to=david.marchand@redhat.com \
--cc=bluca@debian.org \
--cc=dev@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).