From: "Ayush Singh" <ayushdevel1325@gmail.com>
To: Yao, Jiewen <jiewen.yao@intel.com>,devel@edk2.groups.io
Subject: Re: [edk2-devel] [PATCH v1 0/3]: Fix RustPkg/Tests in edkii-rust branch edk2-staging
Date: Sat, 19 Mar 2022 07:14:08 -0700 [thread overview]
Message-ID: <12779.1647699248664537510@groups.io> (raw)
In-Reply-To: <MW4PR11MB5872D7F7FBFE7C7D3197C45C8C149@MW4PR11MB5872.namprd11.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 797 bytes --]
Hello Jiewen,
I am a 2nd year University student and am interested in applying for GSoC 2022. I found the project Tasks-Add-Rust-Support-to-EDK-II ( https://github.com/tianocore/tianocore.github.io/wiki/Tasks-Add-Rust-Support-to-EDK-II ) and it contained links to the edkii-rust repository as being an earlier attempt to do this. So I was trying to update/fix the building of this branch as a kind of task that organizations have for student applications. I wanted to understand the old implementation better anyway since it seemed a good place to start rather than starting from scratch.
I did not know about https://github.com/jyao1/rust-firmware , will take a look at it as well.
My introduction mail can be found here ( https://edk2.groups.io/g/devel/message/87637 ).
Ayush Singh
[-- Attachment #2: Type: text/html, Size: 994 bytes --]
next prev parent reply other threads:[~2022-03-19 14:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-19 7:05 [PATCH v1 0/3]: Fix RustPkg/Tests in edkii-rust branch edk2-staging ayushdevel1325
2022-03-19 7:05 ` [PATCH v1 1/3] RustPkg/Test: Replace cargo-xbuild with build-std Ayush Singh
2022-03-19 7:05 ` [PATCH v1 2/3] RustPkg/Test/TestRustLangLib: Fix Building Ayush Singh
2022-03-19 7:05 ` [PATCH v1 3/3] RustPkg/Test/TestRustLangApp: Fix building Ayush Singh
2022-03-19 8:40 ` [edk2-devel] [PATCH v1 0/3]: Fix RustPkg/Tests in edkii-rust branch edk2-staging Marvin Häuser
2022-03-19 8:46 ` Ayush Singh
2022-03-19 13:59 ` Yao, Jiewen
2022-03-19 14:14 ` Ayush Singh [this message]
2022-03-19 14:36 ` Yao, Jiewen
2022-03-19 21:11 ` Ayush Singh
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=12779.1647699248664537510@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