From: "Kirkendall, Garrett" <garrett.kirkendall@amd.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
Chasel Chiu <chasel.chiu@intel.com>,
Nate DeSimone <nathaniel.l.desimone@intel.com>,
Isaac Oram <isaac.w.oram@intel.com>,
Liming Gao <gaoliming@byosoft.com.cn>,
Eric Dong <eric.dong@intel.com>
Subject: MinPlatformPkg question
Date: Thu, 12 Jan 2023 13:33:04 +0000 [thread overview]
Message-ID: <PH7PR12MB6441B86AC5AE935BC1811C3C85FD9@PH7PR12MB6441.namprd12.prod.outlook.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 740 bytes --]
[Public]
+ MinPlatformPkg Maintainers
Start the conversation:
Some time back there were posts about promoting MinPlatformPkg up to a more generic level. Is there still a desire to implement this and possibly even to promote this more generic MinPlatformPkg to the edk2 repository. Would it be expanded to encompass different architectures other than x86, and maybe how?
GARRETT KIRKENDALL
----------------------------------------------------------------------------------------------------------------------------------
Facebook<https://www.facebook.com/AMD> | Twitter<https://twitter.com/AMD> | amd.com<http://www.amd.com/>
[cid:image001.png@01D92658.1A4E0AC0]
Words to live by: "Slow is Smooth. Smooth is Fast."
[-- Attachment #1.2: Type: text/html, Size: 4039 bytes --]
[-- Attachment #2: image001.png --]
[-- Type: image/png, Size: 2614 bytes --]
next reply other threads:[~2023-01-12 13:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-12 13:33 Kirkendall, Garrett [this message]
2023-01-12 21:44 ` MinPlatformPkg question Isaac Oram
2023-01-31 16:54 ` Kirkendall, Garrett
2023-01-31 18:57 ` [edk2-devel] " Pedro Falcato
2023-01-31 19:28 ` Kirkendall, Garrett
2023-01-31 20:43 ` Isaac Oram
2023-02-01 1:18 ` Pedro Falcato
-- strict thread matches above, loose matches on Subject: below --
2023-01-09 17:30 Kirkendall, Garrett
2023-01-10 3:49 ` Chang, Abner
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=PH7PR12MB6441B86AC5AE935BC1811C3C85FD9@PH7PR12MB6441.namprd12.prod.outlook.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