public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Yuki Machida <machida.yuki@jp.fujitsu.com>
To: Martin KaFai Lau <kafai@fb.com>
Cc: netdev@vger.kernel.org
Subject: Re: Hung up was occurred after v4.4-rc1 during IPv6 Ready Logo Conformance Test
Date: Thu, 17 Mar 2016 16:40:41 +0900	[thread overview]
Message-ID: <56EA5F79.8030802@jp.fujitsu.com> (raw)
In-Reply-To: <20160310063919.GA76112@kafai-mba.local>

Hi Martin,

Thank you for your reply.
Sorry for the delay.

On 2016年03月10日 15:39, Martin KaFai Lau wrote:
> On Thu, Mar 10, 2016 at 01:21:05PM +0900, Yuki Machida wrote:
>> Hi all,
>>
>> Hung up was occurred at Linux Kernel after v4.4-rc1 during IPv6 Ready Logo Conformance Test.
>> Not Fix a bug in v4.5-rc7 yet.
>>
>> Currently, it is under investigation.
>>
>> The following are the details:
> I think you forgot to paste the details?
I found that this problem don't cause a hang-up.
I will report again after more investigation.

>
>>
>> IPv6 Ready Logo
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ipv6ready.org_&d=CwICJg&c=5VD0RTtNlTh3ycd41b3MUw&r=VQnoQ7LvghIj0gVEaiQSUw&m=BzjeED6xB_NfQBjateVt8Gh7IK7hST7tSmPGXEAtRdQ&s=oaM204vOhRnGb6aTD1wxTZu9ss_bCzFAeZU0EmvVe6I&e=
>>
>> I ran the IPv6 Ready Logo Core Conformance Test on Intel D510MO (Atom D510).
>> It is using userland build with yocto project.
>>
>> Test Environment
>> Test Specification          : 4.0.6
>> Tool Version                : REL_3_3_2
>> Test Program Version        : V6LC_5_0_0
>> Target Device               : Intel D510MO (Atom D510)
>>
>> Regards,
>> Yuki Machida
>

      reply	other threads:[~2016-03-17  7:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-10  4:21 Hung up was occurred after v4.4-rc1 during IPv6 Ready Logo Conformance Test Yuki Machida
2016-03-10  6:39 ` Martin KaFai Lau
2016-03-17  7:40   ` Yuki Machida [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=56EA5F79.8030802@jp.fujitsu.com \
    --to=machida.yuki@jp.fujitsu.com \
    --cc=kafai@fb.com \
    --cc=netdev@vger.kernel.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