public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Takuto Naito" <naitaku@gmail.com>
To: "Desimone, Nathaniel L" <nathaniel.l.desimone@intel.com>
Cc: "Chaganty, Rangasai V" <rangasai.v.chaganty@intel.com>,
	"Luo, Heng" <heng.luo@intel.com>,
	 "devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: [PATCH v2 0/2] TigerlakeOpenBoard: Fix build errors with GCC5
Date: Wed, 24 Feb 2021 02:01:39 +0900	[thread overview]
Message-ID: <CADLPuDrzp2V2qPRAA1G4Qn=TxzS=UHN9TgoyyP5oZX-C-nsJag@mail.gmail.com> (raw)
In-Reply-To: <MWHPR1101MB2160A182E40B2BDE0E48310DCD819@MWHPR1101MB2160.namprd11.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 1871 bytes --]

Hi Nate and Heng,

The RELEASE build now succeeds, but I noticed that DEBUG build still fails.
I'm trying to fix it. Do you need me to submit another BZ ticket or use the
same ticket?

Best regards,
Takuto Naito

On Tue, Feb 23, 2021 at 7:27 AM Desimone, Nathaniel L <
nathaniel.l.desimone@intel.com> wrote:

> The series has been pushed as 12ef75d~.. 9fb5174
>
> Thanks,
> Nate
>
> > -----Original Message-----
> > From: Takuto Naito <naitaku@gmail.com>
> > Sent: Sunday, February 21, 2021 7:10 AM
> > To: devel@edk2.groups.io
> > Cc: Chaganty, Rangasai V <rangasai.v.chaganty@intel.com>; Desimone,
> > Nathaniel L <nathaniel.l.desimone@intel.com>; Luo, Heng
> > <heng.luo@intel.com>
> > Subject: [PATCH v2 0/2] TigerlakeOpenBoard: Fix build errors with GCC5
> >
> > REF: https://bugzilla.tianocore.org/show_bug.cgi?id=3224
> > TigerlakeOpenBoard: Fix build errors with GCC5
> >
> > v2:
> > - Split the v1 patch into 2 patches.
> >   One is for Platform/Intel/TigerlakeOpenBoardPkg,
> >   another one is for edk2-platforms\Silicon\Intel\TigerlakeSiliconPkg.
> >
> > https://github.com/naitaku/edk2-
> > platforms/tree/tigerlake_fix_build_error_v2
> >
> > Cc: Sai Chaganty <rangasai.v.chaganty@intel.com>
> > Cc: Nate DeSimone <nathaniel.l.desimone@intel.com>
> > Cc: Heng Luo <heng.luo@intel.com>
> >
> > Takuto Naito (2):
> >   TigerlakeOpenBoardPkg: Fix build errors with GCC5
> >   TigerlakeSiliconPkg/IpBlock: Fix build errors with GCC5
> >
> >  .../PeiFspPolicyInitLib.inf                   |   2 +-
> >  .../BasePlatformHookLib/BasePlatformHookLib.c | 188 ------------------
> >  .../DxeSiliconPolicyUpdateLate.c              |   2 +-
> >  .../DxePchPcieRpPolicyLib.c                   |   2 +-
> >  4 files changed, 3 insertions(+), 191 deletions(-)
> >
> > --
> > 2.30.1
>
> --
内藤 卓人
Takuto Naito

[-- Attachment #2: Type: text/html, Size: 3560 bytes --]

  reply	other threads:[~2021-02-23 17:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-21 15:10 [PATCH v2 0/2] TigerlakeOpenBoard: Fix build errors with GCC5 Takuto Naito
2021-02-21 15:10 ` [PATCH v2 1/2] TigerlakeOpenBoardPkg: " Takuto Naito
2021-02-22  1:06   ` Heng Luo
2021-02-21 15:10 ` [PATCH v2 2/2] TigerlakeSiliconPkg/IpBlock: " Takuto Naito
2021-02-22  1:06   ` Heng Luo
2021-02-22  1:09 ` [PATCH v2 0/2] TigerlakeOpenBoard: " Heng Luo
2021-02-22 22:21 ` Nate DeSimone
2021-02-22 22:27 ` Nate DeSimone
2021-02-23 17:01   ` Takuto Naito [this message]
2021-02-24  1:13     ` [edk2-devel] " Heng Luo

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='CADLPuDrzp2V2qPRAA1G4Qn=TxzS=UHN9TgoyyP5oZX-C-nsJag@mail.gmail.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