From: "Pali Rohár" <pali@kernel.org>
To: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
Cc: Michael Kerrisk <mtk.manpages@gmail.com>, linux-man@vger.kernel.org
Subject: Re: [PATCH] ioctl_tty.2: Document ioctls: TCGETS2, TCSETS2, TCSETSW2, TCSETSF2
Date: Thu, 29 Jul 2021 19:31:18 +0200 [thread overview]
Message-ID: <20210729173118.pud4xucnt4kncvol@pali> (raw)
In-Reply-To: <271f5402-95f5-4e65-84ee-a227879e1c33@gmail.com>
Hello!
On Thursday 29 July 2021 13:30:11 Alejandro Colomar (man-pages) wrote:
> Hi Pali,
>
>
> On 7/26/21 12:55 AM, Pali Rohár wrote:
> > Signed-off-by: Pali Rohár <pali@kernel.org>
> > ---
>
> Please see some comments below.
>
> Thanks,
>
> Alex
>
> > man2/ioctl_tty.2 | 29 +++++++++++++++++++++++++++++
> > 1 file changed, 29 insertions(+)
> >
> > diff --git a/man2/ioctl_tty.2 b/man2/ioctl_tty.2
> > index c8269070180f..0c3a8ec24c76 100644
> > --- a/man2/ioctl_tty.2
> > +++ b/man2/ioctl_tty.2
> > @@ -77,6 +77,35 @@ The following four ioctls are just like
> > .BR TCSETSW ,
> > .BR TCSETSF ,
> > except that they take a
> > +.I "struct termios2\ *"
> > +instead of a
> > +.IR "struct termios\ *" .
> > +.I "struct termios2\ *"
> > +is defined in header file
>
> Maybe s/in/in the/ ?
Ok, I will change it.
> > +.IR "<asm/termbits.h>" .
>
> Quotes are unnecessary here.
Ok.
> > +If struct member
> > +.B c_cflag
> > +contains
> > +.B BOTHER
> > +then baudrate is stored in struct members
> > +.BR c_ispeed " and " c_ospeed
>
> We always break this into:
>
> .B c_ispeed
> and
> .B c_ospeed
Ok.
> > +as integer values.
> > +These ioctls are not supported on all architectures.
> > +.IP
> > +.BI "TCGETS2 struct termios2 *" argp
>
> Please follow the same style as in the rest of the page:
>
> .TP
> .B TCGETS2
> Argument:
> .BI "struct termios2 *" argp
>
> Unless there's a good reason not to.
Few lines below in this file is:
.IR "struct termios\ *" .
.IP
.BI "TCGETA struct termio *" argp
.IP
.BI "TCSETA const struct termio *" argp
.IP
.BI "TCSETAW const struct termio *" argp
.IP
.BI "TCSETAF const struct termio *" argp
Therefore I used same style for TCGETS2...
So, how should I format this part to be consistent?
> > +.IP
> > +.BI "TCSETS2 const struct termios2 *" argp
> > +.IP
> > +.BI "TCSETSW2 const struct termios2 *" argp
> > +.IP
> > +.BI "TCSETSF2 const struct termios2 *" argp
> > +.PP
> > +The following four ioctls are just like
> > +.BR TCGETS ,
> > +.BR TCSETS ,
> > +.BR TCSETSW ,
> > +.BR TCSETSF ,
> > +except that they take a
> > .I "struct termio\ *"
> > instead of a
> > .IR "struct termios\ *" .
> >
>
>
> --
> Alejandro Colomar
> Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
> http://www.alejandro-colomar.es/
next prev parent reply other threads:[~2021-07-29 17:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-25 22:55 [PATCH] ioctl_tty.2: Document ioctls: TCGETS2, TCSETS2, TCSETSW2, TCSETSF2 Pali Rohár
2021-07-29 11:30 ` Alejandro Colomar (man-pages)
2021-07-29 17:31 ` Pali Rohár [this message]
2021-07-29 23:39 ` Alejandro Colomar (man-pages)
2021-07-30 0:09 ` Pali Rohár
2021-07-30 7:04 ` Alejandro Colomar (man-pages)
2021-07-30 10:56 ` Pali Rohár
2021-07-30 0:21 ` Pali Rohár
2021-07-30 7:59 ` Alejandro Colomar (man-pages)
2021-07-30 10:48 ` [PATCH v2] " Pali Rohár
2021-07-30 18:20 ` Alejandro Colomar (man-pages)
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=20210729173118.pud4xucnt4kncvol@pali \
--to=pali@kernel.org \
--cc=alx.manpages@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.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