From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: Peter Senna Tschudin <peter.senna@collabora.com>,
Alan Cox <gnomes@lxorguk.ukuu.org.uk>,
Rob Herring <robherring2@gmail.com>,
Andrey Smirnov <andrew.smirnov@gmail.com>,
"linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
Chris Healy <cphealy@gmail.com>, Jiri Slaby <jslaby@suse.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC, PATCH] imx: serial: Take tty->files_lock opportunistically
Date: Mon, 12 Jun 2017 08:46:56 +0200 [thread overview]
Message-ID: <20170612064656.GA15926@kroah.com> (raw)
In-Reply-To: <CAOMZO5A_hLkuQkmfQFmCmLtCFimf0i70WbtYMr0o811vpreKbA@mail.gmail.com>
On Sun, Jun 11, 2017 at 09:33:13PM -0300, Fabio Estevam wrote:
> Hi Greg,
>
> On Sat, Jun 3, 2017 at 6:30 AM, Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> > On Tue, May 30, 2017 at 03:44:27PM +0200, Peter Senna Tschudin wrote:
> >> On Tue, May 30, 2017 at 02:42:13PM +0100, Alan Cox wrote:
> >>
> >> I sent a second patch recently:
> >>
> >> https://patchwork.kernel.org/patch/9725625/
> >
> > And it's already in linux-next so all should be good here.
>
> linux-next is good, but mainline is not.
>
> Actually we need 4dec2f119e86f9c9 ("imx-serial: RX DMA startup
> latency") to be applied to 4.12-rc as well.
Why? Can't it wait until 4.13-rc1?
thanks,
greg k-h
next prev parent reply other threads:[~2017-06-12 7:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-30 12:37 [RFC, PATCH] imx: serial: Take tty->files_lock opportunistically Andrey Smirnov
2017-05-30 12:59 ` Rob Herring
2017-05-30 13:42 ` Alan Cox
2017-05-30 13:44 ` Peter Senna Tschudin
2017-06-03 9:30 ` Greg Kroah-Hartman
2017-06-12 0:33 ` Fabio Estevam
2017-06-12 6:46 ` Greg Kroah-Hartman [this message]
2017-06-12 11:55 ` Fabio Estevam
2017-06-12 12:04 ` Greg Kroah-Hartman
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=20170612064656.GA15926@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andrew.smirnov@gmail.com \
--cc=cphealy@gmail.com \
--cc=festevam@gmail.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=jslaby@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=peter.senna@collabora.com \
--cc=robherring2@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).