From: "Richardson, Brian" <brian.richardson@intel.com>
To: Leif Lindholm <leif.lindholm@linaro.org>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>,
"Jin, Eric" <eric.jin@intel.com>
Subject: Re: SCT bugzilla topic?
Date: Mon, 3 Dec 2018 18:30:03 +0000 [thread overview]
Message-ID: <80AC2BAA3152784F98F581129E5CF5AFBD71C81A@ORSMSX112.amr.corp.intel.com> (raw)
In-Reply-To: <20181203144638.yubyuhzwso73hrs5@bivouac.eciton.net>
I think "EDK2 Test product with an SCT component" is the best option.
Thanks ... br
---
Brian Richardson -- Director, Firmware Ecosystem Development
brian.richardson@intel.com -- @intel_brian (Twitter & WeChat)
https://software.intel.com/en-us/meet-the-developers/evangelists/team/brian-richardson
-----Original Message-----
From: edk2-devel <edk2-devel-bounces@lists.01.org> On Behalf Of Leif Lindholm
Sent: Monday, December 3, 2018 9:47 AM
To: edk2-devel@lists.01.org
Cc: Kinney, Michael D <michael.d.kinney@intel.com>; Jin, Eric <eric.jin@intel.com>
Subject: [edk2] SCT bugzilla topic?
Hi Eric, Supreeth, Mike,
I was looking to raise a feature request on UEFI SCT and didn't spot such a product. Should we create one?
Or perhaps we should have an EDK2 Test product with an SCT component?
Regards,
Leif
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2018-12-03 18:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-03 14:46 SCT bugzilla topic? Leif Lindholm
2018-12-03 18:30 ` Richardson, Brian [this message]
2018-12-03 19:36 ` Supreeth Venkatesh
2018-12-10 2:18 ` Jin, Eric
2018-12-10 3:02 ` Kinney, Michael D
2018-12-10 8:13 ` Leif Lindholm
2018-12-10 8:43 ` Jin, Eric
2018-12-10 16:40 ` Supreeth Venkatesh
2018-12-10 17:37 ` Kinney, Michael D
2018-12-10 17:51 ` Supreeth Venkatesh
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=80AC2BAA3152784F98F581129E5CF5AFBD71C81A@ORSMSX112.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