All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Hangbin Liu <liuhangbin@gmail.com>
Cc: netdev@vger.kernel.org, sean@mess.org, ast@kernel.org,
	daniel@iogearbox.net
Subject: Re: [PATCHv2 bpf] selftests/bpf/test_lirc_mode2.sh: exit with proper code
Date: Mon, 21 Mar 2022 13:50:09 +0000	[thread overview]
Message-ID: <164787060996.2929.14760488487635325153.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220321024149.157861-1-liuhangbin@gmail.com>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:

On Mon, 21 Mar 2022 10:41:49 +0800 you wrote:
> When test_lirc_mode2_user exec failed, the test report failed but still
> exit with 0. Fix it by exiting with an error code.
> 
> Another issue is for the LIRCDEV checking. With bash -n, we need to quote
> the variable, or it will always be true. So if test_lirc_mode2_user was
> not run, just exit with skip code.
> 
> [...]

Here is the summary with links:
  - [PATCHv2,bpf] selftests/bpf/test_lirc_mode2.sh: exit with proper code
    https://git.kernel.org/bpf/bpf-next/c/ec80906b0fbd

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



      reply	other threads:[~2022-03-21 13:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-17  7:18 [PATCH bpf] selftests/bpf: exit with error code if test failed Hangbin Liu
2022-03-18 15:05 ` Daniel Borkmann
2022-03-21  2:41 ` [PATCHv2 bpf] selftests/bpf/test_lirc_mode2.sh: exit with proper code Hangbin Liu
2022-03-21 13: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=164787060996.2929.14760488487635325153.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=ast@kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=liuhangbin@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=sean@mess.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 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.