From: Noel Ullreich <n.ullreich@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH pve-docs v7 0/1] update the PCI(e) docs
Date: Tue, 20 Jun 2023 14:14:40 +0200 [thread overview]
Message-ID: <20230620121441.64192-1-n.ullreich@proxmox.com> (raw)
This is a followup of Dominiks review:
https://lists.proxmox.com/pipermail/pve-devel/2023-June/057295.html
With the public wiki having been updated, I fixed the links.
Noel Ullreich (1):
update the PCI(e) docs
qm-pci-passthrough.adoc | 155 +++++++++++++++++++++++++++++++---------
qm.adoc | 2 +-
system-booting.adoc | 8 +++
3 files changed, 130 insertions(+), 35 deletions(-)
--
2.30.2
next reply other threads:[~2023-06-20 12:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 12:14 Noel Ullreich [this message]
2023-06-20 12:14 ` [pve-devel] [PATCH pve-docs v7 1/1] " Noel Ullreich
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=20230620121441.64192-1-n.ullreich@proxmox.com \
--to=n.ullreich@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