public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Gerd Hoffmann" <kraxel@redhat.com>
To: "Ojeda Leon, Nicolas" <ncoleon@amazon.de>
Cc: "devel@edk2.groups.io" <devel@edk2.groups.io>, "Graf (AWS),
	Alexander" <graf@amazon.de>
Subject: Re: [edk2-devel] [PATCH v5 4/5] Ovmf/PlatformPei: Use host-provided GPA end if available
Date: Wed, 1 Jun 2022 10:46:52 +0200	[thread overview]
Message-ID: <20220601084652.suex64jnkoztgiod@sirius.home.kraxel.org> (raw)
In-Reply-To: <b064f54ff60c4a13879bd0170918ef52@EX13D49EUC003.ant.amazon.com>

On Fri, May 27, 2022 at 01:05:32PM +0000, Ojeda Leon, Nicolas wrote:
> Hi,
> 
> Following the discussion, could these patches already be merged?

I think so, now that the freeze is over.  I'd suggest to rebase, run
through CI (open a draft pull request for that) and repost the series,
with the maintainers Cc'ed (the script
BaseTools/Scripts/GetMaintainer.py helps with that).

take care,
  Gerd


  reply	other threads:[~2022-06-01  8:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-25 21:43 [PATCH v5 0/5] Handling of multiple PCI host bridges Ojeda Leon, Nicolas
2022-04-25 21:43 ` [PATCH v5 1/5] OvmfPkg/Library: Create base HardwareInfoLib for PCI Host Bridges Ojeda Leon, Nicolas
2022-04-25 21:43 ` [PATCH v5 2/5] Ovmf/HardwareInfoLib: Create Pei lib to parse directly from fw-cfg Ojeda Leon, Nicolas
2022-04-25 21:43 ` [PATCH v5 3/5] Ovmf/HardwareInfoLib: Add Dxe lib to dynamically parse heterogenous data Ojeda Leon, Nicolas
2022-04-25 21:43 ` [PATCH v5 4/5] Ovmf/PlatformPei: Use host-provided GPA end if available Ojeda Leon, Nicolas
2022-04-29 10:18   ` [edk2-devel] " Gerd Hoffmann
2022-05-13  8:45     ` Ojeda Leon, Nicolas
2022-05-27 13:05       ` Ojeda Leon, Nicolas
2022-06-01  8:46         ` Gerd Hoffmann [this message]
2022-04-25 21:43 ` [PATCH v5 5/5] OvmfPkg/PciHostBridgeUtilityLib: Initialize RootBridges apertures with spec Ojeda Leon, Nicolas

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=20220601084652.suex64jnkoztgiod@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