From: Don Slutz <dslutz@verizon.com>
To: Don Slutz <dslutz@verizon.com>
Cc: Peter Crosthwaite <peter.crosthwaite@xilinx.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 1/1] char/serial: Fix emptyness handling
Date: Fri, 28 Mar 2014 07:43:00 -0400 [thread overview]
Message-ID: <53356044.7020309@terremark.com> (raw)
In-Reply-To: <1395160174-16006-1-git-send-email-dslutz@verizon.com>
Ping. (Since this is a bug fix, I think it can go into 2.0)
-Don Slutz
On 03/18/14 12:29, Don Slutz wrote:
> The commit 88c1ee73d3231c74ff90bcfc084a7589670ec244
> char/serial: Fix emptyness check
>
> Still causes extra NULL byte(s) to be sent.
>
> So if the fifo is empty, do not send an extra NULL byte.
>
> Reviewed-by: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
> Signed-off-by: Don Slutz <dslutz@verizon.com>
> ---
> Changes V2 to v3
> Revert v2 changes
> Fix coding style issues.
> Changes v1 to v2
> Do full state change on fifo8_is_empty.
>
>
> hw/char/serial.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/hw/char/serial.c b/hw/char/serial.c
> index 6d3b5af..f4d167f 100644
> --- a/hw/char/serial.c
> +++ b/hw/char/serial.c
> @@ -225,8 +225,10 @@ static gboolean serial_xmit(GIOChannel *chan, GIOCondition cond, void *opaque)
>
> if (s->tsr_retry <= 0) {
> if (s->fcr & UART_FCR_FE) {
> - s->tsr = fifo8_is_empty(&s->xmit_fifo) ?
> - 0 : fifo8_pop(&s->xmit_fifo);
> + if (fifo8_is_empty(&s->xmit_fifo)) {
> + return FALSE;
> + }
> + s->tsr = fifo8_pop(&s->xmit_fifo);
> if (!s->xmit_fifo.num) {
> s->lsr |= UART_LSR_THRE;
> }
next prev parent reply other threads:[~2014-03-28 11:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-18 16:29 [Qemu-devel] [PATCH v3 1/1] char/serial: Fix emptyness handling Don Slutz
2014-03-28 11:43 ` Don Slutz [this message]
2014-03-28 12:10 ` Paolo Bonzini
2014-04-04 12:13 ` Peter Crosthwaite
2014-04-04 23:14 ` [Qemu-devel] [PATCH for-2.0 " Brian Jackson
2014-04-07 14:16 ` [Qemu-devel] [PATCH " Peter Maydell
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=53356044.7020309@terremark.com \
--to=dslutz@verizon.com \
--cc=peter.crosthwaite@xilinx.com \
--cc=qemu-devel@nongnu.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).