From: Rob Herring <robh@kernel.org>
Cc: Dai Okamura <okamura.dai@socionext.com>,
devicetree@vger.kernel.org, Greg KH <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
Masahiro Yamada <yamada.masahiro@socionext.com>,
linux-serial@vger.kernel.org, Jiri Slaby <jslaby@suse.com>,
Mark Rutland <mark.rutland@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/3] serial: 8250_uniphier: remove unused "fifo-size" property
Date: Tue, 25 Sep 2018 04:24:34 -0700 [thread overview]
Message-ID: <5baa1af3.1c69fb81.4e5cb.3bca@mx.google.com> (raw)
In-Reply-To: <1537334893-26079-2-git-send-email-yamada.masahiro@socionext.com>
On Wed, 19 Sep 2018 14:28:11 +0900, Masahiro Yamada wrote:
> The FIFO size of the UART devices is 64 on almost all UniPhier SoCs
> with the exception Pro4TV SoC (MN2WS0230), which used 128 FIFO size.
> However, Pro4TV SoC was never upstreamed, and out of production.
>
> So, this property has never been used in a useful way.
> Let's remove old unused code.
>
> Signed-off-by: Masahiro Yamada <yamada.masahiro@socionext.com>
> ---
>
> Documentation/devicetree/bindings/serial/uniphier-uart.txt | 4 ----
> drivers/tty/serial/8250/8250_uniphier.c | 10 +---------
> 2 files changed, 1 insertion(+), 13 deletions(-)
>
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2018-09-25 11:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-19 5:28 [PATCH 0/3] serial: 8250_uniphier: remove unused code and add auto-flow-control Masahiro Yamada
2018-09-19 5:28 ` [PATCH 1/3] serial: 8250_uniphier: remove unused "fifo-size" property Masahiro Yamada
2018-09-25 11:24 ` Rob Herring [this message]
2018-09-19 5:28 ` [PATCH 2/3] serial: 8250_uniphier: flatten probe function Masahiro Yamada
2018-09-19 5:28 ` [PATCH 3/3] serial: 8250_uniphier: add auto-flow-control support Masahiro Yamada
2018-09-25 11:24 ` Rob Herring
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=5baa1af3.1c69fb81.4e5cb.3bca@mx.google.com \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=okamura.dai@socionext.com \
--cc=yamada.masahiro@socionext.com \
/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).