From: Friedrich Weber <f.weber@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] superseded: [PATCH edk2-firmware] fix #6430: backport patch to fix split lock detection warnings
Date: Thu, 10 Jul 2025 14:54:35 +0200 [thread overview]
Message-ID: <1e32a949-e28e-4d3c-9a63-48928faf10fd@proxmox.com> (raw)
In-Reply-To: <20250710121331.142188-1-f.weber@proxmox.com>
Superseded by:
https://lore.proxmox.com/pve-devel/20250710125029.149536-1-f.weber@proxmox.com/T/#u
Noticed a few annoying typos right after sending, which prompted me to
rephrase the commit message altogether. Sorry for the noise.
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2025-07-10 12:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-10 12:13 [pve-devel] " Friedrich Weber
2025-07-10 12:54 ` Friedrich Weber [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-all 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=1e32a949-e28e-4d3c-9a63-48928faf10fd@proxmox.com \
--to=f.weber@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/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