BPF List
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: KP Singh <kpsingh@kernel.org>
Cc: bpf@vger.kernel.org, ast@kernel.org, daniel@iogearbox.net,
	andrii@kernel.org, revest@chromium.org, jackmanb@chromium.org
Subject: Re: [PATCH bpf-next] selftests/bpf: Propagate error code of the command to vmtest.sh
Date: Fri, 26 Feb 2021 21:20:07 +0000	[thread overview]
Message-ID: <161437440784.26505.14457726843836860385.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210225161947.1778590-1-kpsingh@kernel.org>

Hello:

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

On Thu, 25 Feb 2021 16:19:47 +0000 you wrote:
> From: KP Singh <kpsingh@google.com>
> 
> When vmtest.sh ran a command in a VM, it did not record or propagate the
> error code of the command. This made the script less "script-able". The
> script now saves the error code of the said command in a file in the VM,
> copies the file back to the host and (when available) uses this error
> code instead of its own.
> 
> [...]

Here is the summary with links:
  - [bpf-next] selftests/bpf: Propagate error code of the command to vmtest.sh
    https://git.kernel.org/bpf/bpf-next/c/2854436612c4

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



      parent reply	other threads:[~2021-02-26 21:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-25 16:19 [PATCH bpf-next] selftests/bpf: Propagate error code of the command to vmtest.sh KP Singh
2021-02-26 21:18 ` Andrii Nakryiko
2021-02-26 21: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=161437440784.26505.14457726843836860385.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=jackmanb@chromium.org \
    --cc=kpsingh@kernel.org \
    --cc=revest@chromium.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