Linux bluetooth development
 help / color / mirror / Atom feed
From: Vinicius Costa Gomes <vcgomes@gmail.com>
To: Matthew Monaco <dgbaley27@0x01b.net>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] tools/hci2hid: properly format device path
Date: Mon, 4 Nov 2013 14:18:05 -0200	[thread overview]
Message-ID: <20131104161805.GA32089@molly.amr.corp.intel.com> (raw)
In-Reply-To: <963b569308352e0b0fc18a0a17e2b0c0fe721d72.1383529026.git.matthew.monaco@0x01b.net>

Hi Matthew,

On 18:46 Sun 03 Nov, Matthew Monaco wrote:
> From: Matthew Monaco <matthew.monaco@0x01b.net>
> 
> ---
> Hello! I hope this is the correct place to send a bugfix for bluez.
>  tools/hid2hci.c | 15 +++++++++------
>  1 file changed, 9 insertions(+), 6 deletions(-)

The patch itself looks good.

What I think is missing is a better description of the problem it solves, I
would suggest including in the commit message the values of 'path' for before
and after the patch, for a situation that the current implementation doesn't
work.

Changing the subject line to something like: "tools: Fix wrong paths for
adapters" would make it easier to tell that this patch is indeed a bug fix.

> 
> diff --git a/tools/hid2hci.c b/tools/hid2hci.c
> index bb8a521..8f22047 100644
> --- a/tools/hid2hci.c
> +++ b/tools/hid2hci.c
> @@ -221,18 +221,21 @@ static int usb_switch_dell(int fd, enum mode mode)
>  static int find_device(struct udev_device *udev_dev)
>  {
>  	char path[PATH_MAX];
> -	const char *busnum, *devnum;
> +	const char *str;
> +	long int busnum, devnum;
>  	int fd;
>  
> -	busnum = udev_device_get_sysattr_value(udev_dev, "busnum");
> -	if (!busnum)
> +	str = udev_device_get_sysattr_value(udev_dev, "busnum");
> +	if (!str)
>  		return -1;
> +	busnum = strtol(str, NULL, 0);
>  
> -	devnum = udev_device_get_sysattr_value(udev_dev, "devnum");
> -	if (!devnum)
> +	str = udev_device_get_sysattr_value(udev_dev, "devnum");
> +	if (!str)
>  		return -1;
> +	devnum = strtol(str, NULL, 0);
>  
> -	snprintf(path, sizeof(path), "/dev/bus/usb/%s/%s", busnum, devnum);
> +	snprintf(path, sizeof(path), "/dev/bus/usb/%03d/%03d", busnum, devnum);
>  
>  	fd = open(path, O_RDWR, O_CLOEXEC);
>  	if (fd < 0) {
> -- 
> 1.8.4.2
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


Cheers,
-- 
Vinicius

  reply	other threads:[~2013-11-04 16:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-04  1:46 [PATCH] tools/hci2hid: properly format device path Matthew Monaco
2013-11-04 16:18 ` Vinicius Costa Gomes [this message]
2013-11-04 16:23   ` Bastien Nocera
2013-11-04 16:42     ` Vinicius Costa Gomes
2013-11-04 16:52       ` Matthew Monaco

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=20131104161805.GA32089@molly.amr.corp.intel.com \
    --to=vcgomes@gmail.com \
    --cc=dgbaley27@0x01b.net \
    --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