From: "Yao, Jiewen" <jiewen.yao@intel.com>
To: "Zeng, Star" <star.zeng@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Ni, Ruiyu" <ruiyu.ni@intel.com>,
"Gao, Liming" <liming.gao@intel.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [PATCH 0/3] Correct function description for ALLOCATE_BUFFER
Date: Mon, 11 Dec 2017 07:10:42 +0000 [thread overview]
Message-ID: <74D8A39837DF1E4DA445A8C0B3885C503AA418C6@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <1512975222-8048-1-git-send-email-star.zeng@intel.com>
Reviewed-by: Jiewen.yao@intel.com
> -----Original Message-----
> From: Zeng, Star
> Sent: Monday, December 11, 2017 2:54 PM
> To: edk2-devel@lists.01.org
> Cc: Zeng, Star <star.zeng@intel.com>; Yao, Jiewen <jiewen.yao@intel.com>; Ni,
> Ruiyu <ruiyu.ni@intel.com>; Gao, Liming <liming.gao@intel.com>; Kinney,
> Michael D <michael.d.kinney@intel.com>
> Subject: [PATCH 0/3] Correct function description for ALLOCATE_BUFFER
>
> According to UEFI spec, DUAL_ADDRESS_CYCLE is missing in the
> EFI_UNSUPPORTED return status description for ALLOCATE_BUFFER interface.
> Same issue is also in IOMMU interface.
>
> Cc: Jiewen Yao <jiewen.yao@intel.com>
> Cc: Ruiyu Ni <ruiyu.ni@intel.com>
> Cc: Liming Gao <liming.gao@intel.com>
> Cc: Michael D Kinney <michael.d.kinney@intel.com>
>
> Star Zeng (3):
> MdePkg PciIo.h: Correct function description for ALLOCATE_BUFFER
> MdeModulePkg: Correct function description for AllocateBuffer
> IntelSilicon: Correct function description for AllocateBuffer
>
> IntelSiliconPkg/Feature/VTd/IntelVTdDxe/BmDma.c | 2 +-
> IntelSiliconPkg/Feature/VTd/IntelVTdDxe/IntelVTdDxe.c | 2 +-
> IntelSiliconPkg/Feature/VTd/IntelVTdPmrPei/IntelVTdPmrPei.c | 2 +-
> MdeModulePkg/Bus/Pci/PciBusDxe/PciIo.c | 4 ++--
> MdeModulePkg/Bus/Pci/PciBusDxe/PciIo.h | 4 ++--
> MdeModulePkg/Include/Ppi/IoMmu.h | 2 +-
> MdeModulePkg/Include/Protocol/IoMmu.h | 2 +-
> MdePkg/Include/Protocol/PciIo.h | 4 ++--
> 8 files changed, 11 insertions(+), 11 deletions(-)
>
> --
> 2.7.0.windows.1
prev parent reply other threads:[~2017-12-11 7:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-11 6:53 [PATCH 0/3] Correct function description for ALLOCATE_BUFFER Star Zeng
2017-12-11 6:53 ` [PATCH 1/3] MdePkg PciIo.h: " Star Zeng
2017-12-11 6:53 ` [PATCH 2/3] MdeModulePkg: Correct function description for AllocateBuffer Star Zeng
2017-12-11 6:53 ` [PATCH 3/3] IntelSilicon: " Star Zeng
2017-12-11 6:56 ` [PATCH 0/3] Correct function description for ALLOCATE_BUFFER Ni, Ruiyu
2017-12-11 7:10 ` Yao, Jiewen [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=74D8A39837DF1E4DA445A8C0B3885C503AA418C6@shsmsx102.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