From: patchwork-bot+netdevbpf@kernel.org
To: None <gyutae.opensource@navercorp.com>
Cc: qmo@kernel.org, bpf@vger.kernel.org, daniel@iogearbox.net,
linux-kernel@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
martin.lau@linux.dev, eddyz87@gmail.com, song@kernel.org,
yonghong.song@linux.dev, john.fastabend@gmail.com,
kpsingh@kernel.org, sdf@fomichev.me, haoluo@google.com,
jolsa@kernel.org, gyutae.bae@navercorp.com,
siwan.kim@navercorp.com, dxu@dxuuu.xyz, jiayuan.chen@linux.dev,
chen.dylane@linux.dev, memxor@gmail.com
Subject: Re: [PATCH v4] bpftool: Add 'prepend' option for tcx attach to insert at chain start
Date: Fri, 16 Jan 2026 22:50:07 +0000 [thread overview]
Message-ID: <176860380780.826620.7253991857849966503.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260112034516.22723-1-gyutae.opensource@navercorp.com>
Hello:
This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@kernel.org>:
On Mon, 12 Jan 2026 12:45:16 +0900 you wrote:
> From: Gyutae Bae <gyutae.bae@navercorp.com>
>
> Add support for the 'prepend' option when attaching tcx_ingress and
> tcx_egress programs. This option allows inserting a BPF program at
> the beginning of the TCX chain instead of appending it at the end.
>
> The implementation uses BPF_F_BEFORE flag which automatically inserts
> the program at the beginning of the chain when no relative reference
> is specified.
>
> [...]
Here is the summary with links:
- [v4] bpftool: Add 'prepend' option for tcx attach to insert at chain start
https://git.kernel.org/bpf/bpf-next/c/999b2395e3c3
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-01-16 22:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20251023093150.25411-1-gyutae.bae@navercorp.com>
2025-11-01 16:21 ` [PATCH] bpftool: Add 'head' " Quentin Monnet
2026-01-06 8:55 ` [PATCH v2] bpftool: Add 'prepend' " gyutae.opensource
2026-01-06 13:11 ` Daniel Borkmann
2026-01-07 2:29 ` [PATCH v3] " gyutae.opensource
2026-01-10 2:48 ` Quentin Monnet
2026-01-12 3:45 ` [PATCH v4] " gyutae.opensource
2026-01-12 10:20 ` Quentin Monnet
2026-01-14 14:19 ` Daniel Borkmann
2026-01-16 22:50 ` patchwork-bot+netdevbpf [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=176860380780.826620.7253991857849966503.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=chen.dylane@linux.dev \
--cc=daniel@iogearbox.net \
--cc=dxu@dxuuu.xyz \
--cc=eddyz87@gmail.com \
--cc=gyutae.bae@navercorp.com \
--cc=gyutae.opensource@navercorp.com \
--cc=haoluo@google.com \
--cc=jiayuan.chen@linux.dev \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=memxor@gmail.com \
--cc=qmo@kernel.org \
--cc=sdf@fomichev.me \
--cc=siwan.kim@navercorp.com \
--cc=song@kernel.org \
--cc=yonghong.song@linux.dev \
/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
all inboxes | Powered by JetHome®