linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Santiago Carot-Nemesio <sancane@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Heart Rate Profile API
Date: Sun, 4 Mar 2012 17:51:18 -0800	[thread overview]
Message-ID: <20120305015118.GA26388@x220> (raw)
In-Reply-To: <1330770910-7992-1-git-send-email-sancane@gmail.com>

Hi Santiago,

A couple of issues still:

On Sat, Mar 03, 2012, Santiago Carot-Nemesio wrote:
> @@ -0,0 +1,72 @@
> +BlueZ D-Bus Heart Rate API description
> +****************************************
> +
> +	Santiago Carot-Nemesio <sancane@gmail.com>

Is the above supposed to be a copyright statement? If so, fix it. (the
documentation files need that anyway).

> +Heart Rate Watcher hierarchy
> +============================
> +Service		unique name

Add an empty line after the header.

> +Interface	org.bluez.HeartRateWatcher
> +Object path	freely definable
> +
> +Methods		void MeasurementReceived(dict measure)
> +
> +			This callback is called whenever a heart rate measurement
> +			is received from the heart rate device. The unit for the
> +			Value is expressed in beats per minute (bpm). The energy
> +			field is optional and represents the accumulated energy
> +			expended in kilo Joules since last time it was reset.
> +			Furthermore, the device will be automatically reset when
> +			it is needed.
> +			The Contact field, if present, indicates that the device
> +			supports contact sensor, besides it will be true if skin
> +			contact is detected. The optional interval field is an
> +			array containing RR-Interval values which represent the
> +			time between two R-Wave detections, where the RR-Interval
> +			Value 0 is older than the Value 1 and so on.
> +
> +			Dict is defined as below:
> +			{
> +				"Value" : uint16,
> +				"Energy" : uint16,
> +				"Contact" : boolean,
> +				"Location" : ("Other", "Chest", "Wrist","Finger",
> +					"Hand", "Ear Lobe", "Foot"),
> +				"Interval" : array{uint16}
> +			}

Please reformat the above to be less than 80 characters wide. Right now
some lines are either 80 or 81.

Johan

  parent reply	other threads:[~2012-03-05  1:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-03 10:35 [PATCH] Heart Rate Profile API Santiago Carot-Nemesio
2012-03-03 11:48 ` Anderson Lizardo
2012-03-05  1:51 ` Johan Hedberg [this message]
2012-03-05  4:57 ` Marcel Holtmann
  -- strict thread matches above, loose matches on Subject: below --
2012-02-24  8:08 Santiago Carot-Nemesio
2012-03-02  8:55 ` Santiago Carot
2012-03-02 23:57 ` Johan Hedberg
2012-03-03  0:05   ` Anderson Lizardo
2012-03-03 10:30     ` Santiago Carot
2012-02-20  9:54 Heart Rate Profile v.2 Santiago Carot-Nemesio
2012-02-20  9:54 ` [PATCH] Heart Rate Profile API Santiago Carot-Nemesio
2012-02-23 16:06   ` Anderson Lizardo
2012-02-24  8:00     ` Santiago Carot
2012-02-17 10:37 RFC Heart Rate API Santiago Carot-Nemesio
2012-02-17 10:37 ` [PATCH] Heart Rate Profile API Santiago Carot-Nemesio
2012-02-17 12:00   ` Anderson Lizardo
2012-02-20  9:54     ` Santiago Carot

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=20120305015118.GA26388@x220 \
    --to=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=sancane@gmail.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;
as well as URLs for NNTP newsgroup(s).