From: "gaoliming" <gaoliming@byosoft.com.cn>
To: <devel@edk2.groups.io>, <pedro.falcato@gmail.com>
Subject: 回复: [edk2-devel] [PATCH v2 0/2] Update brotli to the latest commit
Date: Wed, 15 Dec 2021 13:36:09 +0800 [thread overview]
Message-ID: <01f701d7f175$aa37a4c0$fea6ee40$@byosoft.com.cn> (raw)
In-Reply-To: <20211208102701.10815-1-pedro.falcato@gmail.com>
Pedro:
Does Brotli fix GCC warning in the latest version?
Thanks
Liming
> -----邮件原件-----
> 发件人: devel@edk2.groups.io <devel@edk2.groups.io> 代表 Pedro Falcato
> 发送时间: 2021年12月8日 18:27
> 收件人: devel@edk2.groups.io
> 主题: [edk2-devel] [PATCH v2 0/2] Update brotli to the latest commit
>
> BZ: https://bugzilla.tianocore.org/show_bug.cgi?id=3D3417
>
> This patch set updates the brotli submodule to the latest commit, which
> fixes a warning that triggers build failures for both BaseTools and
> MdeModulePkg/BrotliCustomDecompressLib in GCC 11 compilers.
>
> Pedro Falcato (2):
> BaseTools: Update brotli to the latest upstream commit
> MdeModulePkg/BrotliCustomDecompressLib: Update brotli
>
> BaseTools/Source/C/BrotliCompress/GNUmakefile
> | 7 +++++++
> BaseTools/Source/C/BrotliCompress/Makefile
> | 12 +++++++++++-
> BaseTools/Source/C/BrotliCompress/brotli
> | 2 +-
>
> MdeModulePkg/Library/BrotliCustomDecompressLib/BrotliCustomDecompre
> ssLib.inf | 3 +++
> MdeModulePkg/Library/BrotliCustomDecompressLib/brotli
> | 2 +-
> 5 files changed, 23 insertions(+), 3 deletions(-)
>
> --
> 2.34.1
>
>
>
>
>
next prev parent reply other threads:[~2021-12-15 5:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-08 10:26 [PATCH v2 0/2] Update brotli to the latest commit Pedro Falcato
2021-12-08 10:27 ` [PATCH v2 1/2] BaseTools: Update brotli to the latest upstream commit Pedro Falcato
2021-12-08 10:27 ` [PATCH v2 2/2] MdeModulePkg/BrotliCustomDecompressLib: Update brotli Pedro Falcato
2021-12-15 5:36 ` gaoliming [this message]
2021-12-15 10:17 ` [edk2-devel] [PATCH v2 0/2] Update brotli to the latest commit Pedro Falcato
2021-12-16 2:46 ` 回复: " gaoliming
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='01f701d7f175$aa37a4c0$fea6ee40$@byosoft.com.cn' \
--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