From: "Ard Biesheuvel" <ardb@kernel.org>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: devel@edk2.groups.io,
"Ard Biesheuvel" <ardb+tianocore@kernel.org>,
"László Érsek" <lersek@redhat.com>,
"Jordan Justen" <jordan.l.justen@intel.com>,
"Pawel Polawski" <ppolawsk@redhat.com>,
"Oliver Steffen" <osteffen@redhat.com>,
"Jiewen Yao" <jiewen.yao@intel.com>
Subject: Re: [PATCH 0/2] OvmfPkg: check 64bit mmio window for resource conflicts
Date: Fri, 6 Jan 2023 15:14:53 +0100 [thread overview]
Message-ID: <CAMj1kXFukYZHr61Mpz1g4taZUJY+J=MG-1pdeGv54Lg-pUqWAw@mail.gmail.com> (raw)
In-Reply-To: <20230106140403.2889131-1-kraxel@redhat.com>
Hi Gerd,
On Fri, 6 Jan 2023 at 15:04, Gerd Hoffmann <kraxel@redhat.com> wrote:
>
>
>
> Gerd Hoffmann (2):
> OvmfPkg/PlatformInitLib: update PlatformScanOrAdd64BitE820Ram
> documentation
> OvmfPkg/PlatformInitLib: check 64bit mmio window for resource
> conflicts
>
> OvmfPkg/Library/PlatformInitLib/MemDetect.c | 63 +++++++++++++++++----
> 1 file changed, 51 insertions(+), 12 deletions(-)
>
Mind adding a teeny bit of context to explain why this is needed? No
need to respin or anything - just want to make sure i understand the
problem and the solution.
next prev parent reply other threads:[~2023-01-06 14:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 14:04 [PATCH 0/2] OvmfPkg: check 64bit mmio window for resource conflicts Gerd Hoffmann
2023-01-06 14:04 ` [PATCH 1/2] OvmfPkg/PlatformInitLib: update PlatformScanOrAdd64BitE820Ram documentation Gerd Hoffmann
2023-01-09 8:07 ` [edk2-devel] " Laszlo Ersek
2023-01-09 10:15 ` Gerd Hoffmann
2023-01-09 11:30 ` Laszlo Ersek
2023-01-06 14:04 ` [PATCH 2/2] OvmfPkg/PlatformInitLib: check 64bit mmio window for resource conflicts Gerd Hoffmann
2023-01-06 20:39 ` [edk2-devel] " Pedro Falcato
2023-01-09 7:02 ` Gerd Hoffmann
2023-01-06 14:14 ` Ard Biesheuvel [this message]
2023-01-06 15:32 ` [PATCH 0/2] OvmfPkg: " Gerd Hoffmann
2023-01-06 15:39 ` Yao, Jiewen
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='CAMj1kXFukYZHr61Mpz1g4taZUJY+J=MG-1pdeGv54Lg-pUqWAw@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