From: Laszlo Ersek <lersek@redhat.com>
To: Jordan Justen <jordan.l.justen@intel.com>,
Gary Lin <glin@suse.com>,
edk2-devel@ml01.01.org, Qin Long <qin.long@intel.com>
Subject: Re: [PATCH 0/3] Enable HTTPS Boot in OVMF
Date: Tue, 17 Jan 2017 21:13:23 +0100 [thread overview]
Message-ID: <ae6bf5bb-ff7a-9952-3741-d56a78309868@redhat.com> (raw)
In-Reply-To: <148464155549.31945.2690363917914543246@jljusten-ivb>
On 01/17/17 09:25, Jordan Justen wrote:
> On 2017-01-16 20:52:29, Gary Lin wrote:
>> This series adjusts the build files of OVMF in order to support HTTPS.
>> It introdues a new build option, TLS_ENABLE, and makes OpenSSL a hard
>> requirement to enable IPv6 support.
>>
>> Gary Lin (3):
>> OvmfPkg: always resolve OpenSslLib, IntrinsicLib and BaseCryptLib
>
> Ok. I see that OpenSSL will still not be a dependency, unless one of
> the dependent features is enabled. (And, they are all disabled by
> default.)
>
> Series Reviewed-by: Jordan Justen <jordan.l.justen@intel.com>
>
> But, I'll let Laszlo take a look too.
My sincere apologies to you and Qin Long for missing your R-b tags.
In retrospect, the Received headers in those messages are consistent
with the Date fields, so the messages did arrive in time (before my
commit / response) in my IMAP inbox. I must have missed them for one of
two reasons:
- my local OfflineIMAP sync glitched out temporarily (unlikely!), or
- these messages appeared only in my edk2-devel list folder, and not in
my INBOX (likely).
In order to decrease the likelihood of such mess-ups on my end in the
future, Gary, can you please ensure that you copy the complete set of
Cc: tags from across the patches to the blurb? This is good for two
goals: first, everyone CC'd on at least one patch will understand the
big picture from the blurb; second, feedback from people who (correctly)
hit "Reply All" on the blurb will reach everyone else too.
(I recommend this practice in
<https://github.com/tianocore/tianocore.github.io/wiki/Laszlo's-unkempt-git-guide-for-edk2-contributors-and-maintainers#contrib-23>,
under the last bullet.)
Nonetheless, missing this feedback is my fault; I should have waited a
bit longer, and double-checked the list folder right before pushing. I'm
sorry!
Laszlo
> Thanks,
>
> -Jordan
>
>> OvmfPkg: correct the set of modules included for the IPv6 stack
>> OvmfPkg: pull in TLS modules with -D TLS_ENABLE (also enabling HTTPS)
>>
>> OvmfPkg/OvmfPkgIa32.dsc | 29 ++++++++++++++++-------------
>> OvmfPkg/OvmfPkgIa32.fdf | 8 ++++----
>> OvmfPkg/OvmfPkgIa32X64.dsc | 29 ++++++++++++++++-------------
>> OvmfPkg/OvmfPkgIa32X64.fdf | 8 ++++----
>> OvmfPkg/OvmfPkgX64.dsc | 29 ++++++++++++++++-------------
>> OvmfPkg/OvmfPkgX64.fdf | 8 ++++----
>> 6 files changed, 60 insertions(+), 51 deletions(-)
>>
>> --
>> 2.11.0
>>
>> _______________________________________________
>> edk2-devel mailing list
>> edk2-devel@lists.01.org
>> https://lists.01.org/mailman/listinfo/edk2-devel
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
>
next prev parent reply other threads:[~2017-01-17 20:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-17 4:52 [PATCH 0/3] Enable HTTPS Boot in OVMF Gary Lin
2017-01-17 4:52 ` [PATCH 1/3] OvmfPkg: always resolve OpenSslLib, IntrinsicLib and BaseCryptLib Gary Lin
2017-01-17 8:03 ` Wu, Jiaxin
2017-01-17 9:13 ` Laszlo Ersek
2017-01-17 4:52 ` [PATCH 2/3] OvmfPkg: correct the set of modules included for the IPv6 stack Gary Lin
2017-01-17 8:04 ` Wu, Jiaxin
2017-01-17 9:22 ` Laszlo Ersek
2017-01-18 0:47 ` Wu, Jiaxin
2017-01-18 8:17 ` Laszlo Ersek
2017-01-18 9:21 ` Gary Lin
2017-01-19 3:09 ` Wu, Jiaxin
2017-01-19 8:36 ` Laszlo Ersek
2017-01-17 4:52 ` [PATCH 3/3] OvmfPkg: pull in TLS modules with -D TLS_ENABLE (also enabling HTTPS) Gary Lin
2017-01-17 8:04 ` Wu, Jiaxin
2017-01-17 9:24 ` Laszlo Ersek
2017-01-17 8:13 ` [PATCH 0/3] Enable HTTPS Boot in OVMF Long, Qin
2017-01-17 8:25 ` Jordan Justen
2017-01-17 20:13 ` Laszlo Ersek [this message]
2017-01-18 1:59 ` Gary Lin
2017-01-17 9:49 ` Laszlo Ersek
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=ae6bf5bb-ff7a-9952-3741-d56a78309868@redhat.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