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

[bugzilla-daemon@kernel.org]

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

--- Comment #1 from Alejandro Colomar (alx@kernel.org) ---
Hi,

On Fri, Oct 31, 2025 at 04:41:33AM +0000, bugzilla-daemon@kernel.org 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: 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.

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 <alx@kernel.org>
                   Cc: <linux-man@vger.kernel.org>

        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

-- 
You may reply to this email to add a comment.

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