public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: devel@edk2.groups.io, lersek@redhat.com
Cc: Jian J Wang <jian.j.wang@intel.com>,
	Leif Lindholm <leif.lindholm@linaro.org>,
	Shenglei Zhang <shenglei.zhang@intel.com>,
	Xiaoyu Lu <xiaoyux.lu@intel.com>
Subject: Re: [edk2-devel] [PATCH 3/3] CryptoPkg/OpensslLib.inf: list OpenSSL local header "ms/uplink.h"
Date: Thu, 21 Nov 2019 16:51:23 +0100	[thread overview]
Message-ID: <3766b29c-1c26-188e-68bf-a898973f6dba@redhat.com> (raw)
In-Reply-To: <20191121093833.13840-4-lersek@redhat.com>

On 11/21/19 10:38 AM, Laszlo Ersek via Groups.Io wrote:
> Commit 8906f076de35 ("CryptoPkg/OpensslLib: Add missing header files in
> INF file", 2019-08-16) incorrectly placed "ms/uplink.h" in the
> auto-generated part of [Sources], in "OpensslLib.inf".
> 
> ("ms/uplink.h" was added in the right spot in "OpensslLibCrypto.inf".)
> 
> Subsequently, when commit 9f4fbd56d430 ("CryptoPkg/OpensslLib: Update
> process_files.pl to generate .h files", 2019-10-30) re-generated that part
> of "OpensslLib.inf", the "ms/uplink.h" file reference was lost. This
> triggers a warning from the "build" utility now.
> 
> Name the header file in the right spot in [Sources].
> 
> This change makes "OpensslLib.inf" consistent with "OpensslLibCrypto.inf".
> 
> Cc: Jian J Wang <jian.j.wang@intel.com>
> Cc: Leif Lindholm <leif.lindholm@linaro.org>
> Cc: Shenglei Zhang <shenglei.zhang@intel.com>
> Cc: Xiaoyu Lu <xiaoyux.lu@intel.com>
> Fixes: 8906f076de35b222a7d62bcf6ed1a4a2498a5791
> Signed-off-by: Laszlo Ersek <lersek@redhat.com>
> ---
> 
> Notes:
>      Targeting edk2-stable201911.
> 
>   CryptoPkg/Library/OpensslLib/OpensslLib.inf | 1 +
>   1 file changed, 1 insertion(+)
> 
> diff --git a/CryptoPkg/Library/OpensslLib/OpensslLib.inf b/CryptoPkg/Library/OpensslLib/OpensslLib.inf
> index 58202f83118d..3fa52f554320 100644
> --- a/CryptoPkg/Library/OpensslLib/OpensslLib.inf
> +++ b/CryptoPkg/Library/OpensslLib/OpensslLib.inf
> @@ -23,6 +23,7 @@ [Defines]
>   
>   [Sources]
>     $(OPENSSL_PATH)/e_os.h
> +  $(OPENSSL_PATH)/ms/uplink.h
>   # Autogenerated files list starts here
>     $(OPENSSL_PATH)/crypto/aes/aes_cbc.c
>     $(OPENSSL_PATH)/crypto/aes/aes_cfb.c
> 

Reviewed-by: Philippe Mathieu-Daude <philmd@redhat.com>


  parent reply	other threads:[~2019-11-21 15:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-21  9:38 [PATCH 0/3] local header listing fixes for INF files, for edk2-stable201911 Laszlo Ersek
2019-11-21  9:38 ` [PATCH 1/3] MdeModulePkg/VariableSmmRuntimeDxe.inf: list local header "Variable.h" Laszlo Ersek
2019-11-21 15:53   ` [edk2-devel] " Philippe Mathieu-Daudé
2019-11-21 15:55   ` Wang, Jian J
2019-11-21  9:38 ` [PATCH 2/3] CryptoPkg/OpensslLib: improve INF file consistency Laszlo Ersek
2019-11-21 14:44   ` Wang, Jian J
2019-11-21 15:48   ` [edk2-devel] " Philippe Mathieu-Daudé
2019-11-21  9:38 ` [PATCH 3/3] CryptoPkg/OpensslLib.inf: list OpenSSL local header "ms/uplink.h" Laszlo Ersek
2019-11-21 14:43   ` [edk2-devel] " Wang, Jian J
2019-11-21 15:51   ` Philippe Mathieu-Daudé [this message]
2019-11-21 10:00 ` [PATCH 0/3] local header listing fixes for INF files, for edk2-stable201911 Leif Lindholm
2019-11-21 16:07   ` Laszlo Ersek
2019-12-02 20:23 ` [edk2-devel] " 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=3766b29c-1c26-188e-68bf-a898973f6dba@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