From: "Tian, Feng" <feng.tian@intel.com>
To: "Wu, Hao A" <hao.a.wu@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Tian, Feng" <feng.tian@intel.com>
Subject: Re: [PATCH v2 00/10] Fix some bugs in NvmExpressDxe driver
Date: Tue, 6 Sep 2016 07:13:48 +0000 [thread overview]
Message-ID: <7F1BAD85ADEA444D97065A60D2E97EE566D86D82@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1472697187-16092-1-git-send-email-hao.a.wu@intel.com>
Looks good to me
Reviewed-by: Feng Tian <feng.tian@Intel.com>
Thanks
Feng
-----Original Message-----
From: Wu, Hao A
Sent: Thursday, September 1, 2016 10:33 AM
To: edk2-devel@lists.01.org; Tian, Feng <feng.tian@intel.com>
Cc: Wu, Hao A <hao.a.wu@intel.com>
Subject: [PATCH v2 00/10] Fix some bugs in NvmExpressDxe driver
Compared with V1 of the series, the following changes are made:
1. Add NamespaceId validity check in
EFI_NVM_EXPRESS_PASS_THRU_PROTOCOL.PassThru().
2. Fixes the issue that the caller event passed to
EFI_NVM_EXPRESS_PASS_THRU_PROTOCOL.PassThru() will not be signaled for
NVME Admin commands.
3. Set the non-blocking I/O feature support bit in structure
EFI_NVM_EXPRESS_PASS_THRU_MODE
Hao Wu (10):
MdeModulePkg NvmExpressDxe: Avoid crashing 'Mode' during OpenProtocol
MdeModulePkg NvmExpressDxe: Refine BuildDevicePath API to follow spec
MdeModulePkg NvmExpressDxe: Refine GetNameSpace API to follow spec
MdeModulePkg NvmExpressDxe: Refine GetNextNamespace API to follow spec
MdeModulePkg NvmExpressDxe: Add buffer alignment check in PassThru API
MdeModulePkg NvmExpressDxe: Add check on the attributes of NVME
controller
MdeModulePkg NvmExpressDxe: Add check for command packet in PassThru
MdeModulePkg NvmExpressDxe: Add NamespaceId validity check in PassThru
MdeModulePkg NvmExpressDxe: Fix 'Event' won't be signaled for Admin
cmds
MdeModulePkg NvmExpressDxe: Set the non-blocking I/O feature support
bit
MdeModulePkg/Bus/Pci/NvmExpressDxe/NvmExpress.c | 15 ++-
.../Bus/Pci/NvmExpressDxe/NvmExpressPassthru.c | 141 ++++++++++++++++-----
2 files changed, 118 insertions(+), 38 deletions(-)
--
1.9.5.msysgit.0
prev parent reply other threads:[~2016-09-06 7:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-01 2:32 [PATCH v2 00/10] Fix some bugs in NvmExpressDxe driver Hao Wu
2016-09-01 2:32 ` [PATCH v2 01/10] MdeModulePkg NvmExpressDxe: Avoid crashing 'Mode' during OpenProtocol Hao Wu
2016-09-01 2:32 ` [PATCH v2 02/10] MdeModulePkg NvmExpressDxe: Refine BuildDevicePath API to follow spec Hao Wu
2016-09-01 2:33 ` [PATCH v2 03/10] MdeModulePkg NvmExpressDxe: Refine GetNameSpace " Hao Wu
2016-09-01 2:33 ` [PATCH v2 04/10] MdeModulePkg NvmExpressDxe: Refine GetNextNamespace " Hao Wu
2016-09-01 2:33 ` [PATCH v2 05/10] MdeModulePkg NvmExpressDxe: Add buffer alignment check in PassThru API Hao Wu
2016-09-01 2:33 ` [PATCH v2 06/10] MdeModulePkg NvmExpressDxe: Add check on the attributes of NVME controller Hao Wu
2016-09-01 2:33 ` [PATCH v2 07/10] MdeModulePkg NvmExpressDxe: Add check for command packet in PassThru Hao Wu
2016-09-01 2:33 ` [PATCH v2 08/10] MdeModulePkg NvmExpressDxe: Add NamespaceId validity check " Hao Wu
2016-09-01 2:33 ` [PATCH v2 09/10] MdeModulePkg NvmExpressDxe: Fix 'Event' won't be signaled for Admin cmds Hao Wu
2016-09-01 2:33 ` [PATCH v2 10/10] MdeModulePkg NvmExpressDxe: Set the non-blocking I/O feature support bit Hao Wu
2016-09-06 7:13 ` Tian, Feng [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=7F1BAD85ADEA444D97065A60D2E97EE566D86D82@SHSMSX101.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