public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Eric Jin" <eric.jin@intel.com>
To: Ashish Singhal <ashishsingha@nvidia.com>,
	Supreeth Venkatesh <Supreeth.Venkatesh@arm.com>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: Re: UEFI SCT Build Broken
Date: Thu, 13 Jun 2019 08:07:33 +0000	[thread overview]
Message-ID: <DA72DC7456565B47808A57108259571F637C1D63@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <DA72DC7456565B47808A57108259571F637C08B1@SHSMSX103.ccr.corp.intel.com>

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

Ashish,

Supreeth already sent out the patch yesterday, we will let you know if the patches are committed to repo. Thanks.

Best Regards
Eric

From: Jin, Eric <eric.jin@intel.com>
Sent: Wednesday, June 12, 2019 5:19 PM
To: Ashish Singhal <ashishsingha@nvidia.com>; Supreeth Venkatesh <Supreeth.Venkatesh@arm.com>; devel@edk2.groups.io
Cc: Jin, Eric <eric.jin@intel.com>
Subject: RE: UEFI SCT Build Broken

Hi Ashish,

Thank for raising this issue.
UEFI SCT build pass with edk2-stable201903, and fail on edk2-stable201905, because edk2 drop the IPF support (4e1daa60f5372c22a11503961061ffa569eaf873).
UEFI SCT can remove IPF support too. I can follow it tomorrow. Thanks.


Best Regards
Eric

From: Ashish Singhal <ashishsingha@nvidia.com<mailto:ashishsingha@nvidia.com>>
Sent: Wednesday, June 12, 2019 4:26 AM
To: Supreeth Venkatesh <Supreeth.Venkatesh@arm.com<mailto:Supreeth.Venkatesh@arm.com>>; Jin, Eric <eric.jin@intel.com<mailto:eric.jin@intel.com>>; devel@edk2.groups.io<mailto:devel@edk2.groups.io>
Subject: Re: UEFI SCT Build Broken

Supreeth,

It is broken against both edk2 tip as well as latest edk2 tag edk2-stable201903.

I have filed a bugzilla bug<https://bugzilla.tianocore.org/show_bug.cgi?id=1899> for the same.

Thanks
Ashish
________________________________
From: Supreeth Venkatesh <Supreeth.Venkatesh@arm.com<mailto:Supreeth.Venkatesh@arm.com>>
Sent: Tuesday, June 11, 2019 1:36 PM
To: Ashish Singhal; Eric Jin; devel@edk2.groups.io<mailto:devel@edk2.groups.io>
Subject: RE: UEFI SCT Build Broken


Ashish,



We are working towards fixing the issue for the next SCT tag corresponding to edk2 tag.

Can you please let us know whether you are referring to edk2 tip or which edk2 tag (edk2-stable201903)?



If possible, could you log a bug entry in bugzillafor edk2-test/SCT component?



Thanks,

Supreeth



From: Ashish Singhal <ashishsingha@nvidia.com<mailto:ashishsingha@nvidia.com>>
Sent: Tuesday, June 11, 2019 12:18 PM
To: Supreeth Venkatesh <Supreeth.Venkatesh@arm.com<mailto:Supreeth.Venkatesh@arm.com>>; Eric Jin <eric.jin@intel.com<mailto:eric.jin@intel.com>>; devel@edk2.groups.io<mailto:devel@edk2.groups.io>
Subject: UEFI SCT Build Broken



Hello Eric/Supreeth,



With the latest edk2 tag, UEFI SCT tip build is broken. Seems like it needs Guid/SalSystemTable.h header file which is not in edk2 tree any more. Is a fix for this already being looked at?



Thanks

Ashish

________________________________

This email message is for the sole use of the intended recipient(s) and may contain confidential information.  Any unauthorized review, use, disclosure or distribution is prohibited.  If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.

________________________________
IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

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

      parent reply	other threads:[~2019-06-13  8:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-11 17:18 UEFI SCT Build Broken ashishsingha
2019-06-11 19:36 ` Supreeth Venkatesh
2019-06-11 20:25   ` Ashish Singhal
2019-06-12  9:18     ` Eric Jin
2019-06-12 16:49       ` Ashish Singhal
2019-06-13  8:07       ` Eric Jin [this message]

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=DA72DC7456565B47808A57108259571F637C1D63@SHSMSX103.ccr.corp.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