All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Leigh Fiddes <leigh.fiddes@atomos.com>
Cc: Linux Bluetooth <linux-bluetooth@vger.kernel.org>
Subject: Re: [Proposed Patch Bluez v5] btmon: Print connection latency correctly
Date: Fri, 19 Aug 2016 10:49:29 +0200	[thread overview]
Message-ID: <35A91F39-E5C2-47F2-81D5-398797B31C1C@holtmann.org> (raw)
In-Reply-To: <155e0135-7d14-259d-322b-a582afb979c9@atomos.com>

Hi Leigh,

> I submit the following small patch for consideration.
> Leigh
> ---
> 
> In at least two places the Connection Latency field was being displayed by btmon in units of 1.25mS,
> which is incorrect. Print in decimal instead of hex as it is a number.

then print the connection latency with a correct unit and the hex value in parentheses. This way is not acceptable. If we need a print_field_msec helper, then introduce that and use it throughout.

Regards

Marcel


  reply	other threads:[~2016-08-19  8:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-19  7:00 [Proposed Patch Bluez v5] btmon: Print connection latency correctly Leigh Fiddes
2016-08-19  8:49 ` Marcel Holtmann [this message]
2016-08-19 12:01   ` Leigh Fiddes

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=35A91F39-E5C2-47F2-81D5-398797B31C1C@holtmann.org \
    --to=marcel@holtmann.org \
    --cc=leigh.fiddes@atomos.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.