From: Greg KH <gregkh@linuxfoundation.org>
To: "Andreas Bießmann" <andreas.devel@googlemail.com>
Cc: Felipe Balbi <balbi@ti.com>,
linux@arm.linux.org.uk,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
Linux ARM Kernel Mailing List
<linux-arm-kernel@lists.infradead.org>,
stable@vger.kernel.org
Subject: Re: [PATCH] Revert "serial: omap: fix software flow control"
Date: Wed, 21 Nov 2012 12:21:14 -0800 [thread overview]
Message-ID: <20121121202114.GC30682@kroah.com> (raw)
In-Reply-To: <509A306B.10409@gmail.com>
On Wed, Nov 07, 2012 at 10:56:59AM +0100, Andreas Bießmann wrote:
> On 16.10.2012 16:09, Felipe Balbi wrote:
> > 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>
>
> since 957ee7270d632245b43f6feb0e70d9a5e9ea6cf6 made it into stable (at
> least 3.4) I think it would be good decision to also apply this revert
> to stable until a working solution exists.
Now queued up for the stable releases, thanks.
greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: gregkh@linuxfoundation.org (Greg KH)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Revert "serial: omap: fix software flow control"
Date: Wed, 21 Nov 2012 12:21:14 -0800 [thread overview]
Message-ID: <20121121202114.GC30682@kroah.com> (raw)
In-Reply-To: <509A306B.10409@gmail.com>
On Wed, Nov 07, 2012 at 10:56:59AM +0100, Andreas Bie?mann wrote:
> On 16.10.2012 16:09, Felipe Balbi wrote:
> > 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>
>
> since 957ee7270d632245b43f6feb0e70d9a5e9ea6cf6 made it into stable (at
> least 3.4) I think it would be good decision to also apply this revert
> to stable until a working solution exists.
Now queued up for the stable releases, thanks.
greg k-h
WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: "Andreas Bießmann" <andreas.devel@googlemail.com>
Cc: Felipe Balbi <balbi@ti.com>,
linux@arm.linux.org.uk,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
Linux OMAP Mailing List <linux-omap@vger.kernel.org>,
Linux ARM Kernel Mailing List
<linux-arm-kernel@lists.infradead.org>,
stable@vger.kernel.org
Subject: Re: [PATCH] Revert "serial: omap: fix software flow control"
Date: Wed, 21 Nov 2012 12:21:14 -0800 [thread overview]
Message-ID: <20121121202114.GC30682@kroah.com> (raw)
In-Reply-To: <509A306B.10409@gmail.com>
On Wed, Nov 07, 2012 at 10:56:59AM +0100, Andreas Bießmann wrote:
> On 16.10.2012 16:09, Felipe Balbi wrote:
> > 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>
>
> since 957ee7270d632245b43f6feb0e70d9a5e9ea6cf6 made it into stable (at
> least 3.4) I think it would be good decision to also apply this revert
> to stable until a working solution exists.
Now queued up for the stable releases, thanks.
greg k-h
next prev parent reply other threads:[~2012-11-21 20:21 UTC|newest]
Thread overview: 19+ 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 14:09 ` Felipe Balbi
2012-10-16 14:09 ` Felipe Balbi
2012-10-16 15:13 ` Tony Lindgren
2012-10-16 15:13 ` Tony Lindgren
2012-10-24 10:02 ` Felipe Balbi
2012-10-24 10:02 ` Felipe Balbi
2012-10-24 10:02 ` Felipe Balbi
2012-10-24 18:57 ` Greg KH
2012-10-24 18:57 ` Greg KH
2012-10-24 18:53 ` Felipe Balbi
2012-10-24 18:53 ` Felipe Balbi
2012-10-24 18:53 ` Felipe Balbi
2012-11-07 9:56 ` Andreas Bießmann
2012-11-07 9:56 ` Andreas Bießmann
2012-11-07 9:56 ` Andreas Bießmann
2012-11-21 20:21 ` Greg KH [this message]
2012-11-21 20:21 ` Greg KH
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=20121121202114.GC30682@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=andreas.devel@googlemail.com \
--cc=balbi@ti.com \
--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=stable@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.