All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Kal Conley <kal.conley@dectris.com>
Cc: bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next 0/2] selftests: xsk: Add test case for packets at end of UMEM
Date: Wed, 05 Apr 2023 19:20:18 +0000	[thread overview]
Message-ID: <168072241858.12939.4882404272620837331.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230403145047.33065-1-kal.conley@dectris.com>

Hello:

This series was applied to bpf/bpf-next.git (master)
by Martin KaFai Lau <martin.lau@kernel.org>:

On Mon,  3 Apr 2023 16:50:45 +0200 you wrote:
> This patchset fixes a minor bug in xskxceiver.c then adds a test case
> for valid packets at the end of the UMEM.
> 
> Kal Conley (2):
>   selftests: xsk: Use correct UMEM size in testapp_invalid_desc
>   selftests: xsk: Add test case for packets at end of UMEM
> 
> [...]

Here is the summary with links:
  - [bpf-next,1/2] selftests: xsk: Use correct UMEM size in testapp_invalid_desc
    https://git.kernel.org/bpf/bpf-next/c/7a2050df244e
  - [bpf-next,2/2] selftests: xsk: Add test case for packets at end of UMEM
    https://git.kernel.org/bpf/bpf-next/c/ccd1b2933f8c

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



      parent reply	other threads:[~2023-04-05 19:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-03 14:50 [PATCH bpf-next 0/2] selftests: xsk: Add test case for packets at end of UMEM Kal Conley
2023-04-03 14:50 ` [PATCH bpf-next 1/2] selftests: xsk: Use correct UMEM size in testapp_invalid_desc Kal Conley
2023-04-04  6:26   ` Magnus Karlsson
2023-04-03 14:50 ` [PATCH bpf-next 2/2] selftests: xsk: Add test case for packets at end of UMEM Kal Conley
2023-04-04  6:27   ` Magnus Karlsson
2023-04-05 19:16 ` [PATCH bpf-next 0/2] " Martin KaFai Lau
2023-04-05 19:31   ` Kal Cutter Conley
2023-04-05 19:49     ` Martin KaFai Lau
2023-04-05 19: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=168072241858.12939.4882404272620837331.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=kal.conley@dectris.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 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.