From: "Boeuf, Sebastien" <sebastien.boeuf@intel.com>
To: "Yao, Jiewen" <jiewen.yao@intel.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
"ardb@kernel.org" <ardb@kernel.org>
Cc: "kraxel@redhat.com" <kraxel@redhat.com>
Subject: Re: [edk2-devel] CMOS needed for Cloud Hypervisor
Date: Thu, 16 Dec 2021 20:10:22 +0000 [thread overview]
Message-ID: <BY5PR11MB44010891C994F7BA45F6EB14EA779@BY5PR11MB4401.namprd11.prod.outlook.com> (raw)
In-Reply-To: <MW4PR11MB5872E3AB6A703B65A23ACB338C769@MW4PR11MB5872.namprd11.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 2243 bytes --]
Thank you! I really appreciate your responsiveness!
Sebastien
________________________________
From: Yao, Jiewen <jiewen.yao@intel.com>
Sent: Wednesday, December 15, 2021 6:14:07 PM
To: devel@edk2.groups.io <devel@edk2.groups.io>; ardb@kernel.org <ardb@kernel.org>; Boeuf, Sebastien <sebastien.boeuf@intel.com>
Cc: kraxel@redhat.com <kraxel@redhat.com>
Subject: RE: [edk2-devel] CMOS needed for Cloud Hypervisor
Acked-by: Jiewen Yao <Jiewen.yao@intel.com>
Thank you Ard, for the quick response.
I will reply on you to do the revert. Appreciate your help.
Thank you
Yao Jiewen
> -----Original Message-----
> From: devel@edk2.groups.io <devel@edk2.groups.io> On Behalf Of Ard
> Biesheuvel
> Sent: Thursday, December 16, 2021 12:50 AM
> To: edk2-devel-groups-io <devel@edk2.groups.io>; Boeuf, Sebastien
> <sebastien.boeuf@intel.com>
> Cc: kraxel@redhat.com
> Subject: Re: [edk2-devel] CMOS needed for Cloud Hypervisor
>
> On Wed, 15 Dec 2021 at 17:37, Boeuf, Sebastien
> <sebastien.boeuf@intel.com> wrote:
> >
> > Hi Gerd,
> >
> > Your patch 41d8bb30386ceab55787fc9f5aac6434e2493e27 removing the
> CMOS
> > support for getting high mem and low mem is breaking the OVMF support for
> > Cloud Hypervisor as we are still providing this information through that
> mechanism.
> >
> > Do you think it would be acceptable to revert it in order to keep Cloud
> Hypervisor
> > working?
> >
> > Also, I probably need to add some CI related to Cloud Hypervisor to the EDK2
> repo
> > if we want to catch such regressions earlier in the process :)
> >
>
> Thanks for the report. I will go ahead and revert this for now.
>
>
>
>
---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris,
92196 Meudon Cedex, France
Registration Number: 302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
[-- Attachment #2: Type: text/html, Size: 3447 bytes --]
prev parent reply other threads:[~2021-12-16 20:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 16:31 CMOS needed for Cloud Hypervisor Boeuf, Sebastien
2021-12-15 16:50 ` [edk2-devel] " Ard Biesheuvel
2021-12-15 17:14 ` Yao, Jiewen
2021-12-16 20:10 ` Boeuf, Sebastien [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=BY5PR11MB44010891C994F7BA45F6EB14EA779@BY5PR11MB4401.namprd11.prod.outlook.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