From: "Agyeman, Prince" <prince.agyeman@intel.com>
To: "Carsey, Jaben" <jaben.carsey@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [edk2-platforms][PATCH v2 0/2] Adding python build scripts to ClevoOpenBoardPkg , KabylakeOpenBoardPkg and PurleyOpenBoardPkg
Date: Mon, 1 Apr 2019 21:43:35 +0000 [thread overview]
Message-ID: <C056AECA201D3845A68E4107509B7A0D4C28BE91@ORSMSX106.amr.corp.intel.com> (raw)
In-Reply-To: <CB6E33457884FA40993F35157061515CBCBCA2AC@FMSMSX103.amr.corp.intel.com>
- Added python build scripts to edk2-platforms/Platform/Intel /ClevoOpenBoardPkg , KabylakeOpenBoardPkg and PurleyOpenBoardPkg
in v1
- Cc'ed a edk2-platforms maintainer Michael A Kubacki <michael.a.kubacki@intel.com> in v2
Prince
-----Original Message-----
From: Carsey, Jaben
Sent: Monday, April 1, 2019 2:17 PM
To: Agyeman, Prince <prince.agyeman@intel.com>; edk2-devel@lists.01.org
Subject: RE: [edk2] [edk2-platforms][PATCH v2 0/2] Adding python build scripts to ClevoOpenBoardPkg , KabylakeOpenBoardPkg and PurleyOpenBoardPkg
Blurb missing.
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> Agyeman
> Sent: Monday, April 01, 2019 2:14 PM
> To: edk2-devel@lists.01.org
> Subject: [edk2] [edk2-platforms][PATCH v2 0/2] Adding python build
> scripts to ClevoOpenBoardPkg , KabylakeOpenBoardPkg and
> PurleyOpenBoardPkg
>
> *** BLURB HERE ***
>
> Agyeman (2):
> Platform/Intel: Added python build script.
> ReadMe.md: Update the build instructions
>
> Platform/Intel/BuildBios.py | 866 ++++++++++++++++++
> .../ClevoOpenBoardPkg/N1xxWU/buildConfig.json | 31 +
> .../KabylakeRvp3/BuildEx.py | 17 +
> .../KabylakeRvp3/buildConfig.json | 32 +
> .../BoardMtOlympus/BuildBoard.py | 100 ++
> .../BoardMtOlympus/buildConfig.json | 35 +
> Platform/Intel/build.json | 55 ++
> ReadMe.md | 14 +
> 8 files changed, 1150 insertions(+)
> create mode 100644 Platform/Intel/BuildBios.py create mode 100644
> Platform/Intel/ClevoOpenBoardPkg/N1xxWU/buildConfig.json
> create mode 100644
> Platform/Intel/KabylakeOpenBoardPkg/KabylakeRvp3/BuildEx.py
> create mode 100644
> Platform/Intel/KabylakeOpenBoardPkg/KabylakeRvp3/buildConfig.json
> create mode 100644
> Platform/Intel/PurleyOpenBoardPkg/BoardMtOlympus/BuildBoard.py
> create mode 100644
> Platform/Intel/PurleyOpenBoardPkg/BoardMtOlympus/buildConfig.json
> create mode 100644 Platform/Intel/build.json
>
> --
> 2.19.1.windows.1
>
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
prev parent reply other threads:[~2019-04-01 21:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 21:13 [edk2-platforms][PATCH v2 0/2] Adding python build scripts to ClevoOpenBoardPkg , KabylakeOpenBoardPkg and PurleyOpenBoardPkg Agyeman
2019-04-01 21:13 ` [edk2-platforms][PATCH v2 1/2] Platform/Intel: Added python build script Agyeman
2019-04-02 22:44 ` Kubacki, Michael A
2019-04-01 21:13 ` [edk2-platforms][PATCH v2 2/2] ReadMe.md: Update the build instructions Agyeman
2019-04-02 23:01 ` Kubacki, Michael A
2019-04-01 21:17 ` [edk2-platforms][PATCH v2 0/2] Adding python build scripts to ClevoOpenBoardPkg , KabylakeOpenBoardPkg and PurleyOpenBoardPkg Carsey, Jaben
2019-04-01 21:43 ` Agyeman, Prince [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=C056AECA201D3845A68E4107509B7A0D4C28BE91@ORSMSX106.amr.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