From: "Yao, Jiewen" <jiewen.yao@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"Yao, Jiewen" <jiewen.yao@intel.com>,
"Sun, Tengfen" <tengfen.sun@intel.com>
Cc: "Wu, Chris" <chris.wu@intel.com>,
"Gao, Liming" <liming.gao@intel.com>,
"Richardson, Brian" <brian.richardson@intel.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] [staging/HBFA][PATCH] Announce to create "HBFA" branch in edk2-staging.
Date: Wed, 1 May 2019 23:04:59 +0000 [thread overview]
Message-ID: <74D8A39837DF1E4DA445A8C0B3885C503F62035E@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <159A1B40D5D847B3.5414@groups.io>
[-- Attachment #1: Type: text/plain, Size: 2121 bytes --]
Hi Tengfen
I talked with Mike Kinney today on how to resolve the prebuild binary.
One thought is that we may improve the current build process - to use git submodule for cmocka - git://git.cryptomilk.org/projects/cmocka.git
Another idea is generate prebuild binary, but that is compiler specific.
Thank you
Yao Jiewen
From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of Yao, Jiewen
Sent: Monday, April 29, 2019 6:10 PM
To: Sun, Tengfen <tengfen.sun@intel.com>; devel@edk2.groups.io
Cc: Wu, Chris <chris.wu@intel.com>; Gao, Liming <liming.gao@intel.com>; Richardson, Brian <brian.richardson@intel.com>; Kinney, Michael D <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] [staging/HBFA][PATCH] Announce to create "HBFA" branch in edk2-staging.
Thank you Tengfen.
When you create official edk2-staging branch, would you please also add edk2 repo to the same staging-project ?
I think we may need submit some patch to update both edk2 and HBFA at same time.
Thank you
Yao Jiewen
From: Sun, Tengfen
Sent: Tuesday, April 23, 2019 7:21 PM
To: devel@edk2.groups.io<mailto:devel@edk2.groups.io>
Cc: Yao, Jiewen <jiewen.yao@intel.com<mailto:jiewen.yao@intel.com>>; Wu, Chris <chris.wu@intel.com<mailto:chris.wu@intel.com>>; Sun, Tengfen <tengfen.sun@intel.com<mailto:tengfen.sun@intel.com>>; Gao, Liming <liming.gao@intel.com<mailto:liming.gao@intel.com>>; Richardson, Brian <brian.richardson@intel.com<mailto:brian.richardson@intel.com>>; Kinney, Michael D <michael.d.kinney@intel.com<mailto:michael.d.kinney@intel.com>>
Subject: [staging/HBFA][PATCH] Announce to create "HBFA" branch in edk2-staging.
I have created a branch for evaluation version of Host-based Firmware Analyzer (HBFA) in my fork edk2-staging repo: https://github.com/tengfens/edk2-staging/tree/HBFA
Please refer to the Readme.md in above link to get the detail feature introduction and refer to wiki page in my fork repo to get execution and development content.
Note: The branch will be created in edk2-staging by the end of April if no objection.
Thanks & Best Regards,
Sun, Tengfen
[-- Attachment #2: Type: text/html, Size: 8165 bytes --]
prev parent reply other threads:[~2019-05-01 23:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 2:20 [staging/HBFA][PATCH] Announce to create "HBFA" branch in edk2-staging Sun, Tengfen
2019-04-30 1:09 ` Yao, Jiewen
[not found] ` <159A1B40D5D847B3.5414@groups.io>
2019-05-01 23:04 ` Yao, Jiewen [this message]
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=74D8A39837DF1E4DA445A8C0B3885C503F62035E@shsmsx102.ccr.corp.intel.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