From: "Ni, Ruiyu" <ruiyu.ni@intel.com>
To: "Carsey, Jaben" <jaben.carsey@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [PATCH] ShellPkg/ShellPkg.dec: Change comments for PcdShellLibAutoInitialize
Date: Sat, 2 Dec 2017 09:08:53 +0000 [thread overview]
Message-ID: <734D49CCEBEEF84792F5B80ED585239D5BADC65A@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <CB6E33457884FA40993F35157061515CA3BE7C87@FMSMSX103.amr.corp.intel.com>
That's fine. Faster than me in the review response.
> -----Original Message-----
> From: Carsey, Jaben
> Sent: Saturday, December 2, 2017 1:00 AM
> To: Ni, Ruiyu <ruiyu.ni@intel.com>; edk2-devel@lists.01.org
> Subject: RE: [PATCH] ShellPkg/ShellPkg.dec: Change comments for
> PcdShellLibAutoInitialize
>
> Apologies for delay. I missed the email on first pass.
>
> Reviewed-by: Jaben Carsey <jaben.carsey@intel.com>
>
> > -----Original Message-----
> > From: Ni, Ruiyu
> > Sent: Wednesday, November 29, 2017 12:22 AM
> > To: edk2-devel@lists.01.org
> > Cc: Carsey, Jaben <jaben.carsey@intel.com>
> > Subject: [PATCH] ShellPkg/ShellPkg.dec: Change comments for
> > PcdShellLibAutoInitialize
> > Importance: High
> >
> > When Dynamic command drivers links to ShellLib, the ShellLib
> > constructor shouldn't be called because the Shell and ShellParameters
> > protocols don't exist when the driver starts.
> > So it's required to set PcdShellLibAutoInitialize to FALSE for dynamic
> > command drivers.
> > Update the comments in DEC file to describe such requirement for this
> > PCD.
> >
> > Contributed-under: TianoCore Contribution Agreement 1.1
> > Signed-off-by: Ruiyu Ni <ruiyu.ni@intel.com>
> > Cc: Jaben Carsey <jaben.carsey@intel.com>
> > ---
> > ShellPkg/ShellPkg.dec | 1 +
> > 1 file changed, 1 insertion(+)
> >
> > diff --git a/ShellPkg/ShellPkg.dec b/ShellPkg/ShellPkg.dec index
> > 5859c49033..48d50b87b3 100644
> > --- a/ShellPkg/ShellPkg.dec
> > +++ b/ShellPkg/ShellPkg.dec
> > @@ -81,6 +81,7 @@ [PcdsFeatureFlag]
> > [PcdsFixedAtBuild]
> > ## This flag is used to control initialization of the shell library
> > # This should be FALSE for compiling the shell application itself only.
> > + # This should be FALSE for compiling the dynamic command drivers.
> >
> > gEfiShellPkgTokenSpaceGuid.PcdShellLibAutoInitialize|TRUE|BOOLEAN|0x00
> > 000005
> >
> > ## This is the max buffer for ShellLib and internal Shell printings.
> > --
> > 2.15.0.gvfs.1.preview.4
prev parent reply other threads:[~2017-12-02 9:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-29 8:22 [PATCH] ShellPkg/ShellPkg.dec: Change comments for PcdShellLibAutoInitialize Ruiyu Ni
2017-12-01 17:00 ` Carsey, Jaben
2017-12-02 9:08 ` Ni, Ruiyu [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=734D49CCEBEEF84792F5B80ED585239D5BADC65A@SHSMSX104.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