From: "Ni, Ruiyu" <ruiyu.ni@intel.com>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: "Carsey, Jaben" <jaben.carsey@intel.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [PATCH v2 2/3] ShellPkg/tftp: Convert from NULL class library to Dynamic Command
Date: Tue, 28 Nov 2017 07:40:05 +0000 [thread overview]
Message-ID: <734D49CCEBEEF84792F5B80ED585239D5BAD41C1@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <CAKv+Gu9Qsg+JpAzHzWx9q3LMT1dLAuvHpcM-VfjS92GkOt2Nqg@mail.gmail.com>
I just realized OVMF platform is referencing the INF.
I will search in all edkII code.
Thanks/Ray
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> Ard Biesheuvel
> Sent: Tuesday, November 28, 2017 3:35 PM
> To: Ni, Ruiyu <ruiyu.ni@intel.com>
> Cc: Carsey, Jaben <jaben.carsey@intel.com>; Kinney, Michael D
> <michael.d.kinney@intel.com>; edk2-devel@lists.01.org
> Subject: Re: [edk2] [PATCH v2 2/3] ShellPkg/tftp: Convert from NULL class
> library to Dynamic Command
>
> On 27 November 2017 at 05:55, Ruiyu Ni <ruiyu.ni@intel.com> wrote:
> > UEFI Shell spec defines Shell Dynamic Command protocol which is just
> > for the purpose to extend internal command.
> > So tftp command is changed from NULL class library to be a driver
> > producing DynamicCommand protocol.
> >
> > The guideline is:
> > 1. Only use NULL class library for Shell spec defined commands.
> > 2. New commands can be provided as not only a standalone application
> > but also a dynamic command. So it can be used either as an
> > internal command, but also as a standalone application.
> >
> > TftpApp.inf is to provide a standalone application.
> > TftpDynamicCommand.inf is to provide a standalone driver producing
> > Dynamic Command protocol.
> >
> > Contributed-under: TianoCore Contribution Agreement 1.1
> > Signed-off-by: Ruiyu Ni <ruiyu.ni@intel.com>
> > Cc: Jaben Carsey <jaben.carsey@intel.com>
> > Cc: Michael D Kinney <michael.d.kinney@intel.com>
> > ---
> > .../TftpDynamicCommand}/Tftp.c | 92 +++++++++++----
> > .../TftpDynamicCommand/Tftp.h} | 40 +++++--
> > .../TftpDynamicCommand/Tftp.uni} | 0
> > .../DynamicCommand/TftpDynamicCommand/TftpApp.c | 54
> +++++++++
> > .../TftpDynamicCommand/TftpApp.inf} | 34 +++---
> > .../TftpDynamicCommand/TftpDynamicCommand.c | 131
> +++++++++++++++++++++
> > .../TftpDynamicCommand/TftpDynamicCommand.inf} | 39 +++---
> > .../UefiShellTftpCommandLib.c | 97 ---------------
> > ShellPkg/ShellPkg.dsc | 11 +-
> > 9 files changed, 325 insertions(+), 173 deletions(-)
>
> Please make sure that you fix platforms that use .inf files when renaming
> them.
> The ArmVirtQemu build is currently broken due to this patch.
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2017-11-28 7:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 5:55 [PATCH v2 0/3] Convert from NULL class library to Dynamic Command Ruiyu Ni
2017-11-27 5:55 ` [PATCH v2 1/3] ShellPkg/ShellLib: Constructor doesn't depend on ShellParameters Ruiyu Ni
2017-11-27 5:55 ` [PATCH v2 2/3] ShellPkg/tftp: Convert from NULL class library to Dynamic Command Ruiyu Ni
2017-11-28 7:34 ` Ard Biesheuvel
2017-11-28 7:40 ` Ni, Ruiyu [this message]
2017-11-27 5:55 ` [PATCH v2 3/3] ShellPkg/dp: " Ruiyu Ni
2017-11-27 14:59 ` Carsey, Jaben
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=734D49CCEBEEF84792F5B80ED585239D5BAD41C1@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