linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ravi Kumar Veeramally <ravikumar.veeramally@linux.intel.com>
To: linux-bluetooth@vger.kernel.org, Johan Hedberg <johan.hedberg@gmail.com>
Subject: Re: [PATCH_v2 02/11] android/hid: Add a ascii2hex utility
Date: Fri, 08 Nov 2013 11:05:33 +0200	[thread overview]
Message-ID: <527CA95D.8010305@linux.intel.com> (raw)
In-Reply-To: <20131108084831.GA19729@x220.p-661hnu-f1>


On 11/08/2013 10:48 AM, Johan Hedberg wrote:
> Hi Ravi,
>
> On Fri, Nov 08, 2013, Ravi Kumar Veeramally wrote:
>>>> +void ascii2hex(const uint8_t *ascii, int ascii_len, uint8_t *hex)
>>>> +{
>>>> +	int i;
>>>> +
>>>> +	if (!ascii || !hex)
>>>> +		return;
>>>> +
>>>> +	for (i = 0; i < ascii_len / 2; i++)
>>>> +		sscanf((char *) &ascii[i * 2], "%02x",
>>>> +						(unsigned int *) &hex[i]);
>>>> +
>>>> +}
>>> I'd just keep this static inside the HID HAL since that seems to be
>>> the only user for it. Actually I'm not even convinced that it's worth
>>> to have this as a separate function since you only have two users and
>>> essentially the function is just two lines (the if-statement is
>>> redundant).
>> Ok, I will keep it as static. Do you want me to keep in HID HAL or HID
>> daemon?
> The daemon is where you were doing the conversion now as well, so no
> need to change that (sorry about being unclear when I said "HID HAL").
>
>>> Also, the function name isn't quite right. You're converting from hex
>>> to binary
>>   We are converting to hex right? correct me If I am wrong.
> No, we're converting from hex to binary.
>
>>> . Not from ascii to hex (hex notation is already using
>>> the ascii character set). Also, do consider the point from Jerzy about
>>> the format specifier.
>>>
>>   Ok, I will fix Jerzy's suggestion also.
>>
>> Apart from this patch, do you have any comments on rest of the
>> patches?
> Only the ones I already sent.
>
> Johan
>
  Ok, Patch_v2 6 & 7 are independent of ascii stuff, can be it possible to
  apply if there are no comments? (just a request!!).

  Thanks a lot,
  Ravi.

  reply	other threads:[~2013-11-08  9:05 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-07 22:10 [PATCH_v2 00/11] Fix issues and implement virtual unplug and send data Ravi kumar Veeramally
2013-11-07 22:10 ` [PATCH_v2 01/11] android/hid: Remove fixed number of hid set report data length in ipc doc Ravi kumar Veeramally
2013-11-07 22:10 ` [PATCH_v2 02/11] android/hid: Add a ascii2hex utility Ravi kumar Veeramally
2013-11-08  6:44   ` Jerzy Kasenberg
2013-11-08  8:10   ` Johan Hedberg
     [not found]     ` <527CA596.6070602@linux.intel.com>
2013-11-08  8:48       ` Johan Hedberg
2013-11-08  9:05         ` Ravi Kumar Veeramally [this message]
2013-11-07 22:10 ` [PATCH_v2 03/11] android/hid: Fix set report data format Ravi kumar Veeramally
2013-11-07 22:10 ` [PATCH_v2 04/11] android/hid: Add missing hid send data parameters in ipc document Ravi kumar Veeramally
2013-11-07 22:10 ` [PATCH_v2 05/11] android/hid: Add missing parameters in send data struct in HAL headers Ravi kumar Veeramally
2013-11-07 22:10 ` [PATCH_v2 06/11] android/hid: Fill send data structure variables in hal-hidhost Ravi kumar Veeramally
2013-11-08  9:17   ` Johan Hedberg
2013-11-08  9:30     ` Ravi Kumar Veeramally
2013-11-07 22:10 ` [PATCH_v2 07/11] android/hid: Rename virtual unplug define and struct Ravi kumar Veeramally
2013-11-08  9:18   ` Johan Hedberg
2013-11-07 22:10 ` [PATCH_v2 08/11] android/hid: Add hid event virtual unplug structure to HAL msg headers Ravi kumar Veeramally
2013-11-07 22:10 ` [PATCH_v2 09/11] android/hid: Handle virtual unplug notification in hid hal Ravi kumar Veeramally
2013-11-08  8:39   ` Johan Hedberg
2013-11-07 22:10 ` [PATCH_v2 10/11] android/hid: Add virtual unplug implemention in daemon Ravi kumar Veeramally
2013-11-08  8:37   ` Johan Hedberg
2013-11-07 22:10 ` [PATCH_v2 11/11] android/hid: Add send data " Ravi kumar Veeramally

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=527CA95D.8010305@linux.intel.com \
    --to=ravikumar.veeramally@linux.intel.com \
    --cc=johan.hedberg@gmail.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;
as well as URLs for NNTP newsgroup(s).