public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: Michael D Kinney <michael.d.kinney@intel.com>,
	Liming Gao <liming.gao@intel.com>,  Ting Ye <ting.ye@intel.com>,
	Gang Wei <gang.wei@intel.com>,  Jian Wang <jian.j.wang@intel.com>,
	Chao Zhang <chao.b.zhang@intel.com>,
	 Jiewen Yao <jiewen.yao@intel.com>, Hao Wu <hao.a.wu@intel.com>,
	 Star Zeng <star.zeng@intel.com>,
	Achin Gupta <achin.gupta@arm.com>,
	 Jagadeesh Ujja <jagadeesh.ujja@arm.com>
Subject: Re: [PATCH 0/4] Various Packages: add MM_STANDALONE support
Date: Mon, 21 Jan 2019 13:43:49 +0100	[thread overview]
Message-ID: <CAKv+Gu8T5mPtA4o2_EAmxfXp1yq+qR3i9+-CAiXq2k2N8gbP-A@mail.gmail.com> (raw)
In-Reply-To: <20190116212221.7460-1-ard.biesheuvel@linaro.org>

On Wed, 16 Jan 2019 at 22:22, Ard Biesheuvel <ard.biesheuvel@linaro.org> wrote:
>
> Add MM_STANDALONE to the list of permitted module types of various
> libraries that are required to build the standalone MM authenticated
> variable stack.
>
> In some cases, this requires the MODULE_TYPE to be modified to BASE,
> given that the constructor prototype is different between DXE/UEFI
> and MM_STANDALONE drivers.
>
> Cc: Michael D Kinney <michael.d.kinney@intel.com>
> Cc: Liming Gao <liming.gao@intel.com>
> Cc: Ting Ye <ting.ye@intel.com>
> Cc: Gang Wei <gang.wei@intel.com>
> Cc: Jian Wang <jian.j.wang@intel.com>
> Cc: Chao Zhang <chao.b.zhang@intel.com>
> Cc: Jiewen Yao <jiewen.yao@intel.com>
> Cc: Hao Wu <hao.a.wu@intel.com>
> Cc: Star Zeng <star.zeng@intel.com>
> Cc: Achin Gupta <achin.gupta@arm.com>
> Cc: Jagadeesh Ujja <jagadeesh.ujja@arm.com>
>
> Ard Biesheuvel (4):
>   CryptoPkg/SmmCryptLib: permit use by MM_STANDALONE modules
>   SecurityPkg/PlatformSecureLibNull: permit use by MM_STANDALONE modules
>   MdeModulePkg/VarCheckLib: permit use by MM_STANDALONE modules
>   MdePkg/UefiDevicePathLib: permit use by MM_STANDALONE modules
>

Series pushed as 5c5ca9f1fbf8..f634e32db5b6

Thanks all!


  parent reply	other threads:[~2019-01-21 12:44 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-16 21:22 [PATCH 0/4] Various Packages: add MM_STANDALONE support Ard Biesheuvel
2019-01-16 21:22 ` [PATCH 1/4] CryptoPkg/SmmCryptLib: permit use by MM_STANDALONE modules Ard Biesheuvel
2019-01-18  7:05   ` Wang, Jian J
2019-01-18 11:12     ` Ard Biesheuvel
2019-01-21 12:36       ` Ard Biesheuvel
2019-01-21 12:40         ` Gao, Liming
2019-01-21 12:40           ` Ard Biesheuvel
2019-01-22  2:42             ` Ye, Ting
2019-01-16 21:22 ` [PATCH 2/4] SecurityPkg/PlatformSecureLibNull: " Ard Biesheuvel
2019-01-18  7:06   ` Wang, Jian J
2019-01-18 11:13     ` Ard Biesheuvel
2019-01-18 15:01       ` Yao, Jiewen
2019-01-16 21:22 ` [PATCH 3/4] MdeModulePkg/VarCheckLib: " Ard Biesheuvel
2019-01-18  7:06   ` Wang, Jian J
2019-01-18  8:15   ` Zeng, Star
2019-01-18 10:45     ` Zeng, Star
2019-01-16 21:22 ` [PATCH 4/4] MdePkg/UefiDevicePathLib: " Ard Biesheuvel
2019-01-18 11:07   ` Ard Biesheuvel
2019-01-21 12:37     ` Gao, Liming
2019-01-21 12:43 ` Ard Biesheuvel [this message]
2019-01-21 12:49   ` [PATCH 0/4] Various Packages: add MM_STANDALONE support Gao, Liming
2019-01-21 14:34     ` Ard Biesheuvel
2019-02-28 14:53       ` Ard Biesheuvel

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=CAKv+Gu8T5mPtA4o2_EAmxfXp1yq+qR3i9+-CAiXq2k2N8gbP-A@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