public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Zeng, Star" <star.zeng@intel.com>
To: "Ni, Ruiyu" <ruiyu.ni@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Zeng, Star" <star.zeng@intel.com>
Subject: Re: [PATCH v2 0/4] Fix a bug that prevents PMEM access
Date: Tue, 25 Sep 2018 12:12:15 +0000	[thread overview]
Message-ID: <0C09AFA07DD0434D9E2A0C6AEB0483103BBEEF00@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <20180925062117.34772-1-ruiyu.ni@intel.com>

Reviewed-by: Star Zeng <star.zeng@intel.com> with Laszlo's minor comment handled.

Thanks,
Star
-----Original Message-----
From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Ruiyu Ni
Sent: Tuesday, September 25, 2018 2:21 PM
To: edk2-devel@lists.01.org
Subject: [edk2] [PATCH v2 0/4] Fix a bug that prevents PMEM access

The patch sets fix a bug in PciHostBridge driver that prevents PMEM access sometimes. Additionally, it enhances the boundary check and add a new macro to simplify the code.

V2: Patch 3/4 uses Resource as parameter instead of R and treat the parameter
              as a pointer.
    Patch 4/4 is a new patch suggested by Star to move declaration of mIoMmu to
              header file.

Ruiyu Ni (4):
  MdeModulePkg/PciHostBridge: Enhance boundary check in
    Io/Mem.Read/Write
  MdeModulePkg/PciHostBridge: Fix a bug that prevents PMEM access
  MdeModulePkg/PciHostBridge: Add RESOURCE_VALID() to simplify code
  MdeModulePkg/PciHostBridge: Move declaration of mIoMmu to header file

 .../Bus/Pci/PciHostBridgeDxe/PciHostBridge.c       |   4 +-
 .../Bus/Pci/PciHostBridgeDxe/PciHostBridge.h       |   3 +
 .../Bus/Pci/PciHostBridgeDxe/PciRootBridge.h       |   1 -
 .../Bus/Pci/PciHostBridgeDxe/PciRootBridgeIo.c     | 126 ++++++++++++---------
 4 files changed, 78 insertions(+), 56 deletions(-)

--
2.16.1.windows.1

_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel


      parent reply	other threads:[~2018-09-25 12:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-25  6:21 [PATCH v2 0/4] Fix a bug that prevents PMEM access Ruiyu Ni
2018-09-25  6:21 ` [PATCH v2 1/4] MdeModulePkg/PciHostBridge: Enhance boundary check in Io/Mem.Read/Write Ruiyu Ni
2018-09-25  6:21 ` [PATCH v2 2/4] MdeModulePkg/PciHostBridge: Fix a bug that prevents PMEM access Ruiyu Ni
2018-09-25  6:21 ` [PATCH v2 3/4] MdeModulePkg/PciHostBridge: Add RESOURCE_VALID() to simplify code Ruiyu Ni
2018-09-25  6:21 ` [PATCH v2 4/4] MdeModulePkg/PciHostBridge: Move declaration of mIoMmu to header file Ruiyu Ni
2018-09-25 10:43   ` Laszlo Ersek
2018-09-25 10:44   ` Laszlo Ersek
2018-09-25 12:12 ` Zeng, Star [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=0C09AFA07DD0434D9E2A0C6AEB0483103BBEEF00@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