BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Anton Protopopov <a.s.protopopov@gmail.com>
Cc: bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next 0/2] A pair of follow ups for indirect jumps
Date: Fri, 28 Nov 2025 23:20:17 +0000	[thread overview]
Message-ID: <176437201779.828244.16468414801366441428.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20251128063224.1305482-1-a.s.protopopov@gmail.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Alexei Starovoitov <ast@kernel.org>:

On Fri, 28 Nov 2025 06:32:22 +0000 you wrote:
> Two fixes suggested by Alexei in [1]. Resending as a series,
> as the second patch depends on the first.
> 
>   [1] https://lore.kernel.org/bpf/CAADnVQK3piReoo1ja=9hgz7aJ60Y_Jjur_JMOaYV8-Mn_VyE4A@mail.gmail.com/#R
> 
> Anton Protopopov (2):
>   bpf: force BPF_F_RDONLY_PROG on insn array creation
>   bpf: check for insn arrays in check_ptr_alignment
> 
> [...]

Here is the summary with links:
  - [bpf-next,1/2] bpf: force BPF_F_RDONLY_PROG on insn array creation
    https://git.kernel.org/bpf/bpf-next/c/7feff23cdf2e
  - [bpf-next,2/2] bpf: check for insn arrays in check_ptr_alignment
    https://git.kernel.org/bpf/bpf-next/c/e3ea26add687

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2025-11-28 23:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-28  6:32 [PATCH bpf-next 0/2] A pair of follow ups for indirect jumps Anton Protopopov
2025-11-28  6:32 ` [PATCH bpf-next 1/2] bpf: force BPF_F_RDONLY_PROG on insn array creation Anton Protopopov
2025-11-28  6:32 ` [PATCH bpf-next 2/2] bpf: check for insn arrays in check_ptr_alignment Anton Protopopov
2025-11-28 23:20 ` 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=176437201779.828244.16468414801366441428.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=a.s.protopopov@gmail.com \
    --cc=bpf@vger.kernel.org \
    /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