From: Jiri Slaby <jirislaby@kernel.org>
To: Simon Arlott <simon@octiron.net>,
Oliver Neukum <oneukum@suse.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
linux-serial@vger.kernel.org
Subject: Re: [PATCH] docs: ABI: sysfs-tty: close times are in hundredths of a second
Date: Fri, 25 Aug 2023 07:33:40 +0200 [thread overview]
Message-ID: <2a3647bf-91a8-7a5f-9edb-c792a6031f57@kernel.org> (raw)
In-Reply-To: <27304225-c8b0-9cac-94a3-e985e45aa41a@0882a8b5-c6c3-11e9-b005-00805fc181fe.uuid.home.arpa>
On 24. 08. 23, 9:18, Simon Arlott wrote:
> The times for close_delay and closing_wait are in hundredths of a
> second, not milliseconds. Fix the documentation instead of trying
> to use millisecond values (which would have to be rounded).
>
> Signed-off-by: Simon Arlott <simon@octiron.net>
> ---
> If you'd prefer, I can fold the second part of this into my previous
> patch which shouldn't have documented it as milliseconds in the first
> place (but I copied it from the other entry).
>
> Documentation/ABI/testing/sysfs-tty | 12 ++++++++----
> 1 file changed, 8 insertions(+), 4 deletions(-)
>
> diff --git a/Documentation/ABI/testing/sysfs-tty b/Documentation/ABI/testing/sysfs-tty
> index e04e322af568..6ee878771f51 100644
> --- a/Documentation/ABI/testing/sysfs-tty
> +++ b/Documentation/ABI/testing/sysfs-tty
> @@ -87,7 +87,8 @@ What: /sys/class/tty/ttyS<x>/close_delay
> Date: October 2012
> Contact: Alan Cox <alan@linux.intel.com>
> Description:
> - Show the closing delay time for this port in ms.
> + Show the closing delay time for this port in hundredths
> + of a second.
>
> These sysfs values expose the TIOCGSERIAL interface via
> sysfs rather than via ioctls.
> @@ -96,7 +97,8 @@ What: /sys/class/tty/ttyS<x>/closing_wait
> Date: October 2012
> Contact: Alan Cox <alan@linux.intel.com>
> Description:
> - Show the close wait time for this port in ms.
> + Show the close wait time for this port in hundredths of
> + a second.
>
> These sysfs values expose the TIOCGSERIAL interface via
> sysfs rather than via ioctls.
Could you send these two hunks as a separate patch? It's correct
regardless of your other patch.
And I would use "centiseconds" instead, which is used (IMO) in these cases.
thanks,
--
js
suse labs
next prev parent reply other threads:[~2023-08-25 5:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-23 20:37 [PATCH] USB: cdc-acm: expose serial close_delay and closing_wait in sysfs Simon Arlott
2023-08-23 21:12 ` [PATCH (v2)] " Simon Arlott
2023-08-24 7:18 ` [PATCH] docs: ABI: sysfs-tty: close times are in hundredths of a second Simon Arlott
2023-08-25 5:33 ` Jiri Slaby [this message]
2023-08-27 18:23 ` [PATCH (v2)] docs: ABI: sysfs-tty: close times are in centiseconds Simon Arlott
2023-08-24 8:21 ` [PATCH] USB: cdc-acm: expose serial close_delay and closing_wait in sysfs Oliver Neukum
2023-08-24 14:48 ` Greg Kroah-Hartman
2023-08-24 18:02 ` Simon Arlott
2023-08-24 19:22 ` Greg Kroah-Hartman
2023-08-27 15:36 ` Simon Arlott
2023-08-24 23:46 ` Oliver Neukum
2023-08-25 1:53 ` Alan Stern
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=2a3647bf-91a8-7a5f-9edb-c792a6031f57@kernel.org \
--to=jirislaby@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=simon@octiron.net \
/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