public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Mario Limonciello <mario_limonciello@dell.com>
To: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Remove hid2hci from bluez
Date: Mon, 15 Jun 2009 09:43:27 -0500	[thread overview]
Message-ID: <4A365E0F.6000100@dell.com> (raw)
In-Reply-To: <1245076109.11069.7011.camel@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 1118 bytes --]

Hi Bastien:

Bastien Nocera wrote:
> On Mon, 2009-06-15 at 09:13 -0500, Mario Limonciello wrote:
>   
>
> Why? Instead of calling hid2hci, it would launch bluetoothd --udev, like
> the other rules. Problem solved.
>   
Good point, that's sensible enough.
>   
>
> If that's the only benefit, then, frankly, who cares.
>
> The main point is that people with an interested in Bluetooth will need
> to go and fetch the code, and ask for patches to be committed.
>
> We're losing direct commit access to the code, and gaining something
> that could have been achieved in the distro package.
>
>   
Eh, direct commit access?  You submit it to this mailing list and Marcel
has to ack it, you submit it to linux-hotplug and Kay or Martin acks
it.  Seems to be 6 eggs in one hand, half a dozen in the other.  Look
over the history, and those hacking on hid2hci have been me and Marcel:
http://git.kernel.org/?p=bluetooth/bluez.git;a=history;f=tools/hid2hci.c;h=11d707fd76e940b884c9078907ab1
504cd7350d4;hb=HEAD



-- 
Mario Limonciello
*Dell | Linux Engineering*
mario_limonciello@dell.com


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 260 bytes --]

  reply	other threads:[~2009-06-15 14:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-14 22:54 [PATCH] Remove hid2hci from bluez Mario_Limonciello
2009-06-14 23:33 ` Bastien Nocera
2009-06-15 14:13   ` Mario Limonciello
2009-06-15 14:28     ` Bastien Nocera
2009-06-15 14:43       ` Mario Limonciello [this message]
2009-06-15 19:08       ` Marcel Holtmann
2009-06-19 17:04         ` Mario Limonciello
2009-06-19 17:05         ` Mario Limonciello
2009-06-15  8:20 ` Simon Kenyon
2009-06-15 10:03   ` Bastien Nocera
2009-06-15 15:07     ` Simon Kenyon

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=4A365E0F.6000100@dell.com \
    --to=mario_limonciello@dell.com \
    --cc=linux-bluetooth@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox