From: Patrick Georgi <pgeorgi@google.com>
To: edk2-devel@lists.01.org
Cc: Patrick Georgi <pgeorgi@google.com>
Subject: [PATCH 2/3] IntelFsp2Pkg: Fix typo in SplitFspBin
Date: Tue, 18 Sep 2018 09:32:02 -0400 [thread overview]
Message-ID: <20180918133203.192779-2-pgeorgi@google.com> (raw)
In-Reply-To: <20180918133203.192779-1-pgeorgi@google.com>
Signed-off-by: Patrick Georgi <pgeorgi@google.com>
Contributed-under: TianoCore Contribution Agreement 1.1
---
IntelFsp2Pkg/Tools/SplitFspBin.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/IntelFsp2Pkg/Tools/SplitFspBin.py b/IntelFsp2Pkg/Tools/SplitFspBin.py
index bd5507c2fa..ac864492e8 100755
--- a/IntelFsp2Pkg/Tools/SplitFspBin.py
+++ b/IntelFsp2Pkg/Tools/SplitFspBin.py
@@ -726,7 +726,7 @@ def SplitFspBin (fspfile, outdir, nametemplate):
fspname, ext = os.path.splitext(os.path.basename(nametemplate))
filename = os.path.join(outdir, fspname + '_' + fsp.Type + ext)
hfsp = open(filename, 'wb')
- print ("Ceate FSP component file '%s'" % filename)
+ print ("Create FSP component file '%s'" % filename)
for fvidx in fsp.FvIdxList:
fv = fd.FvList[fvidx]
hfsp.write(fv.FvData)
--
2.19.0.397.gdd90340f6a-goog
next prev parent reply other threads:[~2018-09-18 13:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-18 13:32 [PATCH 1/3] IntelFsp2Pkg: Allow calling SplitFspBin.py directly Patrick Georgi
2018-09-18 13:32 ` Patrick Georgi [this message]
2018-09-18 15:04 ` [PATCH 2/3] IntelFsp2Pkg: Fix typo in SplitFspBin Desimone, Nathaniel L
2018-09-20 23:28 ` Chiu, Chasel
2018-09-26 3:11 ` Yao, Jiewen
2018-09-18 13:32 ` [PATCH 3/3] IntelFsp2Pkg: Tell git to format SplitFspBin.py with native newlines Patrick Georgi
2018-09-18 15:10 ` Desimone, Nathaniel L
2018-09-18 15:53 ` Patrick Georgi
2018-09-20 4:37 ` Desimone, Nathaniel L
2018-09-26 3:12 ` Yao, Jiewen
2018-09-26 15:58 ` Patrick Georgi
2018-09-27 0:40 ` Yao, Jiewen
2018-09-18 15:03 ` [PATCH 1/3] IntelFsp2Pkg: Allow calling SplitFspBin.py directly Desimone, Nathaniel L
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=20180918133203.192779-2-pgeorgi@google.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