From: "Ard Biesheuvel" <ardb@kernel.org>
To: devel@edk2.groups.io, kraxel@redhat.com
Cc: Konstantin Kostiuk <kkostiuk@redhat.com>,
Oliver Steffen <osteffen@redhat.com>,
Jiewen Yao <jiewen.yao@intel.com>
Subject: Re: [edk2-devel] [PATCH v3 0/5] OvmfPkg: Add VirtHstiDxe driver
Date: Mon, 22 Apr 2024 14:37:13 +0200 [thread overview]
Message-ID: <CAMj1kXFrUrcx0njsoH8kFuz9+J8vYa7KLb21mmnPVWamsD1d2g@mail.gmail.com> (raw)
In-Reply-To: <20240422104729.502112-1-kraxel@redhat.com>
On Mon, 22 Apr 2024 at 12:47, Gerd Hoffmann <kraxel@redhat.com> wrote:
>
> v3:
> - use PcdOvmfFlashNvStorageVariableBase
> - add reviewed-by tags
> v2:
> - remove 'Q35' from test bits
> - add patch with a README.md
>
> Gerd Hoffmann (3):
> OvmfPkg/VirtHstiDxe: add varstore flash check
> OvmfPkg/VirtHstiDxe: add code flash check
> OvmfPkg/VirtHstiDxe: add README.md
>
> Konstantin Kostiuk (2):
> OvmfPkg: Add VirtHstiDxe driver
> OvmfPkg: Add VirtHstiDxe to OVMF firmware build
>
I'll take these - thanks.
> OvmfPkg/OvmfPkgIa32.dsc | 2 +
> OvmfPkg/OvmfPkgIa32X64.dsc | 2 +
> OvmfPkg/OvmfPkgX64.dsc | 2 +
> OvmfPkg/OvmfPkgIa32.fdf | 1 +
> OvmfPkg/OvmfPkgIa32X64.fdf | 1 +
> OvmfPkg/OvmfPkgX64.fdf | 1 +
> OvmfPkg/VirtHstiDxe/VirtHstiDxe.inf | 56 +++++++++
> OvmfPkg/VirtHstiDxe/VirtHstiDxe.h | 94 +++++++++++++++
> OvmfPkg/VirtHstiDxe/Flash.c | 90 +++++++++++++++
> OvmfPkg/VirtHstiDxe/QemuCommon.c | 36 ++++++
> OvmfPkg/VirtHstiDxe/QemuPC.c | 38 ++++++
> OvmfPkg/VirtHstiDxe/QemuQ35.c | 71 ++++++++++++
> OvmfPkg/VirtHstiDxe/VirtHstiDxe.c | 173 ++++++++++++++++++++++++++++
> OvmfPkg/VirtHstiDxe/README.md | 48 ++++++++
> 14 files changed, 615 insertions(+)
> create mode 100644 OvmfPkg/VirtHstiDxe/VirtHstiDxe.inf
> create mode 100644 OvmfPkg/VirtHstiDxe/VirtHstiDxe.h
> create mode 100644 OvmfPkg/VirtHstiDxe/Flash.c
> create mode 100644 OvmfPkg/VirtHstiDxe/QemuCommon.c
> create mode 100644 OvmfPkg/VirtHstiDxe/QemuPC.c
> create mode 100644 OvmfPkg/VirtHstiDxe/QemuQ35.c
> create mode 100644 OvmfPkg/VirtHstiDxe/VirtHstiDxe.c
> create mode 100644 OvmfPkg/VirtHstiDxe/README.md
>
> --
> 2.44.0
>
>
>
>
>
>
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#118094): https://edk2.groups.io/g/devel/message/118094
Mute This Topic: https://groups.io/mt/105667070/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2024-04-22 12:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-22 10:47 [edk2-devel] [PATCH v3 0/5] OvmfPkg: Add VirtHstiDxe driver Gerd Hoffmann
2024-04-22 10:47 ` [edk2-devel] [PATCH v3 1/5] " Gerd Hoffmann
2024-04-22 10:47 ` [edk2-devel] [PATCH v3 2/5] OvmfPkg: Add VirtHstiDxe to OVMF firmware build Gerd Hoffmann
2024-04-22 10:47 ` [edk2-devel] [PATCH v3 3/5] OvmfPkg/VirtHstiDxe: add varstore flash check Gerd Hoffmann
2024-04-22 10:47 ` [edk2-devel] [PATCH v3 4/5] OvmfPkg/VirtHstiDxe: add code " Gerd Hoffmann
2024-04-23 13:39 ` Aithal, Srikanth via groups.io
2024-04-23 13:44 ` Aithal, Srikanth via groups.io
2024-04-23 14:31 ` Gerd Hoffmann
2024-04-23 15:06 ` Aithal, Srikanth via groups.io
2024-04-22 10:47 ` [edk2-devel] [PATCH v3 5/5] OvmfPkg/VirtHstiDxe: add README.md Gerd Hoffmann
2024-04-22 12:37 ` Ard Biesheuvel [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=CAMj1kXFrUrcx0njsoH8kFuz9+J8vYa7KLb21mmnPVWamsD1d2g@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