public inbox for bpf@vger.kernel.org
 help / color / mirror / Atom feed
From: Anton Protopopov <a.s.protopopov@gmail.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: bpf <bpf@vger.kernel.org>, Alexei Starovoitov <ast@kernel.org>,
	Andrii Nakryiko <andrii@kernel.org>,
	Anton Protopopov <aspsk@isovalent.com>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Eduard Zingerman <eddyz87@gmail.com>,
	Quentin Monnet <qmo@kernel.org>,
	Yonghong Song <yonghong.song@linux.dev>
Subject: Re: [PATCH v4 bpf-next 00/15] BPF indirect jumps
Date: Tue, 30 Sep 2025 12:26:51 +0000	[thread overview]
Message-ID: <aNvMi8T5YvgTFVCJ@mail.gmail.com> (raw)
In-Reply-To: <CAADnVQLvH8bjVYh4XiAvt=8+QKGY3imEuLjm9+zEe3744HM-Fw@mail.gmail.com>

On 25/09/30 01:59PM, Alexei Starovoitov wrote:
> On Tue, Sep 30, 2025 at 12:49 PM Anton Protopopov
> <a.s.protopopov@gmail.com> wrote:
> >
> > v3 -> v4 (this series):
> 
> Doesn't apply to bpf-next :(

Oh, sorry, I will resend it now.

> pw-bot: cr

      reply	other threads:[~2025-09-30 12:21 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-30 10:55 [PATCH v4 bpf-next 00/15] BPF indirect jumps Anton Protopopov
2025-09-30 10:55 ` [PATCH v4 bpf-next 01/15] bpf: fix the return value of push_stack Anton Protopopov
2025-09-30 10:55 ` [PATCH v4 bpf-next 02/15] bpf: save the start of functions in bpf_prog_aux Anton Protopopov
2025-09-30 10:55 ` [PATCH v4 bpf-next 03/15] bpf: generalize and export map_get_next_key for arrays Anton Protopopov
2025-09-30 10:55 ` [PATCH v4 bpf-next 04/15] bpf, x86: add new map type: instructions array Anton Protopopov
2025-09-30 10:55 ` [PATCH v4 bpf-next 05/15] selftests/bpf: add selftests for new insn_array map Anton Protopopov
2025-09-30 10:55 ` [PATCH v4 bpf-next 06/15] bpf: support instructions arrays with constants blinding Anton Protopopov
2025-09-30 10:55 ` [PATCH v4 bpf-next 07/15] selftests/bpf: test instructions arrays with blinding Anton Protopopov
2025-09-30 10:55 ` [PATCH v4 bpf-next 08/15] bpf, x86: allow indirect jumps to r8...r15 Anton Protopopov
2025-09-30 10:55 ` [PATCH v4 bpf-next 09/15] bpf: make bpf_insn_successors to return a pointer Anton Protopopov
2025-09-30 10:55 ` [PATCH v4 bpf-next 10/15] bpf, x86: add support for indirect jumps Anton Protopopov
2025-09-30 10:55 ` [PATCH v4 bpf-next 11/15] bpf: disasm: add support for BPF_JMP|BPF_JA|BPF_X Anton Protopopov
2025-09-30 10:55 ` [PATCH v4 bpf-next 12/15] libbpf: fix formatting of bpf_object__append_subprog_code Anton Protopopov
2025-09-30 10:55 ` [PATCH v4 bpf-next 13/15] libbpf: support llvm-generated indirect jumps Anton Protopopov
2025-09-30 10:55 ` [PATCH v4 bpf-next 14/15] bpftool: Recognize insn_array map type Anton Protopopov
2025-09-30 10:55 ` [PATCH v4 bpf-next 15/15] selftests/bpf: add selftests for indirect jumps Anton Protopopov
2025-09-30 11:59 ` [PATCH v4 bpf-next 00/15] BPF " Alexei Starovoitov
2025-09-30 12:26   ` Anton Protopopov [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=aNvMi8T5YvgTFVCJ@mail.gmail.com \
    --to=a.s.protopopov@gmail.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=andrii@kernel.org \
    --cc=aspsk@isovalent.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=qmo@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