public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: "Kinney, Michael D" <michael.d.kinney@intel.com>,
	"Sheng, W" <w.sheng@intel.com>,
	gaoliming <gaoliming@byosoft.com.cn>,
	"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Liu, Zhiguang" <zhiguang.liu@intel.com>,
	"Yao, Jiewen" <jiewen.yao@intel.com>,
	'Andrew Fish' <afish@apple.com>,
	"Feng, Roger" <roger.feng@intel.com>
Subject: Re: [PATCH] MdePkg/Include: Add CET instructions to Nasm.inc
Date: Tue, 2 Feb 2021 17:01:57 +0100	[thread overview]
Message-ID: <0c54dd3c-1b68-3d4c-69c9-1a8aa81b17ce@redhat.com> (raw)
In-Reply-To: <CO1PR11MB4929A53B8F577EDA8DB38592D2B59@CO1PR11MB4929.namprd11.prod.outlook.com>

On 02/02/21 16:21, Kinney, Michael D wrote:
> Hi Sheng,
> 
> I recommend we update required NASM version.
> 
> From your investigation, the new min version would be 2.15.01.

I'd be happy with that -- the Linux distros I primarily care about seem
to support a nasm version that's not earlier than this.

On my personal laptop, I'd have to build nasm from source, but that's OK.

Given the above, I'd like to avoid more DB-encoded instructions in edk2.

Thanks,
Laszlo


  reply	other threads:[~2021-02-02 16:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-29  2:34 [PATCH] MdePkg/Include: Add CET instructions to Nasm.inc Sheng Wei
2021-01-29  6:35 ` Yao, Jiewen
2021-01-29  8:32   ` Sheng Wei
2021-01-29  9:20     ` Yao, Jiewen
2021-01-29 17:22 ` Michael D Kinney
2021-01-29 19:03   ` Bret Barkelew
2021-02-02  2:43   ` 回复: " gaoliming
2021-02-02  3:38     ` Sheng Wei
2021-02-02  3:50       ` 回复: " gaoliming
2021-02-02 15:23         ` [edk2-devel] " Michael D Kinney
2021-02-02 15:21       ` Michael D Kinney
2021-02-02 16:01         ` Laszlo Ersek [this message]
2021-02-03  0:06         ` Sheng Wei
2021-02-03  2:01           ` 回复: " gaoliming

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=0c54dd3c-1b68-3d4c-69c9-1a8aa81b17ce@redhat.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