From: "gaoliming" <gaoliming@byosoft.com.cn>
To: <devel@edk2.groups.io>, <abner.chang@hpe.com>
Cc: "'Dandan Bi'" <dandan.bi@intel.com>,
"'Wang, Nickle \(HPS SW\)'" <nickle.wang@hpe.com>,
"'O'Hanley, Peter \(EXL\)'" <peter.ohanley@hpe.com>
Subject: 回复: [edk2-devel] 回复: [VFR REST_STYLE PATCH 1/1] VfrSpecification: Add REST_STYLE
Date: Tue, 10 Nov 2020 09:32:42 +0800 [thread overview]
Message-ID: <008301d6b701$62b04da0$2810e8e0$@byosoft.com.cn> (raw)
In-Reply-To: <CS1PR8401MB1144F9BE6B1E314608C6983AFFE90@CS1PR8401MB1144.NAMPRD84.PROD.OUTLOOK.COM>
[-- Attachment #1: Type: text/plain, Size: 6773 bytes --]
This change is for VFR spec, not for code. So, you don’t need to run patch
check for it.
Thanks
Liming
发件人: bounce+27952+67201+4905953+8761045@groups.io
<bounce+27952+67201+4905953+8761045@groups.io> 代表 Abner Chang
发送时间: 2020年11月10日 9:31
收件人: devel@edk2.groups.io
抄送: 'Dandan Bi' <dandan.bi@intel.com>; Wang, Nickle (HPS SW)
<nickle.wang@hpe.com>; O'Hanley, Peter (EXL) <peter.ohanley@hpe.com>
主题: Re: [edk2-devel] 回复: [VFR REST_STYLE PATCH 1/1] VfrSpecification:
Add REST_STYLE
But it won't passed the patch check. So skip patch check?
BtW, do we have owner of VfrSpec?
Abner
Get Outlook for Android <https://aka.ms/ghei36>
_____
From: devel@edk2.groups.io <mailto:devel@edk2.groups.io>
<devel@edk2.groups.io <mailto:devel@edk2.groups.io> > on behalf of gaoliming
<gaoliming@byosoft.com.cn <mailto:gaoliming@byosoft.com.cn> >
Sent: Tuesday, November 10, 2020 9:24:22 AM
To: Chang, Abner (HPS SW/FW Technologist) <abner.chang@hpe.com
<mailto:abner.chang@hpe.com> >; devel@edk2.groups.io
<mailto:devel@edk2.groups.io> <devel@edk2.groups.io
<mailto:devel@edk2.groups.io> >
Cc: 'Dandan Bi' <dandan.bi@intel.com <mailto:dandan.bi@intel.com> >; Wang,
Nickle (HPS SW) <nickle.wang@hpe.com <mailto:nickle.wang@hpe.com> >;
O'Hanley, Peter (EXL) <peter.ohanley@hpe.com <mailto:peter.ohanley@hpe.com>
>
Subject: [edk2-devel] 回复: [VFR REST_STYLE PATCH 1/1] VfrSpecification: Add
REST_STYLE
Abner:
The syntax change is OK. But, please keep license unchanged. This patch is
to add new syntax, not update license.
Thanks
Liming
> -----邮件原件-----
> 发件人: Abner Chang <abner.chang@hpe.com <mailto:abner.chang@hpe.com> >
> 发送时间: 2020年11月9日 23:46
> 收件人: devel@edk2.groups.io <mailto:devel@edk2.groups.io>
> 抄送: abner.chang@hpe.com <mailto:abner.chang@hpe.com> ; Liming Gao
<gaoliming@byosoft.com.cn <mailto:gaoliming@byosoft.com.cn> >;
> Dandan Bi <dandan.bi@intel.com <mailto:dandan.bi@intel.com> >; Nickle Wang
<nickle.wang@hpe.com <mailto:nickle.wang@hpe.com> >;
> Peter O'Hanley <peter.ohanley@hpe.com <mailto:peter.ohanley@hpe.com> >
> 主题: [VFR REST_STYLE PATCH 1/1] VfrSpecification: Add REST_STYLE
>
> Add REST_STYLE to question flag
>
> Signed-off-by: Abner Chang <abner.chang@hpe.com
<mailto:abner.chang@hpe.com> >
>
> Cc: Liming Gao <gaoliming@byosoft.com.cn <mailto:gaoliming@byosoft.com.cn>
>
> Cc: Dandan Bi <dandan.bi@intel.com <mailto:dandan.bi@intel.com> >
> Cc: Nickle Wang <nickle.wang@hpe.com <mailto:nickle.wang@hpe.com> >
> Cc: Peter O'Hanley <peter.ohanley@hpe.com <mailto:peter.ohanley@hpe.com> >
> ---
> .../210_vfr_general_token_definition.md | 13 +++----------
> 2_vfr_description_in_bnf/211_vfr_form_definition.md | 13 +++----------
> 2 files changed, 6 insertions(+), 20 deletions(-)
>
> diff --git a/2_vfr_description_in_bnf/210_vfr_general_token_definition.md
> b/2_vfr_description_in_bnf/210_vfr_general_token_definition.md
> index 7dc42f0..a60308d 100644
> --- a/2_vfr_description_in_bnf/210_vfr_general_token_definition.md
> +++ b/2_vfr_description_in_bnf/210_vfr_general_token_definition.md
> @@ -2,6 +2,7 @@
> 2.10 VFR General Token Definition
>
> Copyright (c) 2007-2017, Intel Corporation. All rights reserved.<BR>
> + (C) Copyright 2020 Hewlett Packard Enterprise Development LP<BR>
>
> Redistribution and use in source (original document form) and
'compiled'
> forms (converted to PDF, epub, HTML and other formats) with or without
> @@ -16,16 +17,7 @@
> notice, this list of conditions and the following disclaimer in the
> documentation and/or other materials provided with the distribution.
>
> - THIS DOCUMENTATION IS PROVIDED BY TIANOCORE PROJECT "AS IS"
> AND ANY EXPRESS OR
> - IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
> WARRANTIES OF
> - MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
> DISCLAIMED. IN NO
> - EVENT SHALL TIANOCORE PROJECT BE LIABLE FOR ANY DIRECT,
> INDIRECT, INCIDENTAL,
> - SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
> NOT LIMITED TO,
> - PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
> DATA, OR PROFITS;
> - OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
> OF LIABILITY,
> - WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
> NEGLIGENCE OR
> - OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
> DOCUMENTATION, EVEN IF
> - ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
> + SPDX-License-Identifier: BSD-2-Clause-Patent
>
> -->
>
> @@ -117,6 +109,7 @@ questionheaderFlagsField ::=
> | "INTERACTIVE"
> | "RESET_REQUIRED"
> | "OPTIONS_ONLY"
> + | "REST_STYLE"
>
> vfrStorageVarId ::=
> ( StringIdentifier "[" Number "]" )
> diff --git a/2_vfr_description_in_bnf/211_vfr_form_definition.md
> b/2_vfr_description_in_bnf/211_vfr_form_definition.md
> index 2e63bdf..b709f35 100644
> --- a/2_vfr_description_in_bnf/211_vfr_form_definition.md
> +++ b/2_vfr_description_in_bnf/211_vfr_form_definition.md
> @@ -2,6 +2,7 @@
> 2.11 VFR Form Definition
>
> Copyright (c) 2007-2017, Intel Corporation. All rights reserved.<BR>
> + (C) Copyright 2020 Hewlett Packard Enterprise Development LP<BR>
>
> Redistribution and use in source (original document form) and
'compiled'
> forms (converted to PDF, epub, HTML and other formats) with or without
> @@ -16,16 +17,7 @@
> notice, this list of conditions and the following disclaimer in the
> documentation and/or other materials provided with the distribution.
>
> - THIS DOCUMENTATION IS PROVIDED BY TIANOCORE PROJECT "AS IS"
> AND ANY EXPRESS OR
> - IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
> WARRANTIES OF
> - MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
> DISCLAIMED. IN NO
> - EVENT SHALL TIANOCORE PROJECT BE LIABLE FOR ANY DIRECT,
> INDIRECT, INCIDENTAL,
> - SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
> NOT LIMITED TO,
> - PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
> DATA, OR PROFITS;
> - OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY
> OF LIABILITY,
> - WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
> NEGLIGENCE OR
> - OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
> DOCUMENTATION, EVEN IF
> - ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
> + SPDX-License-Identifier: BSD-2-Clause-Patent
>
> -->
>
> @@ -786,6 +778,7 @@ oneofoptionFlagsField ::=
> | "INTERACTIVE"
> | "RESET_REQUIRED"
> | "DEFAULT"
> + | "REST_STYLE"
> ```
>
> #### BEHAVIORS AND RESTRICTIONS
> --
> 2.21.0.windows.1
[-- Attachment #2: Type: text/html, Size: 13359 bytes --]
next prev parent reply other threads:[~2020-11-10 1:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-09 15:45 [VFR REST_STYLE PATCH 1/1] VfrSpecification: Add REST_STYLE Abner Chang
2020-11-10 1:24 ` 回复: " gaoliming
2020-11-10 1:31 ` [edk2-devel] " Abner Chang
2020-11-10 1:32 ` gaoliming [this message]
2020-11-10 1:41 ` Abner Chang
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='008301d6b701$62b04da0$2810e8e0$@byosoft.com.cn' \
--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