From: Amit kumar <akamit91@hotmail.com>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [NVMe SCT] Mistakes in nvmepassthru sct test case.
Date: Thu, 23 Nov 2017 16:22:57 +0000 [thread overview]
Message-ID: <DM5PR11MB1578A035FCB47B8E006D24D6DC210@DM5PR11MB1578.namprd11.prod.outlook.com> (raw)
In-Reply-To: <DM5PR11MB157842A99BC3F119EB63B484DC210@DM5PR11MB1578.namprd11.prod.outlook.com>
Forgot to mention. UEFI SCT II Case Spec 2.5 page 910 and UEFI SCT II Case Spec 2.6 A page 855.
> On Nov 23, 2017, at 9:36 PM, Amit kumar <akamit91@hotmail.com> wrote:
>
> Hi ,
> I think there is something wrong with SCT nvmepassthru test case mentioned on page 910 UEFI SCT II Case Spec. for which i have attached the screen shot.
> The assertion and test description looks contradictory.
> Also it fails if passthru doesnt support NON-BLOCKING mode.
>
> 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-23 16:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-23 16:06 [NVMe SCT] Mistakes in nvmepassthru sct test case Amit kumar
2017-11-23 16:22 ` Amit kumar [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=DM5PR11MB1578A035FCB47B8E006D24D6DC210@DM5PR11MB1578.namprd11.prod.outlook.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