public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Yonghong Zhu <yonghong.zhu@intel.com>
To: edk2-devel@lists.01.org
Cc: Liming Gao <liming.gao@intel.com>
Subject: [Patch 0/4] BaseTools: support OPENSSL_PATH has space character
Date: Wed, 19 Apr 2017 18:18:14 +0800	[thread overview]
Message-ID: <1492597098-35836-1-git-send-email-yonghong.zhu@intel.com> (raw)

Update related Tools to support OPENSSL_PATH has space characters.

Cc: Liming Gao <liming.gao@intel.com>
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Yonghong Zhu <yonghong.zhu@intel.com>

Yonghong Zhu (4):
  BaseTools/VolInfo: Update OPENSSL_PATH to support space characters
  BaseTools: Pkcs7Sign Tool to support OPENSSL_PATH has space
  BaseTools: Rsa2048Sha256Sign Tool to support OPENSSL_PATH has space
  BaseTools: Rsa2048Sha256GenerateKeys to support OPENSSL_PATH has space

 BaseTools/Source/C/VolInfo/VolInfo.c                        | 13 +++++++++----
 BaseTools/Source/Python/Pkcs7Sign/Pkcs7Sign.py              |  2 ++
 .../Python/Rsa2048Sha256Sign/Rsa2048Sha256GenerateKeys.py   |  2 ++
 .../Source/Python/Rsa2048Sha256Sign/Rsa2048Sha256Sign.py    |  2 ++
 4 files changed, 15 insertions(+), 4 deletions(-)

-- 
2.6.1.windows.1



             reply	other threads:[~2017-04-19 10:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-19 10:18 Yonghong Zhu [this message]
2017-04-19 10:18 ` [Patch 1/4] BaseTools/VolInfo: Update OPENSSL_PATH to support space characters Yonghong Zhu
2017-04-19 10:18 ` [Patch 2/4] BaseTools: Pkcs7Sign Tool to support OPENSSL_PATH has space Yonghong Zhu
2017-04-19 10:18 ` [Patch 3/4] BaseTools: Rsa2048Sha256Sign " Yonghong Zhu
2017-04-19 10:18 ` [Patch 4/4] BaseTools: Rsa2048Sha256GenerateKeys " Yonghong Zhu
2017-04-27  9:31 ` [Patch 0/4] BaseTools: support OPENSSL_PATH has space character Gao, Liming

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=1492597098-35836-1-git-send-email-yonghong.zhu@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