From: "Jin, Eric" <eric.jin@intel.com>
To: Amit kumar <akamit91@hotmail.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: SCT forum help
Date: Fri, 24 Nov 2017 06:15:11 +0000 [thread overview]
Message-ID: <DA72DC7456565B47808A57108259571F6357996E@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <DM5PR11MB157872C422AB222E8A6DE08BDC210@DM5PR11MB1578.namprd11.prod.outlook.com>
Hi Amit Kumar,
Please send email to utwg@uefi.org for the UEFI SCT discussion.
BTW, please make sure to provide more detail, such as the log, and your concern.
I don't see any attachment in your before email - [edk2] [NVMe SCT] Mistakes in nvmepassthru sct test case..
Best Regards
Eric
-----Original Message-----
From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Amit kumar
Sent: Friday, November 24, 2017 12:49 AM
To: edk2-devel@lists.01.org
Subject: [edk2] SCT forum help
HI
Can somebody tell me the mail chain where i can discuss sct spec and test cases related issue ?
Best Regards
Amit Kumar
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel
prev parent reply other threads:[~2017-11-24 6:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 16:49 SCT forum help Amit kumar
2017-11-24 6:15 ` Jin, Eric [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-list 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=DA72DC7456565B47808A57108259571F6357996E@SHSMSX103.ccr.corp.intel.com \
--to=devel@edk2.groups.io \
/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