From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Revert "serial: omap: fix software flow control"
Date: Tue, 16 Oct 2012 08:13:59 -0700 [thread overview]
Message-ID: <20121016151357.GN15569@atomide.com> (raw)
In-Reply-To: <1350396562-32579-1-git-send-email-balbi@ti.com>
* 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>
next prev parent reply other threads:[~2012-10-16 15:13 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 [this message]
2012-10-24 10:02 ` Felipe Balbi
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=20121016151357.GN15569@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.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).