From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Loic Poulain <loic.poulain@intel.com>
Cc: gregkh@linuxfoundation.org, linux-serial@vger.kernel.org
Subject: Re: [RESEND PATCH] 8250_core: Fix unwanted TX chars write
Date: Thu, 24 Apr 2014 13:24:18 +0300 [thread overview]
Message-ID: <20140424102418.GB23665@xps8300> (raw)
In-Reply-To: <1398332336-5053-1-git-send-email-loic.poulain@intel.com>
On Thu, Apr 24, 2014 at 11:38:56AM +0200, Loic Poulain wrote:
> On transmit-hold-register empty, serial8250_tx_chars
> should be called only if we don't use DMA.
> DMA has its own tx cycle.
>
> Signed-off-by: Loic Poulain <loic.poulain@intel.com>
This should also go to stable tree.
Reviewed-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Thanks,
--
heikki
prev parent reply other threads:[~2014-04-24 10:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-24 9:38 [RESEND PATCH] 8250_core: Fix unwanted TX chars write Loic Poulain
2014-04-24 10:24 ` Heikki Krogerus [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=20140424102418.GB23665@xps8300 \
--to=heikki.krogerus@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-serial@vger.kernel.org \
--cc=loic.poulain@intel.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).