From: "Sean Rhodes" <sean@starlabs.systems>
To: Guo Dong <guo.dong@intel.com>,devel@edk2.groups.io
Subject: Re: [edk2-devel] [PATCH 5/5] UefiPayloadPkg: Add support for Firmware Volume Block Protocol
Date: Wed, 23 Mar 2022 12:52:15 -0700 [thread overview]
Message-ID: <6952.1648065135281733577@groups.io> (raw)
In-Reply-To: <BYAPR11MB3622E6FB16BDCC00F70B389D9E189@BYAPR11MB3622.namprd11.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 389 bytes --]
Hey Guo
To have the parselib and not SMMSTORE support is a bit of a paradox; coreboot isn't fully functional without one. I think moving this and any subsequent patches into edk2-platforms will inevitably lead to forks, which isn't beneficial to anyone.
Is there any method (or ideally exception ;) ) you can suggest for allowing bootloader specific patches?
Many thanks
Sean
[-- Attachment #2: Type: text/html, Size: 421 bytes --]
next prev parent reply other threads:[~2022-03-23 19:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 9:10 [PATCH 1/5] UefiPayloadPkg/UefiPayloadPkg.ci.yaml: Remove duplicated entry Sean Rhodes
2022-03-21 9:10 ` [PATCH 2/5] UefiPayloadPkg/Include/Coreboot: Add headers for SMMSTOREv2 table Sean Rhodes
2022-03-21 9:10 ` [PATCH 3/5] UefiPayloadPkg: Add SmmStoreInfoGuid Sean Rhodes
2022-03-21 9:10 ` [PATCH 4/5] UefiPayloadPkg: Add SmmStoreLib Sean Rhodes
2022-03-21 9:10 ` [PATCH 5/5] UefiPayloadPkg: Add support for Firmware Volume Block Protocol Sean Rhodes
2022-03-23 18:12 ` Guo Dong
2022-03-23 18:24 ` Patrick Rudolph
2022-03-23 19:27 ` [edk2-devel] " Guo Dong
2022-03-23 19:52 ` Sean Rhodes [this message]
2022-03-23 21:06 ` King Sumo
2022-03-23 21:20 ` Guo Dong
2022-03-23 17:58 ` [PATCH 1/5] UefiPayloadPkg/UefiPayloadPkg.ci.yaml: Remove duplicated entry Guo Dong
2022-03-24 0:37 ` Ni, Ray
2022-03-24 1:58 ` duntan
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=6952.1648065135281733577@groups.io \
--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