public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel•org
To: Florian Lehner <dev@der-flo•net>
Cc: bpf@vger•kernel.org, netdev@vger•kernel.org, ast@kernel•org,
	daniel@iogearbox•net, andrii@kernel•org,
	john.fastabend@gmail•com
Subject: Re: [PATCH 0/2 v3] Improve error handling of verifier tests
Date: Fri, 04 Dec 2020 20:30:06 +0000	[thread overview]
Message-ID: <160711380631.17303.9145064627875444770.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20201204181828.11974-1-dev@der-flo.net>

Hello:

This series was applied to bpf/bpf-next.git (refs/heads/master):

On Fri,  4 Dec 2020 19:18:26 +0100 you wrote:
> These patches improve the error handling for verifier tests. With "Test
> the 32bit narrow read" Krzesimir Nowak provided these patches first, but
> they were never merged.
> The improved error handling helps to implement and test BPF program types
> that are not supported yet.
> 
> v3:
>   - Add explicit fallthrough
> 
> [...]

Here is the summary with links:
  - [1/2] selftests/bpf: Print reason when a tester could not run a program
    https://git.kernel.org/bpf/bpf-next/c/7d17167244f5
  - [2/2] selftests/bpf: Avoid errno clobbering
    https://git.kernel.org/bpf/bpf-next/c/5f61b7c6975b

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



      parent reply	other threads:[~2020-12-04 20:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-04 18:18 [PATCH 0/2 v3] Improve error handling of verifier tests Florian Lehner
2020-12-04 18:18 ` [PATCH 1/2] selftests/bpf: Print reason when a tester could not run a program Florian Lehner
2020-12-04 18:18 ` [PATCH 2/2] selftests/bpf: Avoid errno clobbering Florian Lehner
2020-12-04 20:30 ` 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=160711380631.17303.9145064627875444770.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel$(echo .)org \
    --cc=andrii@kernel$(echo .)org \
    --cc=ast@kernel$(echo .)org \
    --cc=bpf@vger$(echo .)kernel.org \
    --cc=daniel@iogearbox$(echo .)net \
    --cc=dev@der-flo$(echo .)net \
    --cc=john.fastabend@gmail$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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