unofficial mirror of libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "Alejandro Colomar \(man-pages\) via Libc-alpha" <libc-alpha@sourceware.org>
To: "Pali Rohár" <pali@kernel.org>
Cc: "Marek Behún" <kabel@kernel.org>,
	linux-man@vger.kernel.org, libc-alpha@sourceware.org,
	"Michael Kerrisk" <mtk.manpages@gmail.com>
Subject: Re: [PATCH v2] ioctl_tty.2: Document ioctls: TCGETS2, TCSETS2, TCSETSW2, TCSETSF2
Date: Fri, 30 Jul 2021 20:20:02 +0200	[thread overview]
Message-ID: <2e3eb624-310b-bae3-c244-fbfac0bc22d6@gmail.com> (raw)
In-Reply-To: <20210730104803.10328-1-pali@kernel.org>

Hi Pali,

On 7/30/21 12:48 PM, Pali Rohár wrote:
> Signed-off-by: Pali Rohár <pali@kernel.org>
> 

Patch applied.  Thanks,

Alex

> ---
> Changes in v2:
> * Remove information about asm/termbits.h (will be in followup patch)
> * Style fixes
> ---
>   man2/ioctl_tty.2 | 29 +++++++++++++++++++++++++++++
>   1 file changed, 29 insertions(+)
> 
> diff --git a/man2/ioctl_tty.2 b/man2/ioctl_tty.2
> index 2a0effdae8ab..c1875530f0b1 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\ *" .
> +If struct member
> +.B c_cflag
> +contains
> +.B BOTHER
> +then baudrate is stored in struct members
> +.B c_ispeed
> +and
> +.B c_ospeed
> +as integer values.
> +These ioctls are not supported on all architectures.
> +.RS
> +.TS
> +lb l.
> +TCGETS2	\fBstruct termios2 *\fPargp
> +TCSETS2	\fBconst struct termios2 *\fPargp
> +TCSETSW2	\fBconst struct termios2 *\fPargp
> +TCSETSF2	\fBconst struct termios2 *\fPargp
> +.TE
> +.RE
> +.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/

      reply	other threads:[~2021-07-30 18:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20210725225506.7404-1-pali@kernel.org>
     [not found] ` <271f5402-95f5-4e65-84ee-a227879e1c33@gmail.com>
     [not found]   ` <20210729173118.pud4xucnt4kncvol@pali>
     [not found]     ` <7d48a1dd-9641-53e9-bb65-868c86f22821@gmail.com>
     [not found]       ` <20210730000915.d6ieqiuqah4tjjxf@pali>
2021-07-30  7:04         ` [PATCH] ioctl_tty.2: Document ioctls: TCGETS2, TCSETS2, TCSETSW2, TCSETSF2 Alejandro Colomar (man-pages) via Libc-alpha
2021-07-30 10:56           ` Pali Rohár via Libc-alpha
     [not found]       ` <20210730002104.ug6gfh3xh4anh3e5@pali>
2021-07-30  7:59         ` Alejandro Colomar (man-pages) via Libc-alpha
2021-07-30 10:48 ` [PATCH v2] " Pali Rohár via Libc-alpha
2021-07-30 18:20   ` Alejandro Colomar (man-pages) via Libc-alpha [this message]

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

  List information: https://www.gnu.org/software/libc/involved.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2e3eb624-310b-bae3-c244-fbfac0bc22d6@gmail.com \
    --to=libc-alpha@sourceware.org \
    --cc=alx.manpages@gmail.com \
    --cc=kabel@kernel.org \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    --cc=pali@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).