public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ni, Ruiyu" <ruiyu.ni@intel.com>
To: "Wu, Hao A" <hao.a.wu@intel.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
	"Gao, Liming" <liming.gao@intel.com>
Cc: "Carsey, Jaben" <jaben.carsey@intel.com>
Subject: Re: [PATCH 14/17] ShellPkg DSC: Add build option to disable deprecated APIs
Date: Fri, 5 Aug 2016 01:32:07 +0000	[thread overview]
Message-ID: <734D49CCEBEEF84792F5B80ED585239D1ADB11A0@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1470358387-13996-15-git-send-email-hao.a.wu@intel.com>



Reviewed-by: Ruiyu Ni <ruiyu.ni@intel.com>
>-----Original Message-----
>From: Wu, Hao A
>Sent: Friday, August 5, 2016 8:53 AM
>To: edk2-devel@lists.01.org; Gao, Liming <liming.gao@intel.com>
>Cc: Wu, Hao A <hao.a.wu@intel.com>; Carsey, Jaben <jaben.carsey@intel.com>; Ni, Ruiyu <ruiyu.ni@intel.com>
>Subject: [PATCH 14/17] ShellPkg DSC: Add build option to disable deprecated APIs
>
>Add the following definition in the [BuildOptions] section in package DSC
>files to disable APIs that are deprecated:
>
>[BuildOptions]
>  *_*_*_CC_FLAGS = -D DISABLE_NEW_DEPRECATED_INTERFACES
>
>Cc: Jaben Carsey <jaben.carsey@intel.com>
>Cc: Ruiyu Ni <ruiyu.ni@intel.com>
>Contributed-under: TianoCore Contribution Agreement 1.0
>Signed-off-by: Hao Wu <hao.a.wu@intel.com>
>---
> ShellPkg/ShellPkg.dsc | 2 ++
> 1 file changed, 2 insertions(+)
>
>diff --git a/ShellPkg/ShellPkg.dsc b/ShellPkg/ShellPkg.dsc
>index 25c4fad..809bd42 100644
>--- a/ShellPkg/ShellPkg.dsc
>+++ b/ShellPkg/ShellPkg.dsc
>@@ -122,3 +122,5 @@
> !endif #$(NO_SHELL_PROFILES)
>   }
>
>+[BuildOptions]
>+  *_*_*_CC_FLAGS = -D DISABLE_NEW_DEPRECATED_INTERFACES
>--
>1.9.5.msysgit.0



  reply	other threads:[~2016-08-05  1:32 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-05  0:52 [PATCH 00/17] Add build option to disable deprecated APIs Hao Wu
2016-08-05  0:52 ` [PATCH 01/17] FatPkg DSC: " Hao Wu
2016-08-05  1:31   ` Ni, Ruiyu
2016-08-05  0:52 ` [PATCH 02/17] IntelFrameworkModulePkg " Hao Wu
2016-08-08  2:35   ` Gao, Liming
2016-08-05  0:52 ` [PATCH 03/17] IntelFrameworkPkg " Hao Wu
2016-08-08  2:35   ` Gao, Liming
2016-08-05  0:52 ` [PATCH 04/17] IntelFsp2Pkg " Hao Wu
2016-08-05  0:55   ` Yao, Jiewen
2016-08-05  0:52 ` [PATCH 05/17] IntelFsp2WrapperPkg " Hao Wu
2016-08-05  0:52 ` [PATCH 06/17] IntelFspPkg " Hao Wu
2016-08-05  0:52 ` [PATCH 07/17] IntelFspWrapperPkg " Hao Wu
2016-08-05  0:52 ` [PATCH 08/17] MdeModulePkg " Hao Wu
2016-08-05  1:00   ` Zeng, Star
2016-08-05  2:45   ` Tian, Feng
2016-08-05  0:52 ` [PATCH 09/17] MdePkg " Hao Wu
2016-08-08  2:34   ` Gao, Liming
2016-08-05  0:53 ` [PATCH 10/17] NetworkPkg " Hao Wu
2016-08-05  5:32   ` Wu, Jiaxin
2016-08-05  0:53 ` [PATCH 11/17] PcAtChipsetPkg " Hao Wu
2016-08-05  1:31   ` Ni, Ruiyu
2016-08-05  0:53 ` [PATCH 12/17] PerformancePkg " Hao Wu
2016-08-08  2:34   ` Gao, Liming
2016-08-05  0:53 ` [PATCH 13/17] SecurityPkg " Hao Wu
2016-08-05  2:47   ` Zhang, Chao B
2016-08-05  0:53 ` [PATCH 14/17] ShellPkg " Hao Wu
2016-08-05  1:32   ` Ni, Ruiyu [this message]
2016-08-05  0:53 ` [PATCH 15/17] SourceLevelDebugPkg " Hao Wu
2016-08-05  4:32   ` Ni, Ruiyu
2016-08-05  0:53 ` [PATCH 16/17] UefiCpuPkg " Hao Wu
2016-08-05  5:20   ` Tian, Feng
2016-08-05  0:53 ` [PATCH 17/17] CryptoPkg " Hao Wu
2016-08-05  2:53   ` Long, Qin
2016-08-05  2:59   ` Ye, Ting

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=734D49CCEBEEF84792F5B80ED585239D1ADB11A0@SHSMSX103.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