From: "Leif Lindholm" <quic_llindhol@quicinc.com>
To: <devel@edk2.groups.io>, <pedro.falcato@gmail.com>
Cc: "Kinney, Michael D" <michael.d.kinney@intel.com>,
"Lin, Benny" <benny.lin@intel.com>,
"Gao, Liming" <gaoliming@byosoft.com.cn>,
"Liu, Zhiguang" <zhiguang.liu@intel.com>,
Sean Brogan <sean.brogan@microsoft.com>,
Michael Kubacki <mikuback@linux.microsoft.com>,
Leif Lindholm <llindhol@qti.qualcomm.com>
Subject: Re: [edk2-devel] [PATCH 0/2] Support FDT library.
Date: Fri, 31 Mar 2023 13:17:52 +0100 [thread overview]
Message-ID: <ZCbPcLLROQBXUyWN@qc-i7.hemma.eciton.net> (raw)
In-Reply-To: <CAKbZUD2u_tG5uV_+T4WwgBwss2cX89fBD+mA34BkJA8TAZqvKg@mail.gmail.com>
On Fri, Mar 31, 2023 at 00:26:37 +0100, Pedro Falcato wrote:
> We also have a whole libc implementation in edk2-libc that seems to be
> permanently gathering dust until Intel touches it for Python purposes
> from time to time. So between crypto, libfdt, etc, could we try to
> unify things here a bit?
Personally, I'd quite like to nuke edk2-libc. The only effect I'm
seeing from it is that it keeps misleading people into believing it's
sensible to expect full POSIX compliance under UEFI, then embed those
expectations into their organisational workflows.
Meanwhile, it receives (next to) no security fixes.
/
Leif
next prev parent reply other threads:[~2023-03-31 12:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-30 16:52 [PATCH 0/2] Support FDT library benny.lin
2023-03-30 16:52 ` [PATCH 1/2] MdePkg: " Benny Lin
2023-03-30 17:01 ` Michael D Kinney
2023-03-30 23:19 ` [edk2-devel] " Pedro Falcato
2023-04-12 16:59 ` Benny Lin
2023-03-30 16:52 ` [PATCH 2/2] .pytool: " Benny Lin
2023-03-30 21:50 ` [edk2-devel] [PATCH 0/2] " Pedro Falcato
2023-03-30 22:59 ` Michael D Kinney
2023-03-30 23:26 ` Pedro Falcato
2023-03-30 23:32 ` Michael D Kinney
2023-03-31 2:35 ` Pedro Falcato
2023-03-31 11:39 ` Gerd Hoffmann
2023-03-31 12:18 ` Pedro Falcato
2023-03-31 12:17 ` Leif Lindholm [this message]
2023-03-31 12:12 ` Leif Lindholm
2023-04-01 1:29 ` Andrei Warkentin
2023-04-06 16:33 ` Sheng Lean Tan
2023-04-07 13:23 ` Pedro Falcato
2023-04-07 22:35 ` Andrei Warkentin
2023-04-07 23:04 ` Michael D Kinney
2023-04-11 13:19 ` Sheng Lean Tan
2023-04-11 16:07 ` Pedro Falcato
2023-04-11 17:00 ` 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=ZCbPcLLROQBXUyWN@qc-i7.hemma.eciton.net \
--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