From: Hao Wu <hao.a.wu@intel.com>
To: edk2-devel@lists.01.org
Cc: Hao Wu <hao.a.wu@intel.com>,
Sean Brogan <sean.brogan@microsoft.com>,
Bret Barkelew <brbarkel@microsoft.com>,
Jian J Wang <jian.j.wang@intel.com>, Ray Ni <ray.ni@intel.com>
Subject: [PATCH v1 0/1] MdeModulePkg/NvmExpressDxe: Report StatusCode for device init failure
Date: Mon, 11 Feb 2019 08:05:03 +0800 [thread overview]
Message-ID: <20190211000504.13756-1-hao.a.wu@intel.com> (raw)
This patch is also available at:
https://github.com/hwu25/edk2/tree/nvme_status_code
Please refer to the log message of the patch for more details.
Cc: Sean Brogan <sean.brogan@microsoft.com>
Cc: Bret Barkelew <brbarkel@microsoft.com>
Cc: Jian J Wang <jian.j.wang@intel.com>
Cc: Ray Ni <ray.ni@intel.com>
Sean Brogan (1):
MdeModulePkg/NvmExpressDxe: Report StatusCode for device init failure
MdeModulePkg/Bus/Pci/NvmExpressDxe/NvmExpressDxe.inf | 3 ++-
MdeModulePkg/Bus/Pci/NvmExpressDxe/NvmExpress.h | 3 ++-
MdeModulePkg/Bus/Pci/NvmExpressDxe/NvmExpressHci.c | 10 +++++++++-
3 files changed, 13 insertions(+), 3 deletions(-)
--
2.12.0.windows.1
next reply other threads:[~2019-02-11 0:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 0:05 Hao Wu [this message]
2019-02-11 0:05 ` [PATCH v1 1/1] MdeModulePkg/NvmExpressDxe: Report StatusCode for device init failure Hao Wu
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=20190211000504.13756-1-hao.a.wu@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