From: Filip Schauer <f.schauer@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH v5 manager 0/2] add edit window for device passthrough
Date: Wed, 17 Apr 2024 10:44:17 +0200 [thread overview]
Message-ID: <20240417084419.37338-1-f.schauer@proxmox.com> (raw)
Changes since v4:
* Simplify cbind
* Fix selection of custom devid not being applied on creation in
onGetValues
Changes since v3:
* Pass confid in via cbind instead of manually setting it in the view
model
* Check me.isCreate instead of !me.confid for whether to find the next
free device slot
Changes since v2:
* Clarify naming of mount point and device passthrough related utils
* Remove unnecessary cbind
* Make the device index selectible
* Add default values as emptyText to the UI elements
* Reorder UI elements to improve the layout
* Disable the Device Passthrough menu entries for non-root users
* Change var to let
* Minor code cleanup of DeviceEdit.js
Changes since v1:
* Remove usb mapping
* Add mode, uid and gid fields
Filip Schauer (2):
utils: clarify naming of LXC mount point utils
ui: lxc: add edit window for device passthrough
www/manager6/Makefile | 1 +
www/manager6/Utils.js | 23 ++-
www/manager6/lxc/DeviceEdit.js | 176 +++++++++++++++++++++++
www/manager6/lxc/MPEdit.js | 4 +-
www/manager6/lxc/MultiMPEdit.js | 4 +-
www/manager6/lxc/Resources.js | 33 ++++-
www/manager6/window/GuestDiskReassign.js | 6 +-
7 files changed, 232 insertions(+), 15 deletions(-)
create mode 100644 www/manager6/lxc/DeviceEdit.js
--
2.39.2
next reply other threads:[~2024-04-17 8:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-17 8:44 Filip Schauer [this message]
2024-04-17 8:44 ` [pve-devel] [PATCH v5 manager 1/2] utils: clarify naming of LXC mount point utils Filip Schauer
2024-04-17 8:44 ` [pve-devel] [PATCH v5 manager 2/2] ui: lxc: add edit window for device passthrough Filip Schauer
2024-04-17 9:54 ` [pve-devel] applied: [PATCH v5 manager 0/2] " Thomas Lamprecht
2024-04-17 10:03 ` Filip Schauer
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=20240417084419.37338-1-f.schauer@proxmox.com \
--to=f.schauer@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