From: "Ada Christine" <adachristine18@gmail.com>
To: edk2-devel-groups-io <devel@edk2.groups.io>,
nathaniel.l.desimone@intel.com
Cc: Andrew Fish <afish@apple.com>,
"mhaeuser@posteo.de" <mhaeuser@posteo.de>,
"discuss@edk2.groups.io" <discuss@edk2.groups.io>,
Pedro Falcato <pedro.falcato@gmail.com>,
"Shi, Steven" <steven.shi@intel.com>
Subject: Re: [edk2-devel] [edk2-discuss] GSoC Proposal
Date: Fri, 15 Apr 2022 12:09:06 +0000 [thread overview]
Message-ID: <CAJdDEFddMfSWT7avbBPmgkc5BTaQs-uByiqY-tf6+VQrPkhEdQ@mail.gmail.com> (raw)
In-Reply-To: <56CE4C08-4232-4897-9B0F-6C6443C2C48D@intel.com>
[-- Attachment #1: Type: text/plain, Size: 701 bytes --]
Hi Everybody
I've read all the discussion here and condensed my plan into a short
project proposal. It's a little short and light on detail at the moment
because I'm pressed for time for other matters today, but I wanted to get
something in before EOD today as requested. Anybody else's input or a
change in the overall strategy to allow for code sharing between DXE
modules, whether it be prelinking or some kind of function pointer table is
absolutely welcome and I'm not attached to any particular way of solving
the code repetition problem. You can find my proposal here
https://summerofcode.withgoogle.com/proposals/details/whGX9tXL
Looking forward to your commentary!
Thanks!
- Ada Christine
[-- Attachment #2: Type: text/html, Size: 900 bytes --]
next prev parent reply other threads:[~2022-04-15 12:09 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <14039.1649847289490383262@groups.io>
2022-04-13 12:05 ` [edk2-discuss] GSoC Proposal Marvin Häuser
2022-04-13 14:38 ` Ada Christine
2022-04-13 15:15 ` Marvin Häuser
2022-04-13 17:53 ` Ada Christine
2022-04-13 18:46 ` [edk2-devel] " Pedro Falcato
2022-04-13 18:42 ` Pedro Falcato
2022-04-13 19:14 ` Marvin Häuser
2022-04-13 22:57 ` Nate DeSimone
2022-04-14 1:30 ` Ada Christine
2022-04-14 7:55 ` Marvin Häuser
2022-04-15 1:06 ` Nate DeSimone
2022-04-15 2:42 ` Andrew Fish
2022-04-15 6:56 ` Marvin Häuser
2022-04-15 8:15 ` Nate DeSimone
2022-04-15 12:09 ` Ada Christine [this message]
2022-04-15 12:31 ` Marvin Häuser
2022-04-15 13:31 ` Zimmer, Vincent
2022-04-15 13:39 ` Marvin Häuser
2022-04-15 14:53 ` Zimmer, Vincent
2022-04-15 15:02 ` Yao, Jiewen
2022-04-15 16:00 ` Marvin Häuser
2022-04-15 16:22 ` Brian J. Johnson
2022-04-15 16:44 ` Marvin Häuser
2022-04-15 18:47 ` Oram, Isaac W
2022-04-15 19:04 ` Marvin Häuser
2022-04-16 4:23 ` Nate DeSimone
2022-04-16 13:36 ` Ada Christine
2022-04-18 17:54 ` Brian J. Johnson
2022-04-13 22:56 ` Nate DeSimone
[not found] <t4R6.1649786926384402958.oz5x@groups.io>
2022-04-13 6:54 ` Marvin Häuser
[not found] ` <16E57BE84FE390E6.22782@groups.io>
2022-04-13 14:46 ` [edk2-devel] " Rebecca Cran
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=CAJdDEFddMfSWT7avbBPmgkc5BTaQs-uByiqY-tf6+VQrPkhEdQ@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