From: Daniel Samuelraj <daniel.samuelraj@broadcom.com>
To: edk2-devel@lists.01.org, utwg@uefi.org, uswg@uefi.org
Cc: Chidambara GR <chidambara.gr@broadcom.com>,
Jianning Wang <jianning.wang@broadcom.com>,
Sathya Prakash <sathya.prakash@broadcom.com>
Subject: Re: SCT 2.3.1 v1.3
Date: Tue, 17 Jan 2017 16:22:35 -0500 [thread overview]
Message-ID: <be4395166613908a2f32c9c0d0af91ab@mail.gmail.com> (raw)
In-Reply-To: 6aa20a69642c82412e1ed5fcfc720e6f@mail.gmail.com
Hi,
What SCT v1.3 states for HII Config Access Protocol seems not in align with
UEFI spec? For example, for extract config, when Progress or Result or
Request is NULL, SCT is expecting EFI Invalid Parameter; similarly for
Route Config, when progress is NULL, SCT expects EFI_INVALID_PARAMETER.
UEFI spec doesn’t seem mention anything for these cases.
Should driver adhere to what SCT expects? Or is this fixed in newer SCT or
will this be addressed in future? Please advise!
Thanks,
Daniel
next reply other threads:[~2017-01-17 21:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 21:22 Daniel Samuelraj [this message]
2017-01-18 8:56 ` SCT 2.3.1 v1.3 Laszlo Ersek
2017-01-20 9:35 ` Gao, Liming
2017-01-22 1:21 ` Jin, Eric
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=be4395166613908a2f32c9c0d0af91ab@mail.gmail.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