From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io
Cc: Andrew Fish <afish@apple.com>,
Ard Biesheuvel <ardb+tianocore@kernel.org>,
Gerd Hoffmann <kraxel@redhat.com>,
Jiewen Yao <jiewen.yao@intel.com>,
Leif Lindholm <quic_llindhol@quicinc.com>,
Michael D Kinney <michael.d.kinney@intel.com>,
Rahul Kumar <rahul1.kumar@intel.com>, Ray Ni <ray.ni@intel.com>,
Sami Mujawar <sami.mujawar@arm.com>
Subject: [edk2-devel] [PATCH 0/3] Maintainers.txt: add Laszlo Ersek as an ArmVirt, Ovmf, UefiCpu Pkg "M"
Date: Thu, 16 Nov 2023 22:50:55 +0100 [thread overview]
Message-ID: <20231116215058.8113-1-lersek@redhat.com> (raw)
I'm offering to restore a subset of my earlier ArmVirtPkg and OvmfPkg
maintainer responsibilities.
I'm both offering and requesting an escalation of my earlier UefiCpuPkg
role.
The commit messages contain lists of files and directories that I intend
to assist with.
Under ArmVirtPkg, my focus is the ArmVirtQemu platform.
Under OvmfPkg and UefiCpuPkg, my focus is the traditional three OVMF
platforms (IA32, IA32X64, X64) and their dependencies; in particular I
refrain from Confidential Computing technologies. Under OvmfPkg, I may
also not be the primary reviewer of those nontrivial device drivers and
libraries that I neither wrote nor reviewed.
Finally, I'm interested in reviewing patches for most of the edk2 core,
and patches for the RISC-V architecture; but it's too early to formalize
those interests even as some "R" lines.
Cc: Andrew Fish <afish@apple.com>
Cc: Ard Biesheuvel <ardb+tianocore@kernel.org>
Cc: Gerd Hoffmann <kraxel@redhat.com>
Cc: Jiewen Yao <jiewen.yao@intel.com>
Cc: Leif Lindholm <quic_llindhol@quicinc.com>
Cc: Michael D Kinney <michael.d.kinney@intel.com>
Cc: Rahul Kumar <rahul1.kumar@intel.com>
Cc: Ray Ni <ray.ni@intel.com>
Cc: Sami Mujawar <sami.mujawar@arm.com>
Thanks,
Laszlo
Laszlo Ersek (3):
Maintainers.txt: add Laszlo Ersek as an ArmVirtPkg maintainer
Maintainers.txt: add Laszlo Ersek as an OvmfPkg maintainer
Maintainers.txt: add Laszlo Ersek as a UefiCpuPkg maintainer
Maintainers.txt | 3 +++
1 file changed, 3 insertions(+)
base-commit: 3db76e6476e493d3cda45b81bba99a645180cf35
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#111323): https://edk2.groups.io/g/devel/message/111323
Mute This Topic: https://groups.io/mt/102636309/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/leave/12367111/7686176/1913456212/xyzzy [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next reply other threads:[~2023-11-16 21:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 21:50 Laszlo Ersek [this message]
2023-11-16 21:50 ` [edk2-devel] [PATCH 1/3] Maintainers.txt: add Laszlo Ersek as an ArmVirtPkg maintainer Laszlo Ersek
2023-11-16 21:55 ` Ard Biesheuvel
2023-11-16 21:50 ` [edk2-devel] [PATCH 2/3] Maintainers.txt: add Laszlo Ersek as an OvmfPkg maintainer Laszlo Ersek
2023-11-16 21:56 ` Ard Biesheuvel
2023-11-16 21:50 ` [edk2-devel] [PATCH 3/3] Maintainers.txt: add Laszlo Ersek as a UefiCpuPkg maintainer Laszlo Ersek
2023-11-20 2:46 ` Ni, Ray
2023-11-16 22:52 ` [edk2-devel] [PATCH 0/3] Maintainers.txt: add Laszlo Ersek as an ArmVirt, Ovmf, UefiCpu Pkg "M" Michael D Kinney
2023-11-17 2:31 ` Yao, Jiewen
2023-11-16 23:45 ` Leif Lindholm
2023-11-17 8:59 ` Gerd Hoffmann
2023-12-08 13:31 ` 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=20231116215058.8113-1-lersek@redhat.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