From: "Justin P. Mattock" <justinmattock@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: Mikko Vinni <mmvinni@yahoo.com>, Ed Tomlinson <edt@aei.ca>,
"Gustavo F. Padovan" <padovan@profusion.mobi>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.38 kernel breaks userspace bluetooth management tools
Date: Tue, 12 Apr 2011 08:47:10 -0700 [thread overview]
Message-ID: <4DA473FE.2040800@gmail.com> (raw)
In-Reply-To: <20110411214416.GB25899@kroah.com>
On 04/11/2011 02:44 PM, Greg KH wrote:
> On Sat, Mar 19, 2011 at 09:46:03PM +0000, Mikko Vinni wrote:
>> İsmail Dönmez<ismail<at> namtrac.org> writes:
>>> According to http://www.bluez.org/the-management-interface/ bluetooth
>>> management interface has changed in the 2.6.38 kernel and this ends up
>>> breaking bluetooth management tools (the ones that get your bluetooth
>>> mouse working) in both KDE& Gnome ( see
>>> https://bugzilla.novell.com/show_bug.cgi?id=680170 ).
>>
>> This sounds like http://www.spinics.net/lists/linux-bluetooth/msg10695.html
>>
>> The fix is on its way. Nothing is deliberately broken.
>>
>> http://git.kernel.org/?p=linux/kernel/git/padovan/bluetooth-next-2.6.git;a=commitdiff;h=b99faf1b798d6d0e33526fd2cef55a405c08ff09;hp=58b6e124aac64bebb2e9e1a136cbd21a5ab0485a
>
> That fix isn't in the -stable tree, and doesn't apply cleanly to the
> .38-stable tree.
>
> Can someone provide a backport to stable@kernel.org?
>
> thanks,
>
> greg k-h
>
o.k my diff skills sucks, but(hopefully) backported correctly, sent out
to stable@kernel.org..
let me know if you get this or not(seems gmail is not showing my sent
mail)..
Justin P. Mattock
next prev parent reply other threads:[~2011-04-12 15:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-19 20:13 2.6.38 kernel breaks userspace bluetooth management tools İsmail Dönmez
2011-03-19 21:46 ` Mikko Vinni
2011-03-19 22:03 ` İsmail Dönmez
2011-04-11 21:44 ` Greg KH
2011-04-12 15:47 ` Justin P. Mattock [this message]
2011-04-12 15:58 ` Greg KH
2011-04-12 16:06 ` Justin P. Mattock
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=4DA473FE.2040800@gmail.com \
--to=justinmattock@gmail.com \
--cc=edt@aei.ca \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mmvinni@yahoo.com \
--cc=padovan@profusion.mobi \
/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