public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Sunil V L" <sunilvl@ventanamicro.com>
To: Jianyong Wu <Jianyong.Wu@arm.com>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>,
	Sami Mujawar <Sami.Mujawar@arm.com>,
	Ard Biesheuvel <ardb@kernel.org>
Subject: Re: [PATCH] CloudHv: can't find gUefiOvmfPkgTokenSpaceGuid
Date: Tue, 28 Mar 2023 10:29:01 +0530	[thread overview]
Message-ID: <ZCJ0FeEYSyHuED/S@sunil-laptop> (raw)
In-Reply-To: <DB9PR08MB7511E58AEC12DC738D2BCFE6F4889@DB9PR08MB7511.eurprd08.prod.outlook.com>

On Tue, Mar 28, 2023 at 03:28:25AM +0000, Jianyong Wu wrote:
> Add Ard Biesheuvel <ardb@kernel.org> and Sunil V L <sunilvl@ventanamicro.com> to cc list.
> 
> > -----Original Message-----
> > From: Jianyong Wu <jianyong.wu@arm.com>
> > Sent: 2023年2月17日 14:48
> > To: devel@edk2.groups.io; Sami Mujawar <Sami.Mujawar@arm.com>
> > Cc: Jianyong Wu <Jianyong.Wu@arm.com>
> > Subject: [PATCH] CloudHv: can't find gUefiOvmfPkgTokenSpaceGuid
> >
> > commit f13264b34 introduces a bug for CloudHv as OvmfPkg/OvmfPkg.dec is
> > missing in CloudHvHasAcpiDtDxe.inf which leads to
> > gUefiOvmfPkgTokenSpaceGuid found nowhere.
> >
> > Signed-off-by: Jianyong Wu <jianyong.wu@arm.com>
> > ---
Hi Jianyong,

Any reason why this platform is not built as part of CI? I think it will
be good to add so that we don't break by some changes like this.

Thanks,
Sunil

  parent reply	other threads:[~2023-03-28  4:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-17  6:48 [PATCH] CloudHv: can't find gUefiOvmfPkgTokenSpaceGuid Jianyong Wu
2023-03-28  3:28 ` Jianyong Wu
2023-03-28  4:41   ` Sunil V L
2023-03-28  4:59   ` Sunil V L [this message]
2023-03-28  7:52     ` Sami Mujawar
2023-03-28  8:17       ` Jianyong Wu
2023-03-28  8:33         ` Sami Mujawar
2023-03-28  8:54           ` Jianyong Wu
2023-03-28  7:45   ` Sami Mujawar

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=ZCJ0FeEYSyHuED/S@sunil-laptop \
    --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