public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gerd Hoffmann" <kraxel@redhat.com>
To: sebastien.boeuf@intel.com
Cc: devel@edk2.groups.io, jiewen.yao@intel.com, jordan.l.justen@intel.com
Subject: Re: [PATCH v2 1/5] OvmfPkg: Make the Xen ELF header generator more flexible
Date: Thu, 24 Feb 2022 09:07:36 +0100	[thread overview]
Message-ID: <20220224080736.h26bj5rki7a7mvth@sirius.home.kraxel.org> (raw)
In-Reply-To: <28aafabd6d684650e526fbc42a28cef2c90a9e86.1645634879.git.sebastien.boeuf@intel.com>

On Wed, Feb 23, 2022 at 05:51:26PM +0100, sebastien.boeuf@intel.com wrote:
> From: Sebastien Boeuf <sebastien.boeuf@intel.com>
> 
> Adding some flexibility to the program so that other targets can use it
> if needed.
> 
> An optional size parameter is added so that we can provide the expected
> blob size of the generated binary.
> 
> A global define is added so that we can choose at build time if we want
> to use 32-bit or 64-bit bases structures.
> 
> The default behavior isn't modified.

Acked-by: Gerd Hoffmann <kraxel@redhat.com>


  reply	other threads:[~2022-02-24  8:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-23 16:51 [PATCH v2 0/5] CloudHv: Rely on PVH boot specification Boeuf, Sebastien
2022-02-23 16:51 ` [PATCH v2 1/5] OvmfPkg: Make the Xen ELF header generator more flexible Boeuf, Sebastien
2022-02-24  8:07   ` Gerd Hoffmann [this message]
2022-02-23 16:51 ` [PATCH v2 2/5] OvmfPkg: Generate CloudHv as a PVH ELF binary Boeuf, Sebastien
2022-02-24  8:16   ` Gerd Hoffmann
2022-02-24 15:12     ` [edk2-devel] " Boeuf, Sebastien
2022-02-25  9:29       ` Gerd Hoffmann
2022-02-25 10:49         ` Boeuf, Sebastien
2022-02-23 16:51 ` [PATCH v2 3/5] OvmfPkg: CloudHv: Retrieve RSDP address from PVH Boeuf, Sebastien
2022-02-23 16:51 ` [PATCH v2 4/5] OvmfPkg: CloudHv: Rely on PVH memmap instead of CMOS Boeuf, Sebastien
2022-02-23 16:51 ` [PATCH v2 5/5] OvmfPkg: CloudHv: Add README Boeuf, Sebastien

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=20220224080736.h26bj5rki7a7mvth@sirius.home.kraxel.org \
    --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