[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140310150858.GA25703@tuxdriver.com>
Date: Mon, 10 Mar 2014 11:08:58 -0400
From: "John W. Linville" <linville@...driver.com>
To: Sander Eikelenboom <linux@...elenboom.it>
Cc: Marcel Holtmann <marcel@...tmann.org>,
"Gustavo F. Padovan" <gustavo@...ovan.org>,
Peter Hurley <peter@...leysoftware.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
"bluez mailin list (linux-bluetooth@...r.kernel.org)"
<linux-bluetooth@...r.kernel.org>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [RC6 Bell Chime] Re: [PATCH 00/24] rfcomm fixes
On Mon, Mar 10, 2014 at 09:38:43AM +0100, Sander Eikelenboom wrote:
> Hi all,
>
> Since:
> - 3.14-RC6 has been cut
> - this regression is known and reported since the merge window
> - the fix (revert of 3 patches) is known for over a month now
> - but it's still not in mainline
> - my polite ping request from last week seems to have provoked exactly 0 (zero) response.
>
> IT'S TIME TO CHIME SOME BELLS :-)
>
> Hope that WILL be heard somewhere ...
>
> --
> Sander
>
> PS. on the informative side the 3 commits to be reverted are:
>
> f86772af6a0f643d3e13eb3f4f9213ae0c333ee4 Bluetooth: Remove rfcomm_carrier_raised()
> 4a2fb3ecc7467c775b154813861f25a0ddc11aa0 Bluetooth: Always wait for a connection on RFCOMM open()
> e228b63390536f5b737056059a9a04ea016b1abf Bluetooth: Move rfcomm_get_device() before rfcomm_dev_activate()
Gustavo, should I be expecting a pull request?
--
John W. Linville Someday the world will need a hero, and you
linville@...driver.com might be all we have. Be ready.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists