linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Jie2x Zhou <jie2x.zhou@intel.com>
Cc: davem@davemloft.net, kuba@kernel.org, shuah@kernel.org,
	dsahern@gmail.com, netdev@vger.kernel.org,
	linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
	lkp@intel.com, xinjianx.ma@intel.com, zhijianx.li@intel.com,
	philip.li@intel.com
Subject: Re: [PATCH v3] selftests: net: Correct ping6 expected rc from 2 to 1
Date: Fri, 10 Dec 2021 03:20:08 +0000	[thread overview]
Message-ID: <163910640878.13476.2519511898599945642.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20211209020230.37270-1-jie2x.zhou@intel.com>

Hello:

This patch was applied to netdev/net.git (master)
by Jakub Kicinski <kuba@kernel.org>:

On Thu,  9 Dec 2021 10:02:30 +0800 you wrote:
> ./fcnal-test.sh -v -t ipv6_ping
> TEST: ping out, VRF bind - ns-B IPv6 LLA                                      [FAIL]
> TEST: ping out, VRF bind - multicast IP                                       [FAIL]
> 
> ping6 is failing as it should.
> COMMAND: ip netns exec ns-A /bin/ping6 -c1 -w1 fe80::7c4c:bcff:fe66:a63a%red
> strace of ping6 shows it is failing with '1',
> so change the expected rc from 2 to 1.
> 
> [...]

Here is the summary with links:
  - [v3] selftests: net: Correct ping6 expected rc from 2 to 1
    https://git.kernel.org/netdev/net/c/92816e262980

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



      reply	other threads:[~2021-12-10  3:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-09  2:02 [PATCH v3] selftests: net: Correct ping6 expected rc from 2 to 1 Jie2x Zhou
2021-12-10  3: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=163910640878.13476.2519511898599945642.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dsahern@gmail.com \
    --cc=jie2x.zhou@intel.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=philip.li@intel.com \
    --cc=shuah@kernel.org \
    --cc=xinjianx.ma@intel.com \
    --cc=zhijianx.li@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).