From: "Sami Mujawar" <sami.mujawar@arm.com>
To: Sami Mujawar <sami.mujawar@arm.com>,devel@edk2.groups.io
Subject: Re: [edk2-devel] [PATCH v3 0/4] ArmPkg/SecurityPkg: Fixes for ArmTrngLib/RngDxe
Date: Wed, 07 Dec 2022 01:04:52 -0800 [thread overview]
Message-ID: <10014.1670403892000042111@groups.io> (raw)
In-Reply-To: <10752.1670403198331721857@groups.io>
[-- Attachment #1: Type: text/plain, Size: 297 bytes --]
Apologies, I accidentally sent the message before I finished. The remaining part of my reply is as below.
I think having the asserts in ProcessLibraryConstructorList() creates more problem. It is very hard to debug issues if the serial port initialisation fails.
Regards,
Sami Mujawar
[-- Attachment #2: Type: text/html, Size: 36698 bytes --]
next prev parent reply other threads:[~2022-12-07 9:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 16:17 [PATCH v3 0/4] ArmPkg/SecurityPkg: Fixes for ArmTrngLib/RngDxe PierreGondois
2022-11-24 16:17 ` [PATCH v3 1/4] ArmPkg/ArmTrngLib: Remove ASSERTs in ArmTrngLibConstructor() PierreGondois
2022-11-24 16:17 ` [PATCH v3 2/4] SecurityPkg/RngDxe: Correctly update mAvailableAlgoArrayCount PierreGondois
2022-11-24 16:17 ` [PATCH v3 3/4] SecurityPkg/RngDxe: Conditionally install EFI_RNG_PROTOCOL PierreGondois
2022-11-24 16:17 ` [PATCH v3 4/4] SecurityPkg/RngDxe: Fix Rng algo selection for Arm PierreGondois
2022-11-26 14:33 ` [PATCH v3 0/4] ArmPkg/SecurityPkg: Fixes for ArmTrngLib/RngDxe Ard Biesheuvel
2022-11-28 13:34 ` PierreGondois
2022-12-07 8:53 ` [edk2-devel] " Sami Mujawar
2022-12-07 9:04 ` Sami Mujawar [this message]
[not found] ` <172BC2FE233A5592.368@groups.io>
2023-01-09 12:26 ` PierreGondois
2023-02-10 9:26 ` PierreGondois
[not found] ` <17426C66FE22D73E.5513@groups.io>
2023-03-06 15:37 ` PierreGondois
2023-03-06 15:42 ` Yao, Jiewen
2023-03-06 16:22 ` Ard Biesheuvel
2023-03-06 17:09 ` PierreGondois
2023-03-06 17:36 ` Ard Biesheuvel
2023-03-07 7:53 ` Yao, Jiewen
2023-03-07 15:38 ` 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=10014.1670403892000042111@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