From: Dave.Martin@arm.com (Dave P Martin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] serial/amba-pl011: Unconditionally poll for FIFO space before each TX char
Date: Tue, 12 May 2015 16:00:38 +0100 [thread overview]
Message-ID: <20150512150037.GA29594@e103592.cambridge.arm.com> (raw)
In-Reply-To: <20150512160027.21244f64@north>
On Tue, May 12, 2015 at 03:00:27PM +0100, Jakub Kici?ski wrote:
> On Tue, 12 May 2015 14:44:26 +0100, Dave Martin wrote:
> > This will cause a conflict with tty-next because it pulls forward
> > some changes made by commit 1e84d22 (serial/amba-pl011: Refactor and
> > simplify TX FIFO handling); however, the resolution is simple except
> > for the following lines which may need to be deleted manually from
> > amba-pl011.c:pl011_startup():
>
> By resolution is simple you mean: keep the code as it is in tty-next,
> right?
Yes, that's right.
Cheers
---Dave
prev parent reply other threads:[~2015-05-12 15:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-12 13:44 [PATCH] serial/amba-pl011: Unconditionally poll for FIFO space before each TX char Dave Martin
2015-05-12 14:00 ` Jakub Kiciński
2015-05-12 15:00 ` Dave P Martin [this message]
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=20150512150037.GA29594@e103592.cambridge.arm.com \
--to=dave.martin@arm.com \
--cc=linux-arm-kernel@lists.infradead.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