All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Mikko Vinni <mmvinni@yahoo.com>,
	"Justin P. Mattock" <justinmattock@gmail.com>,
	Ed Tomlinson <edt@aei.ca>,
	"Gustavo F. Padovan" <padovan@profusion.mobi>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.38 kernel breaks userspace bluetooth management tools
Date: Mon, 11 Apr 2011 14:44:16 -0700	[thread overview]
Message-ID: <20110411214416.GB25899@kroah.com> (raw)
In-Reply-To: <loom.20110319T223719-154@post.gmane.org>

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

  parent reply	other threads:[~2011-04-11 21:45 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 [this message]
2011-04-12 15:47     ` Justin P. Mattock
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=20110411214416.GB25899@kroah.com \
    --to=greg@kroah.com \
    --cc=edt@aei.ca \
    --cc=justinmattock@gmail.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 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.