All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Eduard Zingerman <eddyz87@gmail.com>
Cc: bpf@vger.kernel.org, ast@kernel.org, andrii@kernel.org,
	daniel@iogearbox.net, martin.lau@linux.dev, kernel-team@fb.com,
	yonghong.song@linux.dev, andrii.nakryiko@gmail.com
Subject: Re: [PATCH bpf-next v1] selftests/bpf: bpf_rdonly_cast u{8,16,32,64} access tests
Date: Sat, 28 Jun 2025 02:50:05 +0000	[thread overview]
Message-ID: <175107900577.2118971.13642028018339865468.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250627015539.1439656-1-eddyz87@gmail.com>

Hello:

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

On Thu, 26 Jun 2025 18:55:39 -0700 you wrote:
> Tests with aligned and misaligned memory access of different sizes via
> pointer returned by bpf_rdonly_cast().
> 
> Suggested-by: Andrii Nakryiko <andrii.nakryiko@gmail.com>
> Signed-off-by: Eduard Zingerman <eddyz87@gmail.com>
> ---
>  .../bpf/progs/mem_rdonly_untrusted.c          | 41 +++++++++++++++++++
>  1 file changed, 41 insertions(+)

Here is the summary with links:
  - [bpf-next,v1] selftests/bpf: bpf_rdonly_cast u{8,16,32,64} access tests
    https://git.kernel.org/bpf/bpf-next/c/c4b1be928ea0

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



      reply	other threads:[~2025-06-28  2:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-27  1:55 [PATCH bpf-next v1] selftests/bpf: bpf_rdonly_cast u{8,16,32,64} access tests Eduard Zingerman
2025-06-28  2: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=175107900577.2118971.13642028018339865468.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii.nakryiko@gmail.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=eddyz87@gmail.com \
    --cc=kernel-team@fb.com \
    --cc=martin.lau@linux.dev \
    --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 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.