All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: "Pali Rohár" <pali@kernel.org>,
	"Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org
Subject: Re: [PATCH] termios.3: Clarify zero argument for cfsetispeed()
Date: Tue, 31 Aug 2021 02:25:48 +0200	[thread overview]
Message-ID: <234956c2-74e5-2ca4-d2f6-cfdbc0f244e7@gmail.com> (raw)
In-Reply-To: <20210830112552.18476-1-pali@kernel.org>

Hello Pali,

On 8/30/21 1:25 PM, Pali Rohár wrote:
> Zero in this case refers to literal constant 0 and not symbolic constant B0.
> 
> Signed-off-by: Pali Rohár <pali@kernel.org>

Thanks. Patch applied.

Cheers,

Michael


> ---
>  man3/termios.3 | 6 +++++-
>  1 file changed, 5 insertions(+), 1 deletion(-)
> 
> diff --git a/man3/termios.3 b/man3/termios.3
> index c96a5c15ec87..f888c15d754c 100644
> --- a/man3/termios.3
> +++ b/man3/termios.3
> @@ -1017,7 +1017,11 @@ which must be specified as one of the
>  .BI B nnn
>  constants listed above for
>  .BR cfsetospeed ().
> -If the input baud rate is set to zero, the input baud rate will be
> +If the input baud rate is set to literal constant
> +.B 0
> +(not the symbolic constant
> +.BR B0 ),
> +the input baud rate will be
>  equal to the output baud rate.
>  .PP
>  .BR cfsetspeed ()
> 


-- 
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/

      reply	other threads:[~2021-08-31  0:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-30 10:38 cfsetispeed and zero baudrate Pali Rohár
2021-08-30 11:04 ` Alejandro Colomar (man-pages)
2021-08-30 11:25   ` [PATCH] termios.3: Clarify zero argument for cfsetispeed() Pali Rohár
2021-08-31  0:25     ` Michael Kerrisk (man-pages) [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

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

  git send-email \
    --in-reply-to=234956c2-74e5-2ca4-d2f6-cfdbc0f244e7@gmail.com \
    --to=mtk.manpages@gmail.com \
    --cc=alx.manpages@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --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 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.