public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Zhang, Shenglei" <shenglei.zhang@intel.com>
To: devel@edk2.groups.io
Cc: Chasel Chiu <chasel.chiu@intel.com>,
	Nate DeSimone <nathaniel.l.desimone@intel.com>,
	Star Zeng <star.zeng@intel.com>
Subject: [PATCH 3/3] IntelFsp2Pkg/FspSecCore: Add missing header file in INF file
Date: Thu,  8 Aug 2019 14:24:56 +0800	[thread overview]
Message-ID: <20190808062456.6116-4-shenglei.zhang@intel.com> (raw)
In-Reply-To: <20190808062456.6116-1-shenglei.zhang@intel.com>

SecFsp.h is used but missing inf file, which will cause generating
warning message.

Cc: Chasel Chiu <chasel.chiu@intel.com>
Cc: Nate DeSimone <nathaniel.l.desimone@intel.com>
Cc: Star Zeng <star.zeng@intel.com>
Signed-off-by: Shenglei Zhang <shenglei.zhang@intel.com>
---
 IntelFsp2Pkg/FspSecCore/FspSecCoreS.inf | 1 +
 1 file changed, 1 insertion(+)

diff --git a/IntelFsp2Pkg/FspSecCore/FspSecCoreS.inf b/IntelFsp2Pkg/FspSecCore/FspSecCoreS.inf
index 3de09b5b4921..86d3d31d3269 100644
--- a/IntelFsp2Pkg/FspSecCore/FspSecCoreS.inf
+++ b/IntelFsp2Pkg/FspSecCore/FspSecCoreS.inf
@@ -22,6 +22,7 @@ [Defines]
 
 [Sources]
   SecFspApiChk.c
+  SecFsp.h
 
 [Sources.IA32]
   Ia32/Stack.nasm
-- 
2.18.0.windows.1


  parent reply	other threads:[~2019-08-08  6:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-08  6:24 [PATCH 0/3] Fix warning message issues Zhang, Shenglei
2019-08-08  6:24 ` [PATCH 1/3] MdeModulePkg: Add missing header files in INF files Zhang, Shenglei
2019-08-12  1:59   ` [edk2-devel] " Wu, Hao A
2019-08-12  5:19     ` Zhang, Shenglei
2019-08-08  6:24 ` [PATCH 2/3] ShellPkg/UefiShellAcpiViewCommandLib: Add missing header files in INF Zhang, Shenglei
2019-08-08  8:58   ` [edk2-devel] " Gao, Zhichao
2019-08-08 14:51     ` Carsey, Jaben
2019-08-08  6:24 ` Zhang, Shenglei [this message]
2019-08-08  6:58   ` [PATCH 3/3] IntelFsp2Pkg/FspSecCore: Add missing header file in INF file Chiu, Chasel
2019-08-08 14:56     ` Zeng, Star
2019-08-08 20:47       ` Nate DeSimone

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=20190808062456.6116-4-shenglei.zhang@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