From: Kumar Gala <galak@kernel.crashing.org>
To: Laurent Pinchart <laurentp@cse-semaphore.com>
Cc: linuxppc-dev@ozlabs.org, linux-serial@vger.kernel.org
Subject: Re: [PATCHv2] cpm_uart: Support uart_wait_until_sent()
Date: Wed, 2 Jul 2008 11:13:52 -0500 [thread overview]
Message-ID: <FF9F9674-03B4-4FD1-9B01-8DC0972F6899@kernel.crashing.org> (raw)
In-Reply-To: <200807021058.45619.laurentp@cse-semaphore.com>
On Jul 2, 2008, at 3:58 AM, Laurent Pinchart wrote:
> Set port->fifosize to the software FIFO size, and update the port
> timeout
> when the baud rate is modified. SCC ports have an optional 32 byte
> hardware
> FIFO which is currently not taken into account, as there is no
> documented way
> to check when the FIFO becomes empty.
>
> Signed-off-by: Laurent Pinchart <laurentp@cse-semaphore.com>
> ---
> drivers/serial/cpm_uart/cpm_uart_core.c | 6 ++++++
> 1 files changed, 6 insertions(+), 0 deletions(-)
applied.
- k
prev parent reply other threads:[~2008-07-02 16:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-26 11:55 [PATCH] cpm_uart: Support uart_wait_until_sent() Laurent Pinchart
2008-07-02 7:46 ` Kumar Gala
2008-07-02 8:58 ` [PATCHv2] " Laurent Pinchart
2008-07-02 16:13 ` Kumar Gala [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=FF9F9674-03B4-4FD1-9B01-8DC0972F6899@kernel.crashing.org \
--to=galak@kernel.crashing.org \
--cc=laurentp@cse-semaphore.com \
--cc=linux-serial@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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