From: Felipe Balbi <balbi@ti.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Felipe Balbi <balbi@ti.com>, Greg KH <gregkh@linuxfoundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux ARM Kernel Mailing List
<linux-arm-kernel@lists.infradead.org>,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
<linux@arm.linux.org.uk>,
Santosh Shilimkar <santosh.shilimkar@ti.com>
Subject: Re: [PATCH] Revert "serial: omap: fix software flow control"
Date: Wed, 24 Oct 2012 13:02:55 +0300 [thread overview]
Message-ID: <20121024100254.GG5665@arwen.pp.htv.fi> (raw)
In-Reply-To: <20121016151357.GN15569@atomide.com>
[-- Attachment #1: Type: text/plain, Size: 776 bytes --]
Hi Greg,
On Tue, Oct 16, 2012 at 08:13:59AM -0700, Tony Lindgren wrote:
> * Felipe Balbi <balbi@ti.com> [121016 07:16]:
> > This reverts commit 957ee7270d632245b43f6feb0e70d9a5e9ea6cf6
> > (serial: omap: fix software flow control).
> >
> > As Russell has pointed out, that commit isn't fixing
> > Software Flow Control at all, and it actually makes
> > it even more broken.
> >
> > It was agreed to revert this commit and use Russell's
> > latest UART patches instead.
> >
> > Cc: Russell King <linux@arm.linux.org.uk>
> > Signed-off-by: Felipe Balbi <balbi@ti.com>
>
> This seems like the best way to go for the -rc series:
>
> Acked-by: Tony Lindgren <tony@atomide.com>
Any chance you can pick this one up for v3.7-rc3 ?
cheers
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-10-24 10:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 14:09 [PATCH] Revert "serial: omap: fix software flow control" Felipe Balbi
2012-10-16 15:13 ` Tony Lindgren
2012-10-24 10:02 ` Felipe Balbi [this message]
2012-10-24 18:57 ` Greg KH
2012-10-24 18:53 ` Felipe Balbi
2012-11-07 9:56 ` Andreas Bießmann
2012-11-21 20:21 ` 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=20121024100254.GG5665@arwen.pp.htv.fi \
--to=balbi@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=santosh.shilimkar@ti.com \
--cc=tony@atomide.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