All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Wilk <jwilk@jwilk.net>
To: наб <nabijaczleweli@nabijaczleweli.xyz>
Cc: Alejandro Colomar <alx.manpages@gmail.com>, <linux-man@vger.kernel.org>
Subject: Re: [PATCH 2/4] ioctl_console.2: use symbolic subcodes
Date: Thu, 1 Sep 2022 16:51:38 +0200	[thread overview]
Message-ID: <20220901144621.divjlo6cas65x75e@jwilk.net> (raw)
In-Reply-To: <5850af710e563757039a2a72a4b9219015bd27c6.1662039344.git.nabijaczleweli@nabijaczleweli.xyz>

I was playing with TIOCLINUX just a few days, and found the docs 
unsatisfactory. So this patchset very welcome. :)

* наб <nabijaczleweli@nabijaczleweli.xyz>, 2022-09-01 15:36:
>+Symbolic
>+.IR subcode s
>+are available since
>+Linux 2.5.71.

Indeed:
https://git.kernel.org/pub/scm/linux/kernel/git/history/history.git/commit/?id=6cd8b04781e03b2669c764331181a2d3a8511fe5

It would be helpful to mention the constants are defined in <linux/tiocl.h>.

-- 
Jakub Wilk

  reply	other threads:[~2022-09-01 14:58 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-01 13:35 [PATCH 1/4] ioctl_console.2: ffix наб
2022-09-01 13:36 ` [PATCH 2/4] ioctl_console.2: use symbolic subcodes наб
2022-09-01 14:51   ` Jakub Wilk [this message]
2022-09-01 13:36 ` [PATCH 3/4] ioctl_console.2: devices/char/console.c and sel_buffer don't exist anymore наб
2022-09-01 13:37 ` [PATCH 4/4] ioctl_console.2: document all extant TIOCLINUX subcodes as of 6.0 (2.6.17) наб
2022-09-01 15:13   ` Jakub Wilk
2022-09-01 21:28 ` [PATCH 1/4] ioctl_console.2: ffix Alejandro Colomar
2022-09-02 13:06 ` [PATCH v2 2/4] ioctl_console.2: use symbolic subcodes наб
2022-09-02 13:06 ` [PATCH v2 3/4] ioctl_console.2: devices/char/console.c and sel_buffer don't exist anymore наб
2022-09-02 13:07 ` [PATCH v2 4/4] ioctl_console.2: document all extant TIOCLINUX subcodes as of 6.0 (2.6.17) наб
2022-09-02 19:07   ` Alejandro Colomar

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=20220901144621.divjlo6cas65x75e@jwilk.net \
    --to=jwilk@jwilk.net \
    --cc=alx.manpages@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=nabijaczleweli@nabijaczleweli.xyz \
    /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.