DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: David Marchand <david.marchand@redhat.com>
Cc: dev@dpdk.org, bruce.richardson@intel.com
Subject: Re: [PATCH v3 0/4] Test examples compilation externally
Date: Thu, 22 Jun 2023 15:54:11 +0200	[thread overview]
Message-ID: <2074725.KlZ2vcFHjT@thomas> (raw)
In-Reply-To: <20230620140704.171667-1-david.marchand@redhat.com>

20/06/2023 16:07, David Marchand:
> As DPDK provides examples compiled with makefiles, we need some tests in
> the CI. So far, a few maintainers have been testing them but a simple
> issue has been missed for some time and there was no way to try to build
> all examples that were built with meson.
> 
> Additionnally, this series can help in identify issues in public headers
> that the current headers check can not catch as it relies on the meson
> framework for finding headers include path (which points at sources).
> 
> Changes since v2:
> - tweaked patch 2 commitlog,
> - dropped -e sed option in patch 3/4,
> 
> Changes since v1:
> - reworked built examples discovery,

Applied with the additional patch for l2fwd-cat, thanks.



      parent reply	other threads:[~2023-06-22 13:54 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-13  8:17 [PATCH " 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
2023-06-22 13:54   ` 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=2074725.KlZ2vcFHjT@thomas \
    --to=thomas@monjalon.net \
    --cc=bruce.richardson@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.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).