public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Ard Biesheuvel" <ardb@kernel.org>
To: devel@edk2.groups.io, lersek@redhat.com
Cc: Anthony Perard <anthony.perard@citrix.com>,
	Ard Biesheuvel <ardb+tianocore@kernel.org>,
	 Brijesh Singh <brijesh.singh@amd.com>,
	Erdem Aktas <erdemaktas@google.com>,
	 Eric Dong <eric.dong@intel.com>,
	Gerd Hoffmann <kraxel@redhat.com>,
	 James Bottomley <jejb@linux.ibm.com>,
	Jiewen Yao <jiewen.yao@intel.com>,
	 Jordan Justen <jordan.l.justen@intel.com>,
	Julien Grall <julien@xen.org>, Min Xu <min.m.xu@intel.com>,
	 Peter Grehan <grehan@freebsd.org>,
	Rahul Kumar <rahul1.kumar@intel.com>, Ray Ni <ray.ni@intel.com>,
	 Rebecca Cran <rebecca@bsdio.com>,
	Sebastien Boeuf <sebastien.boeuf@intel.com>,
	 Tom Lendacky <thomas.lendacky@amd.com>
Subject: Re: [edk2-devel] [PATCH 0/4] fixes for BZs 3876, 4235, 4236
Date: Wed, 4 Jan 2023 10:46:24 +0100	[thread overview]
Message-ID: <CAMj1kXHRymOV9MxbbVh2jKce5T9jQ7z3oXLwQ8nX1-BAdrunhw@mail.gmail.com> (raw)
In-Reply-To: <20230103150244.66835-1-lersek@redhat.com>

On Tue, 3 Jan 2023 at 16:03, Laszlo Ersek <lersek@redhat.com> wrote:
>
> Repo:   https://pagure.io/lersek/edk2.git
> Branch: smorgasboard
>
> Round-up series of small patches, for the BZs noted in the subject.
>
> Successful test build: <https://github.com/tianocore/edk2/pull/3847>.
>
> Regarding runtime testing: notes have been captured in the commit
> messages. For testing, I first reverted 7bda8c648192^..3f378450dfaf, due
> to BZ 4234.
>
> Cc: Anthony Perard <anthony.perard@citrix.com>
> Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>
> Cc: Brijesh Singh <brijesh.singh@amd.com>
> Cc: Erdem Aktas <erdemaktas@google.com>
> Cc: Eric Dong <eric.dong@intel.com>
> Cc: Gerd Hoffmann <kraxel@redhat.com>
> Cc: James Bottomley <jejb@linux.ibm.com>
> Cc: Jiewen Yao <jiewen.yao@intel.com>
> Cc: Jordan Justen <jordan.l.justen@intel.com>
> Cc: Julien Grall <julien@xen.org>
> Cc: Min Xu <min.m.xu@intel.com>
> Cc: Peter Grehan <grehan@freebsd.org>
> Cc: Rahul Kumar <rahul1.kumar@intel.com>
> Cc: Ray Ni <ray.ni@intel.com>
> Cc: Rebecca Cran <rebecca@bsdio.com>
> Cc: Sebastien Boeuf <sebastien.boeuf@intel.com>
> Cc: Tom Lendacky <thomas.lendacky@amd.com>
>
> Laszlo Ersek (4):
>   OvmfPkg/QemuVideoDxe/VbeShim.sh: remove end-of-options delimiter for
>     nasm
>   OvmfPkg: raise DXEFV size to 13 MB in the traditional platform FDFs
>   UefiCpuPkg/SmmCpuFeaturesLib: drop obsolete API implementation
>   OvmfPkg/SmmCpuFeaturesLib: drop obsolete API implementation
>

Merged as #3852 - thanks for the fixes

  parent reply	other threads:[~2023-01-04  9:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-03 15:02 [PATCH 0/4] fixes for BZs 3876, 4235, 4236 Laszlo Ersek
2023-01-03 15:02 ` [PATCH 1/4] OvmfPkg/QemuVideoDxe/VbeShim.sh: remove end-of-options delimiter for nasm Laszlo Ersek
2023-01-03 15:02 ` [PATCH 2/4] OvmfPkg: raise DXEFV size to 13 MB in the traditional platform FDFs Laszlo Ersek
2023-01-03 15:02 ` [PATCH 3/4] UefiCpuPkg/SmmCpuFeaturesLib: drop obsolete API implementation Laszlo Ersek
2023-01-03 15:02 ` [PATCH 4/4] OvmfPkg/SmmCpuFeaturesLib: " Laszlo Ersek
2023-01-04  9:46 ` Ard Biesheuvel [this message]
2023-01-04 12:11   ` [edk2-devel] [PATCH 0/4] fixes for BZs 3876, 4235, 4236 Laszlo Ersek

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=CAMj1kXHRymOV9MxbbVh2jKce5T9jQ7z3oXLwQ8nX1-BAdrunhw@mail.gmail.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