From: "Gao, Liming" <liming.gao@intel.com>
To: "Wang, Jian J" <jian.j.wang@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [PATCH v2 0/2] Add sanity check for FilePath device path
Date: Tue, 19 Feb 2019 09:23:03 +0000 [thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E3E1749@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <20190219092139.844-1-jian.j.wang@intel.com>
Reviewed-by: Liming Gao <liming.gao@intel.com>
>-----Original Message-----
>From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Jian
>J Wang
>Sent: Tuesday, February 19, 2019 5:22 PM
>To: edk2-devel@lists.01.org
>Subject: [edk2] [PATCH v2 0/2] Add sanity check for FilePath device path
>
>> v2: fix wrong detection of FilePath device path
>
>REF: https://bugzilla.tianocore.org/show_bug.cgi?id=1497
>
>Tests
>- Pass specific DevicePathLib test cases
>- Boot shell
>- Boot to Fedora 26 (Qemu/x64)
>- Boot to Ubuntu 18.04 (Qemu/x64)
>- Boot to Windows 10 (Qemu/x64)
>- Boot to Windows 7 (Qemu/x64)
>
>Jian J Wang (2):
> MdePkg/UefiDevicePathLib: Add sanity check for FilePath device path
> MdePkg/UefiDevicePathLibDevicePathProtocol: Add sanity check for
> FilePath device path
>
> MdePkg/Library/UefiDevicePathLib/DevicePathUtilities.c | 9 +++++++++
> .../UefiDevicePathLib.c | 9 +++++++++
> 2 files changed, 18 insertions(+)
>
>--
>2.17.1.windows.2
>
>_______________________________________________
>edk2-devel mailing list
>edk2-devel@lists.01.org
>https://lists.01.org/mailman/listinfo/edk2-devel
prev parent reply other threads:[~2019-02-19 9:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-19 9:21 [PATCH v2 0/2] Add sanity check for FilePath device path Jian J Wang
2019-02-19 9:21 ` [PATCH v2 1/2] MdePkg/UefiDevicePathLib: " Jian J Wang
2019-02-19 9:34 ` Ni, Ray
2019-02-19 10:12 ` Wang, Jian J
2019-02-19 13:11 ` Ni, Ray
2019-02-19 9:21 ` [PATCH v2 2/2] MdePkg/UefiDevicePathLibDevicePathProtocol: " Jian J Wang
2019-02-19 9:23 ` Gao, Liming [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=4A89E2EF3DFEDB4C8BFDE51014F606A14E3E1749@SHSMSX104.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