From: "Eric Jin" <eric.jin@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"supreeth.venkatesh@arm.com" <supreeth.venkatesh@arm.com>,
"nick.wang@insyde.com" <nick.wang@insyde.com>
Cc: "@intel.com >> Jin"
<IMCEAINVALID-+40intel+2Ecom+20+3E+3E+20Jin@arm.com>,
"Li, Ruth" <ruth.li@intel.com>,
"leon.chen@insyde.com" <leon.chen@insyde.com>,
"sunny.hsu@insyde.com >> sunny hsu" <sunny.hsu@insyde.com>
Subject: Re: [edk2-devel][edk2-test][PATCH] EFI/Protocol: Fix to use VENDOR_DEVICE_PATH to create the Debug port device node for DevicePath related protocol tests.
Date: Wed, 8 May 2019 01:12:04 +0000 [thread overview]
Message-ID: <DA72DC7456565B47808A57108259571F6379B9A1@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <50a025de5afcf410f6eca721346b24ca5a2e58ec.camel@arm.com>
Hi Nick,
Thank you for the patch.
Comments (same as Supreeth) as below.
1. Please add your email . E.g: Signed-off-by: Nick Wang <nick.wang@insyde.com>
2. replace 0x03 and 0x0a with meaningful macros. The macro can be defined in SctPkg/UEFI/Protocol/DevicePath.h
Best Regards
Eric
-----Original Message-----
From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Supreeth Venkatesh
Sent: Tuesday, May 7, 2019 12:42 AM
To: devel@edk2.groups.io; nick.wang@insyde.com
Cc: @intel.com >> Jin <IMCEAINVALID-+40intel+2Ecom+20+3E+3E+20Jin@arm.com>; Jin, Eric <eric.jin@intel.com>; Li, Ruth <ruth.li@intel.com>; leon.chen@insyde.com; sunny.hsu@insyde.com >> sunny hsu <sunny.hsu@insyde.com>
Subject: Re: [edk2-devel][edk2-test][PATCH] EFI/Protocol: Fix to use VENDOR_DEVICE_PATH to create the Debug port device node for DevicePath related protocol tests.
Hi Nick,
Thanks for the patch.
On Sun, 2019-05-05 at 22:10 -0500, via Groups.Io wrote:
> Follow edk2 tree hash: 9343d0a1cd09544686b14dba5b428d7bc811f6b9 to use
> VENDOR_DEVICE_PATH to create the Debug port device node.
>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Nick Wang
Please add your email E.g., Signed-off-by: Name <email>
> ---
> .../BlackBoxTest/DevicePathFromTextBBTestCoverage.c | 13 +++++++-----
> -
> .../BlackBoxTest/DevicePathToTextBBTestMain.c | 5 +++--
> 2 files changed, 10 insertions(+), 8 deletions(-)
>
> diff --git a/uefi-
> sct/SctPkg/TestCase/UEFI/EFI/Protocol/DevicePathFromText/BlackBoxTest
> /DevicePathFromTextBBTestCoverage.c b/uefi-
> sct/SctPkg/TestCase/UEFI/EFI/Protocol/DevicePathFromText/BlackBoxTest
> /DevicePathFromTextBBTestCoverage.c
> index 96cd84fd..56128f2a 100644
> --- a/uefi-
> sct/SctPkg/TestCase/UEFI/EFI/Protocol/DevicePathFromText/BlackBoxTest
> /DevicePathFromTextBBTestCoverage.c
> +++ b/uefi-
> sct/SctPkg/TestCase/UEFI/EFI/Protocol/DevicePathFromText/BlackBoxTest
> /DevicePathFromTextBBTestCoverage.c
> @@ -2,6 +2,7 @@
>
> Copyright 2006 - 2017 Unified EFI, Inc.
>
> Copyright (c) 2010 - 2018, Intel Corporation. All rights reserved.
>
> + Copyright (c) 2019, Insyde Software Corp. All Rights Reserved.
>
>
> This program and the accompanying materials are licensed and made
> available under the terms and conditions of the BSD License @@
> -1114,13 +1115,13 @@ CreateDebugPortDeviceNode ( IN CHAR16
> *TextDeviceNode
> )
> {
> - VENDOR_DEFINED_MESSAGING_DEVICE_PATH *Vend;
> + VENDOR_DEVICE_PATH *Vend;
>
> - Vend = (VENDOR_DEFINED_MESSAGING_DEVICE_PATH *) CreateDeviceNode (
> - DebugPortNodeType,
> - DebugPortNodeSubType,
> - sizeof(VENDOR_DEFINED_MESSAGING_DEVICE_PATH)
> - );
> + Vend = (VENDOR_DEVICE_PATH *) CreateDeviceNode ( DebugPortNodeType,
> + DebugPortNodeSubType,
> + sizeof(VENDOR_DEVICE_PATH)
> + );
> Vend->Guid = gBlackBoxEfiDebugPortProtocolGuid;
>
> return (EFI_DEVICE_PATH_PROTOCOL *) Vend; diff --git a/uefi-
> sct/SctPkg/TestCase/UEFI/EFI/Protocol/DevicePathToText/BlackBoxTest/D
> evicePathToTextBBTestMain.c b/uefi-
> sct/SctPkg/TestCase/UEFI/EFI/Protocol/DevicePathToText/BlackBoxTest/D
> evicePathToTextBBTestMain.c
> index d0809776..2fe58337 100644
> --- a/uefi-
> sct/SctPkg/TestCase/UEFI/EFI/Protocol/DevicePathToText/BlackBoxTest/D
> evicePathToTextBBTestMain.c
> +++ b/uefi-
> sct/SctPkg/TestCase/UEFI/EFI/Protocol/DevicePathToText/BlackBoxTest/D
> evicePathToTextBBTestMain.c
> @@ -2,6 +2,7 @@
>
> Copyright 2006 - 2017 Unified EFI, Inc.
>
> Copyright (c) 2010 - 2019, Intel Corporation. All rights reserved.
>
> + Copyright (c) 2019, Insyde Software Corp. All Rights Reserved.
>
>
> This program and the accompanying materials are licensed and made
> available under the terms and conditions of the BSD License @@ -1708,9
> +1709,9 @@ BuildDebugPortDeviceNode ( IN CHAR16 *TextDeviceNode
> )
> {
> - VENDOR_DEFINED_MESSAGING_DEVICE_PATH *Vend;
> + VENDOR_DEVICE_PATH *Vend;
>
> - Vend = (VENDOR_DEFINED_MESSAGING_DEVICE_PATH *) CreateDeviceNode
> (0x3, 0x0a, sizeof (VENDOR_DEFINED_MESSAGING_DEVICE_PATH));
> + Vend = (VENDOR_DEVICE_PATH *) CreateDeviceNode (0x3, 0x0a, sizeof
> (VENDOR_DEVICE_PATH));
Can you please define meaningful macros/constants for 0x03 and 0x0a (E.g., DebugNodeType, DebugNodeSubType) ?
>
>
> Vend->Guid = gBlackBoxEfiDebugPortProtocolGuid;
>
prev parent reply other threads:[~2019-05-08 1:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 3:10 [edk2-devel][edk2-test][PATCH] EFI/Protocol: Fix to use VENDOR_DEVICE_PATH to create the Debug port device node for DevicePath related protocol tests Nick Wang
2019-05-06 16:42 ` Supreeth Venkatesh
2019-05-08 1:12 ` Eric Jin [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=DA72DC7456565B47808A57108259571F6379B9A1@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