From: "Laszlo Ersek" <lersek@redhat.com>
To: Oliver Steffen <osteffen@redhat.com>,
devel@edk2.groups.io, gaoliming@byosoft.com.cn
Cc: Bob Feng <bob.c.feng@intel.com>, Rebecca Cran <rebecca@bsdio.com>,
Yuwei Chen <yuwei.chen@intel.com>,
Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: 回复: [edk2-devel] [PATCH v1 1/1] MdeModulePkg: Warn if out of flash space when writing variables
Date: Tue, 5 Mar 2024 15:34:03 +0100 [thread overview]
Message-ID: <558c78ba-6b94-4bf6-ff57-4d3111dae4be@redhat.com> (raw)
In-Reply-To: <CA+bRGFqJGPGAFGBY_pjJWoRZsbGm+ffyf9LHxYQwK=Pkm9DBmQ@mail.gmail.com>
On 3/5/24 13:44, Oliver Steffen wrote:
> The root cause is of course not addressed by this, but it might also be
> hard to solve. One would have to identify obsolete network/hardware
> settings somehow, but there is no way to tell if a certain NIC/MAC
> might come back at a later point or not.
Tricky because, even if you could identify a non-volatile variable named
after a MAC that matched *no* NIC in the system, you still might not
want to remove that variable. What if the user unplugged the NIC only
temporarily, and "wanted their settings back" upon re-plugging the NIC?
Laszlo
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#116395): https://edk2.groups.io/g/devel/message/116395
Mute This Topic: https://groups.io/mt/104735640/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2024-03-05 14:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 15:18 [edk2-devel] [PATCH v1 0/1] MdeModulePkg: Warn if out of flash space when writing variables Oliver Steffen
2024-03-04 15:18 ` [edk2-devel] [PATCH v1 1/1] " Oliver Steffen
2024-03-04 17:26 ` Laszlo Ersek
2024-03-05 0:40 ` 回复: " gaoliming via groups.io
2024-03-05 7:33 ` Laszlo Ersek
2024-03-05 12:44 ` Oliver Steffen
2024-03-05 14:34 ` Laszlo Ersek [this message]
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=558c78ba-6b94-4bf6-ff57-4d3111dae4be@redhat.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