From: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>
To: Fabio Estevam <festevam@gmail.com>
Cc: Sebastian Andrzej Siewior <sebastian@breakpoint.cc>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
jiwang <jiada_wang@mentor.com>, Jiri Slaby <jslaby@suse.cz>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
anton_bondarenko@mentor.com, Dirk Behme <dirk.behme@de.bosch.com>,
Nicolae Rosia <nicolae.rosia@gmail.com>,
Fabio Estevam <fabio.estevam@freescale.com>
Subject: Re: [PATCH] serial: imx: Revert "initialized DMA w/o HW flow enabled"
Date: Thu, 7 May 2015 23:16:57 +0200 [thread overview]
Message-ID: <20150507211657.GA30982@breakpoint.cc> (raw)
In-Reply-To: <CAOMZO5B1AKN8QXA5dhU7YoCGu2MXVXRq+mT2HXohv_wKXm-6-A@mail.gmail.com>
On 2015-05-07 17:54:31 [-0300], Fabio Estevam wrote:
> Thanks, this fixes Bluetooth operation on a imx6sl-warp running
> without SDMA firmware.
>
> Two suggestions:
>
> 1. You should Cc stable as it affects 4.0 also
I have the Fixes tag, doesn't this count?
> 2. It doesn't apply cleanly against linux-next, so I think Greg will
> have problems applying it.
It is on top of Greg's tty-next tree. Shouldn't this work?
Sebastian
next prev parent reply other threads:[~2015-05-07 21:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-07 20:24 [PATCH] serial: imx: Revert "initialized DMA w/o HW flow enabled" Sebastian Andrzej Siewior
2015-05-07 20:54 ` Fabio Estevam
2015-05-07 21:16 ` Sebastian Andrzej Siewior [this message]
2015-05-07 22:11 ` Fabio Estevam
2015-05-07 23:17 ` Fabio Estevam
2015-05-08 7:13 ` [PATCH v2] " Sebastian Andrzej Siewior
2015-05-08 11:30 ` Fabio Estevam
2015-05-08 11:50 ` Sebastian Andrzej Siewior
2015-05-08 12:24 ` Fabio Estevam
2015-05-19 12:18 ` Fabio Estevam
2015-06-12 13:30 ` Sebastian Andrzej Siewior
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=20150507211657.GA30982@breakpoint.cc \
--to=sebastian@breakpoint.cc \
--cc=anton_bondarenko@mentor.com \
--cc=bigeasy@linutronix.de \
--cc=dirk.behme@de.bosch.com \
--cc=fabio.estevam@freescale.com \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jiada_wang@mentor.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=nicolae.rosia@gmail.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).