All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Shani Peretz <shperetz@nvidia.com>
Cc: dev@dpdk.org, Ori Kam <orika@nvidia.com>
Subject: Re: [PATCH v2] examples/flow_filtering: add more snippets
Date: Tue, 25 Nov 2025 00:27:23 +0100	[thread overview]
Message-ID: <3100526.bB369e8A3T@thomas> (raw)
In-Reply-To: <20251113101347.162908-1-shperetz@nvidia.com>

13/11/2025 11:13, Shani Peretz:
> Added the following snippets:
> - Steering by Integrity Check Flags
> - Match packet type
> - ECN in IP Header Modification
> - Random Match
> - VXLAN-GPE Header Fields Matching
> - VXLAN-GBP Header Fields Matching
> - NVGRE Matching
> - NAT64 Action Usage
> 
> Signed-off-by: Shani Peretz <shperetz@nvidia.com>
> 
> --------------
> v2: fix compilation errors

There are still some issues but I fail to understand why:

/usr/bin/ld: build/snippet_NAT64.o: in function `snippet_match_nat64_create_actions':
snippet_NAT64.c:(.text+0x43): undefined reference to `create_jump_flow'
/usr/bin/ld: build/snippet_match_nvgre.o: in function `snippet_match_nvgre_create_actions':
snippet_match_nvgre.c:(.text+0x44): undefined reference to `create_jump_flow'
/usr/bin/ld: build/snippet_match_vxlan_gpe.o: in function `snippet_match_vxlan_gpe_create_actions':
snippet_match_vxlan_gpe.c:(.text+0x44): undefined reference to `create_jump_flow'




  reply	other threads:[~2025-11-24 23:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-19  9:52 [PATCH] examples/flow_filtering: add more snippets Shani Peretz
2025-11-13 10:13 ` [PATCH v2] " Shani Peretz
2025-11-24 23:27   ` Thomas Monjalon [this message]
2025-12-02  9:50   ` [PATCH v3] " Shani Peretz
2026-03-25 23:40     ` 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=3100526.bB369e8A3T@thomas \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=orika@nvidia.com \
    --cc=shperetz@nvidia.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 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.