From: "Maciej Rabeda" <maciej.rabeda@linux.intel.com>
To: devel@edk2.groups.io, sivaramann@amiindia.co.in
Cc: Lavanya Paneerselvam <lavanyap@ami.com>
Subject: Re: [edk2-devel] reg: RNG functions Usage in NetworkPkg
Date: Tue, 16 Feb 2021 14:09:44 +0100 [thread overview]
Message-ID: <9c0d93b4-27b2-7991-a3f3-fcc157f90098@linux.intel.com> (raw)
In-Reply-To: <B4DE137BDB63634BAC03BD9DE765F19702E3DCF640@VENUS1.in.megatrends.com>
[-- Attachment #1: Type: text/plain, Size: 1176 bytes --]
Hi Siva,
I am not proactively trying to change that.
NET_RANDOM is used throughout the network stack and touching it would
require solid regression.
Is there any defect requiring such a change?
Thanks,
Maciej
On 12-Feb-21 06:52, Sivaraman Nainar wrote:
>
> Hello Maciej:
>
> Do you have any comment on this.
>
> -Siva
>
> *From:* devel@edk2.groups.io [mailto:devel@edk2.groups.io] *On Behalf
> Of *Sivaraman Nainar
> *Sent:* Thursday, February 4, 2021 10:05 AM
> *To:* Rabeda, Maciej; devel@edk2.groups.io
> *Cc:* Lavanya Paneerselvam
> *Subject:* [edk2-devel] reg: RNG functions Usage in NetworkPkg
>
> Hello Maciej:
>
> Do we have any plan to use the RNG Library function in the Macro
> “*NET_RANDOM” *of NetworkPkg.
>
> **
>
> NET_RANDOM can use *GetRandomNumber32() *which is more reliable right?
>
> **
>
> Thanks
>
> Siva
>
> This e-mail is intended for the use of the addressee only and may
> contain privileged, confidential, or proprietary information that is
> exempt from disclosure under law. If you have received this message in
> error, please inform us promptly by reply e-mail, then delete the
> e-mail and destroy any printed copy. Thank you.
>
>
[-- Attachment #2: Type: text/html, Size: 5215 bytes --]
next prev parent reply other threads:[~2021-02-16 13:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1660715EBDF480CD.8308@groups.io>
2021-02-12 5:52 ` reg: RNG functions Usage in NetworkPkg Sivaraman Nainar
2021-02-16 13:09 ` Maciej Rabeda [this message]
2021-02-17 9:31 ` [edk2-devel] " Sivaraman Nainar
2021-02-22 17:12 ` Maciej Rabeda
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=9c0d93b4-27b2-7991-a3f3-fcc157f90098@linux.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