public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Carsey, Jaben" <jaben.carsey@intel.com>
To: "Yao, Jiewen" <jiewen.yao@intel.com>,
	Tim Lewis <tim.lewis@insyde.com>,
	"Ni, Ruiyu" <ruiyu.ni@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Carsey, Jaben" <jaben.carsey@intel.com>
Subject: Re: [PATCH 0/5] Move Shell protocol definitions to MdePkg
Date: Mon, 17 Oct 2016 16:30:27 +0000	[thread overview]
Message-ID: <CB6E33457884FA40993F35157061515C54A90DEC@FMSMSX103.amr.corp.intel.com> (raw)
In-Reply-To: <74D8A39837DF1E4DA445A8C0B3885C50386B1CEE@shsmsx102.ccr.corp.intel.com>

Yao,

How many closed source packages are going to be working against the trunk?  Don't most of those platforms already have a copy of ShellPkg and therefore they wont care?

-Jaben

> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> Yao, Jiewen
> Sent: Saturday, October 15, 2016 6:30 AM
> To: Tim Lewis <tim.lewis@insyde.com>; Ni, Ruiyu <ruiyu.ni@intel.com>;
> edk2-devel@lists.01.org
> Subject: Re: [edk2] [PATCH 0/5] Move Shell protocol definitions to MdePkg
> Importance: High
> 
> Of course, it is fine to give a good name in MdePkg. :)
> 
> My concern is only about "Compatibility".
> This series patch only updated ArmPkg and EmbeddedPkg.
> But there might be more close source IP protected packages using the
> original header file.
> 
> That is why I propose a compatible way: We give a good file name in MdePkg.
> At same time, we can keep the old file name in ShellPkg to include the good
> name in MdePkg.
> 
> I recommend we give a solution to make close source package unchanged
> after this patch is applied.
> 
> Thank you
> Yao Jiewen
> 
> 
> From: Tim Lewis [mailto:tim.lewis@insyde.com]
> Sent: Saturday, October 15, 2016 12:21 AM
> To: Yao, Jiewen <jiewen.yao@intel.com>; Ni, Ruiyu <ruiyu.ni@intel.com>;
> edk2-devel@lists.01.org
> Subject: RE: [edk2] [PATCH 0/5] Move Shell protocol definitions to MdePkg
> 
> I prefer the renamed .h file, even though I have substantial investment in
> the current infrastructure.
> 
> Why? Because engineers don't have time to remember "how does protocol
> X translate to header file Y" It should be a consistent rule. How many times
> have I needed to grep the header file name just because I got a build error
> because the rule wasn't predictable.
> 
> 1) remove the EFI_ prefix and the _PROTOCOL  suffix
> (EFI_BLOCK_IO_PROTOCOL -> BLOCK_IO
> 2) Convert to upper-and-lower case, BLOCK_IO -> Block_Io
> 3) Remove the _ (Block_Io -> BlockIo)
> 4)  add a .h BlockIo -> BlockIo.h
> 
> Most protocol and PPI header files already follow this rule. The current
> header files for shell are among the few exceptions, because they don't
> follow this.
> 
> Tim
> 
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> Yao, Jiewen
> Sent: Friday, October 14, 2016 6:14 AM
> To: Yao, Jiewen <jiewen.yao@intel.com<mailto:jiewen.yao@intel.com>>;
> Ni, Ruiyu <ruiyu.ni@intel.com<mailto:ruiyu.ni@intel.com>>; edk2-
> devel@lists.01.org<mailto:edk2-devel@lists.01.org>
> Subject: Re: [edk2] [PATCH 0/5] Move Shell protocol definitions to MdePkg
> 
> Or if you really think we should give a better name.
> 
> My recommendation is:
> 
> 1)      We add content in MdePkg.
> 
> 2)      We can keep the old protocol file in ShellPkg, but let .h in shellPkg
> include the .h in MdePkg.
> 
> Then we can avoid duplicated code and make it a compatible solution to
> avoid other module update.
> 
> Thank you
> Yao Jiewen
> 
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> Yao, Jiewen
> Sent: Friday, October 14, 2016 9:09 PM
> To: Ni, Ruiyu <ruiyu.ni@intel.com<mailto:ruiyu.ni@intel.com>>; edk2-
> devel@lists.01.org<mailto:edk2-devel@lists.01.org>
> Subject: Re: [edk2] [PATCH 0/5] Move Shell protocol definitions to MdePkg
> 
> Hi
> I think the requests is just to *move*.
> 
> There is no request to *rename*.
> 
> Can we just move to avoid other update?
> 
> 
> > -----Original Message-----
> > From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> > Ruiyu Ni
> > Sent: Friday, October 14, 2016 5:44 PM
> > To: edk2-devel@lists.01.org<mailto:edk2-devel@lists.01.org<mailto:edk2-
> devel@lists.01.org%3cmailto:edk2-devel@lists.01.org>>
> > Subject: [edk2] [PATCH 0/5] Move Shell protocol definitions to MdePkg
> >
> > The patches moves Shell spec defined protocol definitions to MdePkg
> > and updates all references.
> > Content of ShellBase.h is moved to Protocol/Shell.h and ShellBase.h is
> > removed.
> >
> > Ruiyu Ni (5):
> >   ShellPkg: Move SHELL_FREE_NON_NULL from ShellBase.h to ShellLib.h
> >   MdePkg: Include Shell/ShellDynamicCommand/ShellParameters
> > definitions
> >   ArmPkg/LinuxLoader: Reference Shell protocols in MdePkg
> >   EmbeddedPkg/FdtPlatformDxe: Reference Shell protocols in MdePkg
> >   ShellPkg: Remove Shell/ShellDynamicCommand/ShellParameter
> > definitions
> >
> >  ArmPkg/Application/LinuxLoader/LinuxLoader.h       |   4 +-
> >  EmbeddedPkg/Drivers/FdtPlatformDxe/FdtPlatform.h   |   4 +-
> >  .../EfiShell.h => MdePkg/Include/Protocol/Shell.h  | 134
> > +++++++++++++++++-
> >  .../Include/Protocol/ShellDynamicCommand.h         |   7 +-
> >  .../Include/Protocol/ShellParameters.h             |   4 +-
> >  MdePkg/MdePkg.dec                                  |  15 ++
> >  ShellPkg/Application/Shell/Shell.h                 |   5 +-
> >  ShellPkg/Include/Library/ShellCommandLib.h         |   5 +-
> >  ShellPkg/Include/Library/ShellLib.h                |  14 +-
> >  ShellPkg/Include/ShellBase.h                       | 157
> > ---------------------
> >  ShellPkg/Library/UefiDpLib/Dp.h                    |   3 +-
> >  ShellPkg/Library/UefiDpLib/UefiDpLib.h             |   7 +-
> >  .../UefiHandleParsingLib/UefiHandleParsingLib.h    |   8 +-
> >  .../UefiShellBcfgCommandLib.c                      |   5 +-
> >  .../UefiShellCEntryLib/UefiShellCEntryLib.c        |   6 +-
> >  .../UefiShellCommandLib/UefiShellCommandLib.h      |   7 +-
> >  .../Library/UefiShellDebug1CommandsLib/Compress.c  |   7 +-
> >  .../UefiShellDebug1CommandsLib.h                   |   7 +-
> >  .../UefiShellDriver1CommandsLib.h                  |   7 +-
> >  .../UefiShellLevel1CommandsLib.h                   |   7 +-
> >  .../UefiShellLevel2CommandsLib.h                   |   7 +-
> >  ShellPkg/Library/UefiShellLevel3CommandsLib/Help.c |   2 +-
> >  .../UefiShellLevel3CommandsLib.h                   |   7 +-
> >  ShellPkg/Library/UefiShellLib/UefiShellLib.c       |   1 -
> >  ShellPkg/Library/UefiShellLib/UefiShellLib.h       |   6 +-
> >  .../UefiShellNetwork1CommandsLib.h                 |   3 +-
> >  .../UefiShellTftpCommandLib.h                      |   3 +-
> >  ShellPkg/ShellPkg.dec                              |   3 -
> >  ShellPkg/ShellPkg.dsc                              |   2 +
> >  29 files changed, 213 insertions(+), 234 deletions(-)  rename
> > ShellPkg/Include/Protocol/EfiShell.h =>
> > MdePkg/Include/Protocol/Shell.h (92%)  rename
> > ShellPkg/Include/Protocol/EfiShellDynamicCommand.h =>
> > MdePkg/Include/Protocol/ShellDynamicCommand.h (92%)  rename
> > ShellPkg/Include/Protocol/EfiShellParameters.h =>
> > MdePkg/Include/Protocol/ShellParameters.h (92%)  delete mode 100644
> > ShellPkg/Include/ShellBase.h
> >
> > --
> > 2.9.0.windows.1
> >
> > _______________________________________________
> > edk2-devel mailing list
> > edk2-devel@lists.01.org<mailto:edk2-devel@lists.01.org<mailto:edk2-
> devel@lists.01.org%3cmailto:edk2-devel@lists.01.org>>
> > https://lists.01.org/mailman/listinfo/edk2-devel
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org<mailto:edk2-devel@lists.01.org<mailto:edk2-
> devel@lists.01.org%3cmailto:edk2-devel@lists.01.org>>
> https://lists.01.org/mailman/listinfo/edk2-devel
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org<mailto:edk2-devel@lists.01.org>
> https://lists.01.org/mailman/listinfo/edk2-devel
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel


      reply	other threads:[~2016-10-17 16:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-14  9:44 [PATCH 0/5] Move Shell protocol definitions to MdePkg Ruiyu Ni
2016-10-14  9:44 ` [PATCH 1/5] ShellPkg: Move SHELL_FREE_NON_NULL from ShellBase.h to ShellLib.h Ruiyu Ni
2016-10-14 16:22   ` Tim Lewis
2016-10-17 16:25   ` Carsey, Jaben
2016-10-14  9:44 ` [PATCH 2/5] MdePkg: Include Shell/ShellDynamicCommand/ShellParameters definitions Ruiyu Ni
2016-10-17 18:02   ` Carsey, Jaben
2016-10-18  5:56     ` Ni, Ruiyu
2016-10-18  5:59       ` Kinney, Michael D
2016-10-18 15:19         ` Brian J. Johnson
2016-10-14  9:44 ` [PATCH 3/5] ArmPkg/LinuxLoader: Reference Shell protocols in MdePkg Ruiyu Ni
2016-10-14 19:55   ` Leif Lindholm
2016-10-14  9:44 ` [PATCH 4/5] EmbeddedPkg/FdtPlatformDxe: " Ruiyu Ni
2016-10-14 19:55   ` Leif Lindholm
2016-10-14  9:44 ` [PATCH 5/5] ShellPkg: Remove Shell/ShellDynamicCommand/ShellParameter definitions Ruiyu Ni
2016-10-14 13:08 ` [PATCH 0/5] Move Shell protocol definitions to MdePkg Yao, Jiewen
2016-10-14 13:13   ` Yao, Jiewen
2016-10-14 16:21     ` Tim Lewis
2016-10-15 13:29       ` Yao, Jiewen
2016-10-17 16:30         ` 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=CB6E33457884FA40993F35157061515C54A90DEC@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