From: "Sean" <sean.brogan@microsoft.com>
To: Spottswood, Jason <jason.spottswood@hpe.com>,devel@edk2.groups.io
Subject: Re: [edk2-devel] Recent changes to EsrtFmp causing ASSERTs
Date: Tue, 01 Oct 2019 09:49:34 -0700 [thread overview]
Message-ID: <11067.1569948574783300209@groups.io> (raw)
In-Reply-To: <CS1PR8401MB1239E499F034196275A2968D93820@CS1PR8401MB1239.NAMPRD84.PROD.OUTLOOK.COM>
[-- Attachment #1: Type: text/plain, Size: 335 bytes --]
Jason/Mike,
What would you propose is done if the hw instance in 0 but an entry with same guid and instance 0 already exists?
Ignore it and first in wins?
It asserts because i am not aware of the right answer for the ESRT and it creates a situation with unpredictable results for capsule processing using ESRT.
Thanks
Sean
[-- Attachment #2: Type: text/html, Size: 397 bytes --]
next prev parent reply other threads:[~2019-10-01 16:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-30 20:48 Recent changes to EsrtFmp causing ASSERTs jason.spottswood
2019-09-30 20:52 ` [edk2-devel] " Rothman, Michael A
2019-09-30 21:23 ` jason.spottswood
2019-10-01 16:49 ` Sean [this message]
2019-10-01 17:30 ` Michael D Kinney
2019-10-01 21:20 ` Spottswood, Jason
2019-10-02 15:12 ` Michael D Kinney
2019-10-18 21:52 ` scott.wiginton
2019-10-19 1:03 ` Michael D Kinney
2019-10-21 13:12 ` scott.wiginton
2019-10-21 16:30 ` Michael D Kinney
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=11067.1569948574783300209@groups.io \
--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