From: Alexander Zeidler <a.zeidler@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH v2 docs] sysadmin: add section 'Firmware Updates' and references
Date: Mon, 11 Sep 2023 12:27:00 +0200 [thread overview]
Message-ID: <f482e257abed6b4a2565a419afe57accfdb220ad.camel@proxmox.com> (raw)
In-Reply-To: <20230728132112.96386-1-a.zeidler@proxmox.com>
On Fri, 2023-07-28 at 15:21 +0200, Alexander Zeidler wrote:
> Firmware updates are important, their existence should not be checked
> only when there are already noticeable problems.
>
> Signed-off-by: Alexander Zeidler <a.zeidler@proxmox.com>
Ping. Still applies on master.
Would be of interest, see e.g.:
[PVE-User] EPYC ZEN gen1 migration success after installing amd64
microcode (FYI)
https://lists.proxmox.com/pipermail/pve-user/2023-September/017223.html
next prev parent reply other threads:[~2023-09-11 10:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 13:21 Alexander Zeidler
2023-09-11 10:27 ` Alexander Zeidler [this message]
2023-09-20 9:59 ` Dominik Csapak
2023-09-20 13:26 ` Thomas Lamprecht
2023-09-21 13:17 ` [pve-devel] applied: " Thomas Lamprecht
2023-09-21 13:50 ` Thomas Lamprecht
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=f482e257abed6b4a2565a419afe57accfdb220ad.camel@proxmox.com \
--to=a.zeidler@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