From: Felipe Balbi <balbi@ti.com>
To: Frans Klaver <frans.klaver@xsens.com>
Cc: <linux-serial@vger.kernel.org>, Rob Herring <robh+dt@kernel.org>,
"Pawel Moll" <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
Jiri Slaby <jslaby@suse.cz>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH 0/3] omap-serial high-speed fixes/improvements
Date: Mon, 18 Aug 2014 08:45:08 -0500 [thread overview]
Message-ID: <20140818134507.GC9662@saruman.home> (raw)
In-Reply-To: <1406645577-18620-1-git-send-email-frans.klaver@xsens.com>
[-- Attachment #1: Type: text/plain, Size: 588 bytes --]
Hi,
On Tue, Jul 29, 2014 at 04:52:54PM +0200, Frans Klaver wrote:
> Hi,
>
> Here's a couple of patches that should improve the behavior of the omap serial
> driver at high data rates and baud rates.
>
> I was actually surprised to see that proper dma support isn't there yet, but
> there you go. Anyone got news on that, by the way?
please resend these patches and make sure you get the right Cc list.
You're missing linux-omap, Tony Lingren, linux-arm-kernel...
scripts/get_maintainer.pl would give you a more exaustive list of
people to Cc.
cheers
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-08-18 13:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-29 14:52 [RFC PATCH 0/3] omap-serial high-speed fixes/improvements Frans Klaver
[not found] ` <1406645577-18620-2-git-send-email-frans.klaver@xsens.com>
2014-07-29 15:00 ` [PATCH 1/3] tty: omap-serial: prevent division by zero Frans Klaver
2014-07-29 15:02 ` [RFC PATCH 0/3] omap-serial high-speed fixes/improvements Frans Klaver
2014-07-29 15:02 ` [PATCH 1/3] tty: omap-serial: prevent division by zero Frans Klaver
2014-07-29 15:02 ` [PATCH 2/3] tty: omap-serial: use threaded interrupt handler Frans Klaver
2014-07-29 15:02 ` [PATCH 3/3] tty: omap-serial: support setting of hardware flow control in dts Frans Klaver
2014-08-11 10:09 ` [RFC PATCH 0/3] omap-serial high-speed fixes/improvements Frans Klaver
2014-08-18 13:45 ` Felipe Balbi [this message]
2014-08-18 14:45 ` Frans Klaver
2014-08-19 12:14 ` [RFC PATCHv2 0/4] " Frans Klaver
2014-08-19 12:14 ` [PATCH 1/4] tty: omap-serial: pull out calculation from baud_is_mode16 Frans Klaver
2014-08-19 12:14 ` [PATCH 2/4] tty: omap-serial: prevent division by zero Frans Klaver
2014-08-19 12:14 ` [RFC PATCH 3/4] tty: omap-serial: use threaded interrupt handler Frans Klaver
2014-08-19 18:57 ` Felipe Balbi
2014-08-20 6:40 ` Frans Klaver
2014-08-20 16:06 ` Felipe Balbi
2014-08-21 21:41 ` Frans Klaver
2014-08-21 21:48 ` Felipe Balbi
2014-08-21 22:07 ` Frans Klaver
2014-08-22 14:02 ` Frans Klaver
2014-08-19 12:14 ` [PATCH 4/4] tty: omap-serial: support setting of hardware flow control in dts Frans Klaver
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=20140818134507.GC9662@saruman.home \
--to=balbi@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=frans.klaver@xsens.com \
--cc=galak@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.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).