From: Bruce Richardson <bruce.richardson@intel.com>
To: <jerinj@marvell.com>
Cc: Rajesh Kumar <rajesh3.kumar@intel.com>, <dev@dpdk.org>,
<thomas@monjalon.net>, <david.marchand@redhat.com>,
<stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v1] examples/ptp_tap_relay_sw: fix build inclusion
Date: Wed, 2 Sep 2026 10:42:46 +0100 [thread overview]
Message-ID: <apfvlnSMoRdIgR71@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20260902082523.206083-1-jerinj@marvell.com>
On Wed, Sep 02, 2026 at 01:55:23PM +0530, jerinj@marvell.com wrote:
> From: Jerin Jacob <jerinj@marvell.com>
>
> The ptp_tap_relay_sw example was not building because
> examples/meson.build was not updated to wire up this directory.
>
> Fixes: bec00deaa8fb ("examples/ptp_tap_relay_sw: add PTP transparent clock relay")
> Cc: stable@dpdk.org
>
> Signed-off-by: Jerin Jacob <jerinj@marvell.com>
> ---
> examples/meson.build | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/examples/meson.build b/examples/meson.build
> index 25d9c88457..ab82cf5fbd 100644
> --- a/examples/meson.build
> +++ b/examples/meson.build
> @@ -43,6 +43,7 @@ all_examples = [
> 'packet_ordering',
> 'pipeline',
> 'ptpclient',
> + 'ptp_tap_relay_sw',
> 'qos_meter',
> 'qos_sched',
> 'rxtx_callbacks',
Minor nit, the ptp_tap_relay_sw line should be before ptpclient rather than
after, as word breaks or underscores count before "a" alphabetically,
rather than being skipped.
Otherwise:
Acked-by: Bruce Richardson <bruce.richardson@intel.com>
> --
> 2.54.0
>
next prev parent reply other threads:[~2026-09-02 9:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 8:25 [dpdk-dev] [PATCH v1] examples/ptp_tap_relay_sw: fix build inclusion jerinj
2026-09-02 9:09 ` David Marchand
2026-09-02 9:41 ` Bruce Richardson
2026-09-02 9:42 ` Bruce Richardson [this message]
2026-09-02 15:33 ` [dpdk-dev] [PATCH v2] " jerinj
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=apfvlnSMoRdIgR71@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=rajesh3.kumar@intel.com \
--cc=stable@dpdk.org \
--cc=thomas@monjalon.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.