From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-mips@vger.kernel.org
Cc: Jonas Gorski <jonas.gorski@gmail.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org
Subject: [PATCH v2 1/6] serial: 8250: remove AR7 support
Date: Fri, 22 Sep 2023 08:15:22 +0200 [thread overview]
Message-ID: <20230922061530.3121-2-wsa+renesas@sang-engineering.com> (raw)
In-Reply-To: <20230922061530.3121-1-wsa+renesas@sang-engineering.com>
AR7 is going to be removed from the Kernel, so remove its type
definition from 8250 code. As with previous removals, I checked with
Debian Code Search that 'PORT_AR7' is not used in userspace.
Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
Acked-by: Florian Fainelli <f.fainelli@gmail.com>
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
Changes since v1:
* added acks
* kept uapi define for for serial port type
drivers/tty/serial/8250/8250_port.c | 7 -------
1 file changed, 7 deletions(-)
diff --git a/drivers/tty/serial/8250/8250_port.c b/drivers/tty/serial/8250/8250_port.c
index fb891b67968f..a4f5d792679a 100644
--- a/drivers/tty/serial/8250/8250_port.c
+++ b/drivers/tty/serial/8250/8250_port.c
@@ -170,13 +170,6 @@ static const struct serial8250_config uart_config[] = {
.fcr = UART_FCR_ENABLE_FIFO | UART_FCR_R_TRIG_10,
.flags = UART_CAP_FIFO,
},
- [PORT_AR7] = {
- .name = "AR7",
- .fifo_size = 16,
- .tx_loadsz = 16,
- .fcr = UART_FCR_ENABLE_FIFO | UART_FCR_R_TRIG_00,
- .flags = UART_CAP_FIFO /* | UART_CAP_AFE */,
- },
[PORT_U6_16550A] = {
.name = "U6_16550A",
.fifo_size = 64,
--
2.35.1
next prev parent reply other threads:[~2023-09-22 6:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-22 6:15 [PATCH v2 0/6] remove AR7 platform and associated drivers Wolfram Sang
2023-09-22 6:15 ` Wolfram Sang [this message]
2023-09-22 6:15 ` [PATCH v2 2/6] mtd: parsers: ar7: remove support Wolfram Sang
2023-09-22 14:39 ` Miquel Raynal
2023-09-22 17:55 ` Wolfram Sang
2023-09-22 18:35 ` Philippe Mathieu-Daudé
2023-09-25 7:11 ` Miquel Raynal
2023-09-28 7:10 ` Wolfram Sang
2023-10-02 9:39 ` Miquel Raynal
2023-09-22 6:15 ` [PATCH v2 3/6] vlynq: remove bus driver Wolfram Sang
2023-09-22 6:15 ` [PATCH v2 4/6] watchdog: ar7_wdt: remove driver to prepare for platform removal Wolfram Sang
2023-09-22 6:15 ` [PATCH net-next v2 5/6] net: cpmac: " Wolfram Sang
2023-10-05 14:08 ` Thomas Bogendoerfer
2023-10-05 14:16 ` Jakub Kicinski
2023-10-05 19:07 ` Thomas Bogendoerfer
2023-10-06 14:26 ` Jakub Kicinski
2023-09-22 6:15 ` [PATCH v2 6/6] MIPS: AR7: remove platform Wolfram Sang
2023-09-28 7:06 ` Wolfram Sang
2023-09-28 7:29 ` Thomas Bogendoerfer
2023-09-28 7:49 ` Wolfram Sang
2023-10-06 8:20 ` Thomas Bogendoerfer
2023-10-19 8:49 ` Thomas Bogendoerfer
2023-10-19 12:32 ` Wolfram Sang
2023-10-19 8:50 ` [PATCH v2 0/6] remove AR7 platform and associated drivers Thomas Bogendoerfer
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=20230922061530.3121-2-wsa+renesas@sang-engineering.com \
--to=wsa+renesas@sang-engineering.com \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=jonas.gorski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@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 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 NNTP newsgroup(s).