From: Stephen Hemminger <stephen@networkplumber.org>
To: Harsh raj Singh <singhharshraj215@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH] examples/l2fwd_acl: add ACL-based L2 forwarding example
Date: Mon, 23 Feb 2026 09:07:46 -0800 [thread overview]
Message-ID: <20260223090746.14d3bde3@phoenix.local> (raw)
In-Reply-To: <CAN33txETfmQEj8j=W4-nkUk1rAq0_JLhZuR4R-c3YCrDY90y6A@mail.gmail.com>
On Sat, 21 Feb 2026 00:13:33 +0530
Harsh raj Singh <singhharshraj215@gmail.com> wrote:
> diff --git a/examples/l2fwd_acl/main.c b/examples/l2fwd_acl/main.c
> new file mode 100644
> index 0000000000..6e05145b33
> --- /dev/null
> +++ b/examples/l2fwd_acl/main.c
> @@ -0,0 +1,247 @@
> +/* SPDX-License-Identifier: BSD-3-Clause
> + * l
New files should have a copyright.
next prev parent reply other threads:[~2026-02-23 17:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 18:43 [PATCH] examples/l2fwd_acl: add ACL-based L2 forwarding example Harsh raj Singh
2026-02-23 4:28 ` Harsh raj Singh
2026-02-23 9:09 ` Harsh raj Singh
2026-02-23 17:07 ` Stephen Hemminger [this message]
2026-02-23 17:08 ` Stephen Hemminger
-- strict thread matches above, loose matches on Subject: below --
2026-02-19 9:25 Harsh raj Singh
2026-02-20 17:25 ` Stephen Hemminger
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=20260223090746.14d3bde3@phoenix.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=singhharshraj215@gmail.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