From: "Carsey, Jaben" <jaben.carsey@intel.com>
To: "Ni, Ruiyu" <ruiyu.ni@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [PATCH 0/2] Fix dynamic command cannot start in boot
Date: Tue, 28 Nov 2017 15:00:25 +0000 [thread overview]
Message-ID: <CB6E33457884FA40993F35157061515CA3BE18E9@FMSMSX103.amr.corp.intel.com> (raw)
In-Reply-To: <20171128120207.186068-1-ruiyu.ni@intel.com>
Reviewed-by: Jaben Carsey <jaben.carsey@intel.com>
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> Ruiyu Ni
> Sent: Tuesday, November 28, 2017 4:02 AM
> To: edk2-devel@lists.01.org
> Subject: [edk2] [PATCH 0/2] Fix dynamic command cannot start in boot
> Importance: High
>
> When dynamic command drivers are built into FV and start during
> boot, they fails. Because Shell protocol doesn't exist during boot.
> The patch changes both ShellLib and dynamic command drivers to fix
> the bug.
>
> Ruiyu Ni (2):
> ShellPkg/ShellLib: Fix dynamic command fails to start during boot
> ShellPkg/DynamicCommand: Fix bug that cannot start in boot
>
> .../DpDynamicCommand/DpDynamicCommand.c | 1 +
> .../TftpDynamicCommand/TftpDynamicCommand.c | 1 +
> ShellPkg/Library/UefiShellLib/UefiShellLib.c | 89 +++++++++++++---------
> ShellPkg/ShellPkg.dsc | 7 +-
> 4 files changed, 60 insertions(+), 38 deletions(-)
>
> --
> 2.15.0.gvfs.1.preview.4
>
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
prev parent reply other threads:[~2017-11-28 14:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 12:02 [PATCH 0/2] Fix dynamic command cannot start in boot Ruiyu Ni
2017-11-28 12:02 ` [PATCH 1/2] ShellPkg/ShellLib: Fix dynamic command fails to start during boot Ruiyu Ni
2017-11-28 12:02 ` [PATCH 2/2] ShellPkg/DynamicCommand: Fix bug that cannot start in boot Ruiyu Ni
2017-11-28 15:00 ` Carsey, Jaben [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=CB6E33457884FA40993F35157061515CA3BE18E9@FMSMSX103.amr.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