From: David Miller <davem@davemloft.net>
To: marcel@holtmann.org
Cc: keithp@keithp.com, gustavo@padovan.org,
linux-kernel@vger.kernel.org, linux-bluetooth@vger.kernel.org,
johan.hedberg@intel.com
Subject: Re: [PATCH] Revert "Bluetooth: Always enable management interface"
Date: Thu, 29 Mar 2012 00:39:50 -0400 (EDT) [thread overview]
Message-ID: <20120329.003950.997517954860580620.davem@davemloft.net> (raw)
In-Reply-To: <1332992022.1870.183.camel@aeonflux>
From: Marcel Holtmann <marcel@holtmann.org>
Date: Thu, 29 Mar 2012 05:33:42 +0200
> I think we actually have a broken user space in this case. I do have a
> hunch on what went wrong. It is not the kernel's fault here.
I call bullshit.
It doesn't matter what userspace is doing, "broken" or however you
want to call it. The bluez on everyone's computer broke because of
the kernel change.
Therefore you must revert the kernel change or modify it so that
existing userland continues to work properly.
There is no other proper course of action.
And to think, I gave you bluetooth guys shit because of coding style
problems, that appears to have been just the tip of the iceberg.
next prev parent reply other threads:[~2012-03-29 4:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 1:19 [PATCH] Revert "Bluetooth: Always enable management interface" Keith Packard
2012-03-29 1:25 ` David Miller
2012-03-29 2:25 ` Marcel Holtmann
2012-03-29 2:28 ` Gustavo Padovan
2012-03-29 2:35 ` Keith Packard
2012-03-29 3:33 ` Marcel Holtmann
2012-03-29 4:39 ` David Miller [this message]
2012-03-29 4:40 ` David Miller
2012-03-30 6:54 ` Gustavo Padovan
2012-04-03 12:29 ` Gustavo Padovan
2012-04-05 22:24 ` Keith Packard
2012-04-06 1:01 ` Gustavo Padovan
2012-03-29 3:48 ` Keith Packard
2012-03-29 4:40 ` David Miller
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=20120329.003950.997517954860580620.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=gustavo@padovan.org \
--cc=johan.hedberg@intel.com \
--cc=keithp@keithp.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.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).