From: Thomas Monjalon <thomas@monjalon.net>
To: David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org, stable@dpdk.org,
Tomasz Kantecki <tomasz.kantecki@intel.com>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Natanael Copa <ncopa@alpinelinux.org>
Subject: Re: [PATCH] examples/l2fwd-cat: fix external build
Date: Thu, 22 Jun 2023 15:55:59 +0200 [thread overview]
Message-ID: <2084962.bB369e8A3T@thomas> (raw)
In-Reply-To: <20230622135021.831889-1-thomas@monjalon.net>
22/06/2023 15:48, Thomas Monjalon:
> From: David Marchand <david.marchand@redhat.com>
>
> cpu_set_t definition requires _GNU_SOURCE.
>
> Fixes: e0473c6d5b18 ("eal: fix build with musl")
> Cc: stable@dpdk.org
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
> ---
> This patch was missing in the patchset to make all examples compile.
> It will be merged with others from:
> "Test examples compilation externally"
Tested-by: Thomas Monjalon <thomas@monjalon.net>
and applied.
next prev parent reply other threads:[~2023-06-22 13:56 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 8:17 [PATCH 0/4] Test examples compilation externally David Marchand
2023-06-13 8:17 ` [PATCH 1/4] examples/fips_validation: fix external build David Marchand
2023-06-13 15:05 ` [EXT] " Gowrishankar Muthukrishnan
2023-06-13 8:17 ` [PATCH 2/4] examples/server_node_efd: simplify build configuration David Marchand
2023-06-13 11:05 ` David Marchand
2023-06-13 8:17 ` [PATCH 3/4] devtools: build all examples externally David Marchand
2023-06-13 9:20 ` Bruce Richardson
2023-06-13 9:29 ` David Marchand
2023-06-13 9:23 ` Bruce Richardson
2023-06-13 8:17 ` [PATCH 4/4] ci: build " David Marchand
2023-06-13 9:21 ` [PATCH 0/4] Test examples compilation externally Bruce Richardson
2023-06-13 14:06 ` [PATCH v2 " David Marchand
2023-06-13 14:06 ` [PATCH v2 1/4] examples/fips_validation: fix external build David Marchand
2023-06-13 14:06 ` [PATCH v2 2/4] examples/server_node_efd: simplify build configuration David Marchand
2023-06-20 9:42 ` Thomas Monjalon
2023-06-20 9:58 ` David Marchand
2023-06-13 14:06 ` [PATCH v2 3/4] devtools: build all examples externally David Marchand
2023-06-20 9:45 ` Thomas Monjalon
2023-06-20 9:52 ` David Marchand
2023-06-13 14:06 ` [PATCH v2 4/4] ci: build " David Marchand
2023-06-16 13:14 ` Aaron Conole
2023-06-20 14:07 ` [PATCH v3 0/4] Test examples compilation externally David Marchand
2023-06-20 14:07 ` [PATCH v3 1/4] examples/fips_validation: fix external build David Marchand
2023-06-21 6:23 ` David Marchand
2023-06-20 14:07 ` [PATCH v3 2/4] examples/server_node_efd: simplify build configuration David Marchand
2023-06-20 14:07 ` [PATCH v3 3/4] devtools: build all examples externally David Marchand
2023-06-20 14:07 ` [PATCH v3 4/4] ci: build " David Marchand
2023-06-22 13:48 ` [PATCH] examples/l2fwd-cat: fix external build Thomas Monjalon
2023-06-22 13:55 ` Thomas Monjalon [this message]
2023-06-22 13:54 ` [PATCH v3 0/4] Test examples compilation externally Thomas Monjalon
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=2084962.bB369e8A3T@thomas \
--to=thomas@monjalon.net \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ncopa@alpinelinux.org \
--cc=stable@dpdk.org \
--cc=tomasz.kantecki@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).