From: Lukas Wagner <l.wagner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH manager] configs: blacklist: fix typo
Date: Fri, 31 Mar 2023 14:45:15 +0200 [thread overview]
Message-ID: <20230331124515.392786-1-l.wagner@proxmox.com> (raw)
Signed-off-by: Lukas Wagner <l.wagner@proxmox.com>
---
configs/pve-blacklist.conf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/configs/pve-blacklist.conf b/configs/pve-blacklist.conf
index 9687961d..27d1be48 100644
--- a/configs/pve-blacklist.conf
+++ b/configs/pve-blacklist.conf
@@ -1,4 +1,4 @@
# This file contains a list of modules which are not supported by Proxmox VE
-# nidiafb see bugreport https://bugzilla.proxmox.com/show_bug.cgi?id=701
+# nvidiafb see bugreport https://bugzilla.proxmox.com/show_bug.cgi?id=701
blacklist nvidiafb
--
2.30.2
next reply other threads:[~2023-03-31 12:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 12:45 Lukas Wagner [this message]
2023-04-12 11:26 ` [pve-devel] applied: " 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=20230331124515.392786-1-l.wagner@proxmox.com \
--to=l.wagner@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