public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Marvin Häuser" <mhaeuser@posteo.de>
To: devel@edk2.groups.io, ayushdevel1325@gmail.com
Cc: jiewen.yao@intel.com
Subject: Re: [edk2-devel] [PATCH v1 0/3]: Fix RustPkg/Tests in edkii-rust branch edk2-staging
Date: Sat, 19 Mar 2022 08:40:04 +0000	[thread overview]
Message-ID: <97F1C97B-CD49-47AB-9041-A6EF2B21CCDA@posteo.de> (raw)
In-Reply-To: <20220319070553.25770-1-ayushdevel1325@gmail.com>



> On 19. Mar 2022, at 08:06, Ayush Singh <ayushdevel1325@gmail.com> wrote:
> 
> CC Jiewen Yao

You didn’t actually CC, done.

Best regards,
Marvin

> 
> This is my 2nd email about this patch to fix edkii-rust branch in
> edk2-staging repo, this time hopefully following contributing procedure
> better.
> 
> I have tried to to fix RustPkg/Test/HelloWorld,
> RustPkg/Test/HelloWorld2, RustPkg/Test/TestRustLangApp, and
> RustPkg/Test/TestRustLangLib. This also meant fixing
> RustPkg/Library/UefiRustIntrinsicLib and
> RustPkg/Library/UefiRustAllocationLib.
> 
> It is also not possible to build this branch with gcc-11 since that will
> require a rebase to edk2/master, but I am not sure how that can be done
> since edk2-staging/master does not track edk2/master like it is supposed
> to according to the edk2-staging/about branch.
> 
> My working repository for these commits can be found at: 
> https://github.com/Ayush1325/edk2-staging/tree/edkii-rust-fix-v1
> 
> Ayush Singh (3):
>  RustPkg/Test: Replace cargo-xbuild with build-std
>  RustPkg/Test/TestRustLangLib: Fix Building
>  RustPkg/Test/TestRustLangApp: Fix building
> 
> RustPkg/Library/UefiRustAllocationLib/src/lib.rs |  53 ++--
> RustPkg/Library/UefiRustIntrinsicLib/src/lib.rs  |   8 -
> RustPkg/Test/HelloWorld/.cargo/config.toml       |   3 +
> RustPkg/Test/HelloWorld2/.cargo/config.toml      |   3 +
> RustPkg/Test/TestRustLangApp/.cargo/config.toml  |   3 +
> RustPkg/Test/TestRustLangApp/src/main.rs         |  95 +++----
> RustPkg/Test/TestRustLangLib/.cargo/config.toml  |   3 +
> RustPkg/Test/TestRustLangLib/src/lib.rs          | 264 ++++++++------------
> 8 files changed, 186 insertions(+), 246 deletions(-)
> create mode 100644 RustPkg/Test/HelloWorld/.cargo/config.toml
> create mode 100644 RustPkg/Test/HelloWorld2/.cargo/config.toml
> create mode 100644 RustPkg/Test/TestRustLangApp/.cargo/config.toml
> create mode 100644 RustPkg/Test/TestRustLangLib/.cargo/config.toml
> 
> -- 
> 2.35.1
> 
> 
> 
> 
> 
> 


  parent reply	other threads:[~2022-03-19  8:40 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 ` Marvin Häuser [this message]
2022-03-19  8:46   ` [edk2-devel] [PATCH v1 0/3]: Fix RustPkg/Tests in edkii-rust branch edk2-staging Ayush Singh
2022-03-19 13:59   ` Yao, Jiewen
2022-03-19 14:14     ` Ayush Singh
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=97F1C97B-CD49-47AB-9041-A6EF2B21CCDA@posteo.de \
    --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