From: Marcel Holtmann <marcel@holtmann.org>
To: Mario Limonciello <mario_limonciello@dell.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH 1/3] Add support for command line arguments on hid2hci tool
Date: Fri, 15 May 2009 13:11:18 -0700 [thread overview]
Message-ID: <1242418278.3446.20.camel@localhost.localdomain> (raw)
In-Reply-To: <4A0DC533.8080900@dell.com>
Hi Mario,
> This means that hid2hci won't have to run
> on every bootup for every machine with bluetooth installed. It instead
> gets ran on demand if a
> product that is called out from the dbus rules file contains the
> correct attributes and/or VID/PID.
>
> It also makes it easier for users to manually test new VID/PID
> combinations that may or may not
> be yet supported by bluez.
> ---
> scripts/Makefile.am | 12 ++-
> scripts/bluetooth.default | 3 -
> scripts/bluetooth.init | 7 --
> scripts/hid2hci.rules | 38 ++++++++++
> tools/hid2hci.c | 179
> +++++++++++++++++++-------------------------
> 5 files changed, 124 insertions(+), 115 deletions(-)
> create mode 100644 scripts/hid2hci.rules
>
> Attaching patch as Exchange would mangle otherwise.
please restrict the commit message to 70-72 chars per line.
And please do the following changes:
s/radiomode/mode/ since it is not about the radio part here.
s/hidproxy/csr/ if you wanna expose this then call it what it is.
And go over the coding style once more since there are some cases where
it breaks.
Also please split Makefile/rules changes from the actual code changes. I
want two patches here. One that fixes the code and another one that
takes care of the udev integration.
Other than that, looks pretty good.
Regards
Marcel
next prev parent reply other threads:[~2009-05-15 20:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 19:40 [PATCH 1/3] Add support for command line arguments on hid2hci tool Mario Limonciello
2009-05-15 20:11 ` Marcel Holtmann [this message]
2009-05-15 22:07 ` Mario Limonciello
2009-05-16 13:35 ` Marcel Holtmann
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=1242418278.3446.20.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mario_limonciello@dell.com \
/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