From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
linux-serial@vger.kernel.org,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-kernel@vger.kernel.org,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Subject: [PATCH v2 0/5] serial: Remove custom frame size calculation
Date: Tue, 30 Aug 2022 11:49:20 +0300 [thread overview]
Message-ID: <20220830084925.5608-1-ilpo.jarvinen@linux.intel.com> (raw)
A few drivers still calculate number of frame bits on their own. As core
can do that for them these days, take advantage of core's capabilities.
v2:
- Address coding style comments (from Andy)
Ilpo Järvinen (5):
serial: ucc_uart: Remove custom frame size calculation
serial: cpm_uart: Remove custom frame size calculation
serial: fsl_lpuart: Remove custom frame size calculation
serial: sunsab: Remove frame size calculation dead-code
serial: tegra: Remove custom frame size calculation
drivers/tty/serial/cpm_uart/cpm_uart_core.c | 31 +++++++--------------
drivers/tty/serial/fsl_lpuart.c | 9 ++----
drivers/tty/serial/serial-tegra.c | 12 ++------
drivers/tty/serial/sunsab.c | 20 ++++++-------
drivers/tty/serial/ucc_uart.c | 15 +---------
5 files changed, 24 insertions(+), 63 deletions(-)
--
2.30.2
next reply other threads:[~2022-08-30 8:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-30 8:49 Ilpo Järvinen [this message]
2022-08-30 8:49 ` [PATCH v2 1/5] serial: ucc_uart: Remove custom frame size calculation Ilpo Järvinen
2022-08-30 17:01 ` Timur Tabi
2022-08-30 17:01 ` Timur Tabi
2022-08-30 8:49 ` [PATCH v2 2/5] serial: cpm_uart: " Ilpo Järvinen
2022-08-30 8:49 ` [PATCH v2 3/5] serial: fsl_lpuart: " Ilpo Järvinen
2022-08-30 8:49 ` [PATCH v2 4/5] serial: sunsab: Remove frame size calculation dead-code Ilpo Järvinen
2022-08-30 8:49 ` [PATCH v2 5/5] serial: tegra: Remove custom frame size calculation Ilpo Järvinen
2022-09-15 12:33 ` Thierry Reding
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=20220830084925.5608-1-ilpo.jarvinen@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.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.