Skip to contentSkip to conversation

New: Patch of ioctl_vt (2), small clarification.

Bug 220726 [email protected] 2 participants 14 messages Oct 31, 2025 – Dec 15, 2025 Man-pages: manual pages for Linux -- Sections 2, 3, 4, 5, and 7

lore
Share & tools
lore
#0 lore 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: [email protected]
Reporter: [email protected]
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;

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.
#1 lore raw

[Bug 220726] Patch of ioctl_vt (2), small clarification.

https://bugzilla.kernel.org/show_bug.cgi?id=220726

--- Comment #1 from Alejandro Colomar ([email protected]) --- Hi,

Quoted 22 lines · On Fri, Oct 31, 2025 at 04:41:33AM +0000, [email protected] wrote:

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: [email protected]
Reporter: [email protected]
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.

Quoted 13 lines

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;

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

Would you mind sending the patch to the mailing list? Please see

        $ cat CONTRIBUTING
        Name
               Contributing - instructions for contributing to the project

Synopsis
Mailing list, patches, lint & check, style guide, bug reports, and more.

Description
The main discussions regarding development of the project, patches, bugs, news, doubts, etc. happen on the mailing list. To send an email to the project, send it to Alejandro and CC the mailing list:

To: Alejandro Colomar <[email protected]>
Cc: <[email protected]>

Files
CONTRIBUTING.d/git
Instructions for configuring git(1).

CONTRIBUTING.d/mail
Instructions for sending emails to the project

CONTRIBUTING.d/patches/
Instructions for contributing patches

CONTRIBUTING.d/bugs
Instructions for reporting bugs

CONTRIBUTING.d/lint
Instructions for linting manual pages

CONTRIBUTING.d/external_pages
Pages imported or generated from other projects

CONTRIBUTING.d/style
Preferred layout of manual pages and style guide notes

See also
<https://www.kernel.org/doc/man-pages/missing_pages.html>

and

        $ cat CONTRIBUTING.d/patches/patches
        Name
                patches/patches - instructions for contributing patches

Description
If you know how to fix a problem in a manual page (if not, see <CONTRIBUTING.d/bugs>), then send a patch in an email.

Configure git(1) for this project. See <CONTRIBUTING.d/git>.

Send logically separate patches. For logically-separate
issues,
send separate emails. For related issues, send a patch set
with
a cover letter that gives an overview of all of the patches,
and
each patch should be a reply to the cover-letter mail. We recommend using git-format-patch(1) for preparing the patches.

Patches should contain a description alongside the diff. A
diff
without a description is mostly useless. See <CONTRIBUTING.d/patches/description>.

Have a lovely day!
Alex

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.
#2 lore raw

[Bug 220726] Patch of ioctl_vt (2), small clarification.

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=220726

--- Comment #2 from teika kazura ([email protected]) --- Created attachment 308927
--> https://bugzilla.kernel.org/attachment.cgi?id=308927&action=edit
VT_SETMODE demontration in python.

Ok, I'll soon (TM) post to the mailing list. Now I close this entry as INVALID.

The attachment is a python code that demonstrates the VT_SETMODE ioctl. It is for reference.

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.
#3 lore raw

Re: [Bug 220726] Patch of ioctl_vt (2), small clarification.

Hi Teika,

Quoted 8 lines · On Mon, Nov 10, 2025 at 07:30:42AM +0000, [email protected] wrote:

https://bugzilla.kernel.org/show_bug.cgi?id=220726

--- Comment #2 from teika kazura ([email protected]) --- Created attachment 308927
--> https://bugzilla.kernel.org/attachment.cgi?id=308927&action=edit
VT_SETMODE demontration in python.

Ok, I'll soon (TM) post to the mailing list. Now I close this entry as INVALID.

You don't need to close the bug. You could keep it open until we fix it.

It's just that we discuss patches in the mailing list.

Have a lovely day!
Alex

Signature · 2 lines
<https://www.alejandro-colomar.es>
Use port 80 (that is, <...:80/>).
#4 lore raw

[Bug 220726] Patch of ioctl_vt (2), small clarification.

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=220726

teika kazura ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------

             Status|NEW                         |RESOLVED
         Resolution|---                         |INVALID

--- Comment #3 from teika kazura ([email protected]) --- Now I close this bug.

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.
#5 lore raw

[Bug 220726] Patch of ioctl_vt (2), small clarification.

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=220726

--- Comment #4 from teika kazura ([email protected]) --- Created attachment 308928
--> https://bugzilla.kernel.org/attachment.cgi?id=308928&action=edit
VT_WAITACTIVE demo in python.

VT_WAITACTIVE demo in python.

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.
#6 lore raw

[Bug 220726] Patch of ioctl_vt (2), small clarification.

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=220726

--- Comment #5 from Alejandro Colomar ([email protected]) --- Hi Teika,

Quoted 9 lines · On Mon, Nov 10, 2025 at 07:30:42AM +0000, [email protected] wrote:

https://bugzilla.kernel.org/show_bug.cgi?id=220726

--- Comment #2 from teika kazura ([email protected]) --- Created attachment 308927
--> https://bugzilla.kernel.org/attachment.cgi?id=308927&action=edit
VT_SETMODE demontration in python.

Ok, I'll soon (TM) post to the mailing list. Now I close this entry as INVALID.

You don't need to close the bug. You could keep it open until we fix it.

It's just that we discuss patches in the mailing list.

Have a lovely day!
Alex

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.
#7 lore raw

[Bug 220726] Patch of ioctl_vt (2), small clarification.

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=220726

teika kazura ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------

 Attachment #308874|0                           |1

is obsolete| |

--- Comment #6 from teika kazura ([email protected]) --- Created attachment 309016
--> https://bugzilla.kernel.org/attachment.cgi?id=309016&action=edit
My version of vt_ioctl.2

This is the third version of vt_ioctl.2. Unlike preceding versions this is not a patch, but the entire file. The second version was posted to the mailing list:
<https://lore.kernel.org/linux-man/[email protected]/T/#u>.
The accuracy was justified in the post cited above (and follow up emails.)

My contribution is released to the public domain. I don't post the corresponding patch, but it is based on the git HEAD as of today, i.e.
<https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/commit/man/man2/ioctl_vt.2?id=9fbe82>.

The project refuses my work to merge because of not complying with its policy about the use of AIs. I believe my improvement helps, so hereby post for the community's sake.

Best regards.

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.
#8 lore raw

[Bug 220726] Patch of ioctl_vt (2), small clarification.

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=220726

Alejandro Colomar ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.
#9 lore raw

[Bug 220726] Patch of ioctl_vt (2), small clarification.

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=220726

Alejandro Colomar ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------

      Comment #6 is|1                           |0

private| |

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.
#10 lore raw

[Bug 220726] Patch of ioctl_vt (2), small clarification.

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=220726

--- Comment #7 from Alejandro Colomar ([email protected]) --- Hi Teika,

Quoted 22 lines · On Sat, Dec 13, 2025 at 08:00:04AM +0000, [email protected] wrote:

https://bugzilla.kernel.org/show_bug.cgi?id=220726

teika kazura ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------

 Attachment #308874|0                           |1

is obsolete| |

--- Comment #6 from teika kazura ([email protected]) --- Created attachment 309016
--> https://bugzilla.kernel.org/attachment.cgi?id=309016&action=edit
My version of vt_ioctl.2

This is the third version of vt_ioctl.2. Unlike preceding versions this is not
a patch, but the entire file. The second version was posted to the mailing list:

<https://lore.kernel.org/linux-man/[email protected]/T/#u>.
The accuracy was justified in the post cited above (and follow up emails.)

Quoted 8 lines

My contribution is released to the public domain. I don't post the corresponding patch, but it is based on the git HEAD as of today, i.e.

<https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/commit/man/man2/ioctl_vt.2?id=9fbe82>.

The project refuses my work to merge because of not complying with its policy about the use of AIs. I believe my improvement helps, so hereby post for the community's sake.

We don't refuse to take your work. You seem to refuse to follow our policies. You're welcome to do work that is clean of AI, and we'll consider it. But AI-derived code will not be accepted anywhere in this project, including the bugzilla. I've marked the attachment as private.

Have a lovely day!
Alex

Quoted 2 lines

Best regards.

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.
#11 lore raw

[Bug 220726] Patch of ioctl_vt (2), small clarification.

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=220726

--- Comment #8 from teika kazura ([email protected]) ---
Hi. Hiding my last post here is wrong, because mine was done outside the man-pages project. Manual pages are GPL'd and anyone can do anything as long as they obey the license. You don't have the right to do it. Everyone mistakes and that's ok, but lift it.

Also remember kernel bugzilla is not only for man-pages, and at least the kernel itself does not have any policy about the AI use. I know my post does not directly help any projects hosted here right now, but I'm not spamming either.

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.
#12 lore raw

[Bug 220726] Patch of ioctl_vt (2), small clarification.

In reply to [email protected]

https://bugzilla.kernel.org/show_bug.cgi?id=220726

--- Comment #9 from Alejandro Colomar ([email protected]) --- (In reply to teika kazura from comment #8)

Quoted 2 lines

Hi. Hiding my last post here is wrong, because mine was done outside the man-pages project.

This is part of the Linux man-pages project. Look at "component" up.

Quoted 2 lines

Manual pages are GPL'd and anyone can do anything as long as they obey the license.

You're of course free to do anything in your website. But that license doesn't give you a right to publish anything in the project infrastructure.

Quoted 2 lines

You don't have the right to do it. Everyone
mistakes and that's ok, but lift it.

No.

Quoted 8 lines

Also remember kernel bugzilla is not only for man-pages, and at least the kernel itself does not have any policy about the AI use.

I know my post does
not directly help any projects hosted here right now, but I'm not spamming either.

That's why I've hidden your manual page, and not your messages.

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.