From: Stefan Agner <stefan@agner.ch>
To: gregkh@linuxfoundation.org
Cc: jslaby@suse.cz, jingchang.lu@freescale.com, shawn.guo@linaro.org,
linux-serial@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] serial: fsl_lpuart: fix various DMA related issues
Date: Fri, 12 Dec 2014 14:44:06 +0100 [thread overview]
Message-ID: <677f2c62b6b6c1fe8e16cd38d5f20d47@agner.ch> (raw)
In-Reply-To: <1417134205-4400-1-git-send-email-stefan@agner.ch>
Any thoughts on this patchset? Would have hopped that it makes it into
3.19 as those are mostly fixes.
--
Stefan
On 2014-11-28 01:23, Stefan Agner wrote:
> Patch 1 and 3 are actual fixes, whereas 2 and 4 don't lead to issues
> in standard cases but are still worthwhile fixes.
>
> Stefan Agner (4):
> serial: fsl_lpuart: delete timer on shutdown
> serial: fsl_lpuart: move DMA channel request to probe
> serial: fsl_lpuart: avoid new transfer while DMA is running
> serial: fsl_lpuart: update RX timer on successful DMA transfer
>
> drivers/tty/serial/fsl_lpuart.c | 110 +++++++++++++++++++---------------------
> 1 file changed, 52 insertions(+), 58 deletions(-)
next prev parent reply other threads:[~2014-12-12 13:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-28 0:23 [PATCH 0/4] serial: fsl_lpuart: fix various DMA related issues Stefan Agner
2014-11-28 0:23 ` [PATCH 1/4] serial: fsl_lpuart: delete timer on shutdown Stefan Agner
2014-11-28 0:23 ` [PATCH 2/4] serial: fsl_lpuart: move DMA channel request to probe Stefan Agner
2014-11-28 0:23 ` [PATCH 3/4] serial: fsl_lpuart: avoid new transfer while DMA is running Stefan Agner
2014-11-28 0:23 ` [PATCH 4/4] serial: fsl_lpuart: update RX timer on successful DMA transfer Stefan Agner
2014-12-12 13:44 ` Stefan Agner [this message]
2014-12-12 14:32 ` [PATCH 0/4] serial: fsl_lpuart: fix various DMA related issues Greg KH
2014-12-12 16:19 ` Stefan Agner
2015-01-09 22:14 ` Greg KH
2015-01-09 22:19 ` Stefan Agner
2015-01-09 22:34 ` Greg KH
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=677f2c62b6b6c1fe8e16cd38d5f20d47@agner.ch \
--to=stefan@agner.ch \
--cc=gregkh@linuxfoundation.org \
--cc=jingchang.lu@freescale.com \
--cc=jslaby@suse.cz \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=shawn.guo@linaro.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).