From: bugzilla-daemon@kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 220726] New: Patch of ioctl_vt (2), small clarification.
Date: Fri, 31 Oct 2025 04:41:33 +0000 [thread overview]
Message-ID: <bug-220726-11311@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=220726
Bug ID: 220726
Summary: Patch of ioctl_vt (2), small clarification.
Product: Documentation
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: man-pages
Assignee: documentation_man-pages@kernel-bugs.osdl.org
Reporter: teika@gmx.com
Regression: No
Created attachment 308874
--> https://bugzilla.kernel.org/attachment.cgi?id=308874&action=edit
Patch of man/man2/ioctl_vt.2
Let me submit a patch of the man page ioctl_vt (2), which clarifies a bit.
I also have a comment in this page about the struct vt_mode in VT_SETMODE. It
has the member "waitv", which does not seem to be meaningful any more today.
It is because among all files in the kernel source drivers/tty/, it is only
refered once, in vt/vt_ioctl.c, in the line:
vc->vt_mode.waitv = 0;
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2025-10-31 4:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 4:41 bugzilla-daemon [this message]
2025-10-31 9:45 ` [Bug 220726] Patch of ioctl_vt (2), small clarification bugzilla-daemon
2025-11-10 7:30 ` bugzilla-daemon
2025-11-10 10:11 ` Alejandro Colomar
2025-11-10 7:32 ` bugzilla-daemon
2025-11-10 7:32 ` bugzilla-daemon
2025-11-10 10:11 ` bugzilla-daemon
2025-12-13 8:00 ` bugzilla-daemon
2025-12-13 15:36 ` bugzilla-daemon
2025-12-13 15:37 ` bugzilla-daemon
2025-12-13 15:41 ` bugzilla-daemon
2025-12-15 5:41 ` bugzilla-daemon
2025-12-15 10:20 ` bugzilla-daemon
2025-12-15 11:52 ` bugzilla-daemon
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=bug-220726-11311@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-man@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.