From: Yuki Machida <machida.yuki@jp.fujitsu.com>
To: Larry Goss <Larry.Goss@enea.com>, yocto@yoctoproject.org
Subject: Re: ipv6 testing
Date: Tue, 19 Jan 2016 18:58:13 +0900 [thread overview]
Message-ID: <569E08B5.8050502@jp.fujitsu.com> (raw)
In-Reply-To: <37573EC8CA5E1846A6DF0BDECDD7DA9329CC1E62@SESTOEX04.enea.se>
Hi,
> Does Yocto do any IPv6 conformance testing?
We are using IPv6 Ready Logo Conformance Test.
It can check the basic function of IPv6.
What’s IPv6 Ready Logo
\vLINKIFYIJaDeeHGHHCDfaHcAdCHIcICcafIcFCIbbdBbfaD
IPv6 Ready Logo test suite
\vLINKIFYJCEbAEfDeIJfECFcIfIebBAJJadCDGFEHJdGBCcb
Embedded Linux Distributor of Fujitsu includes
LTSI Kernel and is built with Yocto Project.
We are testing our distribution by IPv6 Ready Logo Conformance Test.
http://www.fujitsu.com/downloads/JP/archive/imgjp/group/fct/v4/events/exhibit/ipv6-evaluation-status-of-ltsi-r004.pdf
Best regards,
Yuki Machida
On 2016年01月16日 03:52, Larry Goss wrote:
> Hi,
>
> Does Yocto do any IPv6 conformance testing?
>
> Thanks,
>
> *Larry Goss*
>
> Sr. Field Applications Engineer
>
> Enea North America
>
> *Email*: larry.goss@enea.com**
>
> *Phone*: (603) 475-1087
>
> http://www.enea.com/
>
> ________________________________________________________________________________________________________________________________
>
> This message, including attachments, is CONFIDENTIAL. It may also be privileged or otherwise protected by law. If you received this email by mistake please let us know by reply and then delete it from your system; you should not copy it or disclose its contents to anyone. All messages sent to and from Enea may be monitored to ensure compliance with internal policies and to protect our business. Emails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message, which arise as a result of e-mail transmission. Anyone who communicates with us by email accepts these risks.
>
>
>
prev parent reply other threads:[~2016-01-19 10:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-15 18:52 ipv6 testing Larry Goss
2016-01-18 17:11 ` akuster
2016-01-19 9:58 ` 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=569E08B5.8050502@jp.fujitsu.com \
--to=machida.yuki@jp.fujitsu.com \
--cc=Larry.Goss@enea.com \
--cc=yocto@yoctoproject.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.