From: David Ahern <dsahern@kernel.org>
To: kernel test robot <oliver.sang@intel.com>,
Richard Gobert <richardbgobert@gmail.com>
Cc: lkp@lists.01.org, lkp@intel.com, Jakub Kicinski <kuba@kernel.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [net] 0e4d354762: kernel-selftests.net.fcnal-test.sh.fail
Date: Sun, 30 Oct 2022 09:59:29 -0600 [thread overview]
Message-ID: <2adc406f-1abf-1312-941a-47a1e1f4c995@kernel.org> (raw)
In-Reply-To: <202210062117.c7eef1a3-oliver.sang@intel.com>
On 10/6/22 7:23 AM, kernel test robot wrote:
> # TEST: Global server, device client via IP_UNICAST_IF, local connection, with connect() - ns-A loopback IPv6 [FAIL]
...
> # TEST: Global server, device client via IP_UNICAST_IF, local connection, with connect() - ns-A loopback IPv6 [FAIL]
Richard:
Don't recall a followup on this report. Can you take a look? These tests
were added by you after your change for IP_UNICAST_IF.
prev parent reply other threads:[~2022-10-30 15:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-06 13:23 kernel test robot
2022-10-30 15:59 ` David Ahern [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=2adc406f-1abf-1312-941a-47a1e1f4c995@kernel.org \
--to=dsahern@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=netdev@vger.kernel.org \
--cc=oliver.sang@intel.com \
--cc=richardbgobert@gmail.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
Powered by JetHome