summaryrefslogtreecommitdiff
path: root/drivers/tty
diff options
context:
space:
mode:
authorHugo Villeneuve <hvilleneuve@dimonoff.com>2026-04-10 11:20:11 -0400
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2026-05-11 17:19:52 +0200
commit2f0c8853109bca54ac28e33659ce600ceb45ff12 (patch)
treef9b30a8090329e80ae5507ef8b4daeccf61ab068 /drivers/tty
parent888b245964ad3617866d6d4b5bb8a154a410ef32 (diff)
downloadlinux-next-2f0c8853109bca54ac28e33659ce600ceb45ff12.tar.gz
linux-next-2f0c8853109bca54ac28e33659ce600ceb45ff12.zip
serial: core: update uart_get_baud_rate() obsolete comments
Update obsolete comments to match the actual code. Signed-off-by: Hugo Villeneuve <hvilleneuve@dimonoff.com> Link: https://patch.msgid.link/20260410152022.2146488-4-hugo@hugovil.com Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/tty')
-rw-r--r--drivers/tty/serial/serial_core.c5
1 files changed, 3 insertions, 2 deletions
diff --git a/drivers/tty/serial/serial_core.c b/drivers/tty/serial/serial_core.c
index 89cebdd27841..e6a8ab40442d 100644
--- a/drivers/tty/serial/serial_core.c
+++ b/drivers/tty/serial/serial_core.c
@@ -465,7 +465,8 @@ EXPORT_SYMBOL(uart_update_timeout);
* baud.
*
* If the new baud rate is invalid, try the @old termios setting. If it's still
- * invalid, we try 9600 baud. If that is also invalid 0 is returned.
+ * invalid, clip to the nearest chip supported rate.
+ * If that is also invalid 0 is returned.
*
* The @termios structure is updated to reflect the baud rate we're actually
* going to be using. Don't do this for the case where B0 is requested ("hang
@@ -523,7 +524,7 @@ uart_get_baud_rate(struct uart_port *port, struct ktermios *termios,
return baud;
/*
- * Oops, the quotient was zero. Try again with
+ * If the range cannot be met then try again with
* the old baud rate if possible.
*/
termios->c_cflag &= ~CBAUD;