Linux bluetooth development
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Paulo Alcantara <paulo.alcantara@openbossa.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v2 1/2] storage: Store BLE address type in "primary" file
Date: Tue, 22 May 2012 11:05:36 +0300	[thread overview]
Message-ID: <20120522080536.GB9688@x220> (raw)
In-Reply-To: <1337633316-4992-2-git-send-email-paulo.alcantara@openbossa.org>

Hi Paulo,

On Mon, May 21, 2012, Paulo Alcantara wrote:
> +	/* New format: address#type */
> +	ba2str(dba, key);
> +	sprintf(&key[17], "#%hhu", bdaddr_type);

Since BlueZ 4.100 will be the first user space version being able to use
mgmtops with a kernel where mgmt is enabled by default (3.4) I don't
think we need to worry about old format vs new format, i.e. the code
comment above is unnecessary.

> +	/* New format: address#type */
> +	ba2str(dba, key);
> +	sprintf(&key[17], "#%hhu", bdaddr_type);
> +
> +	str = textfile_caseget(filename, key);
> +	if (str != NULL)
> +		return str;
> +
> +	/* Old format: address only */
> +	key[17] = '\0';
> +
> +	return textfile_caseget(filename, key);

Same thing here. I think we can leave out any code that tries to work
with the old storage format since we can consider LE support as
experimental/unstable in all previous user space releases.

Johan

  reply	other threads:[~2012-05-22  8:05 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-18 20:57 [PATCH BlueZ 0/2] Store address type on storage Paulo Alcantara
2012-05-18 20:57 ` [PATCH BlueZ 1/2] storage: Store BLE address type in "primary" file Paulo Alcantara
2012-05-19  6:41   ` Johan Hedberg
2012-05-21 20:52     ` Paulo Alcantara
2012-05-18 20:57 ` [PATCH BlueZ 2/2] core: Fix creating device from " Paulo Alcantara
2012-05-19  6:43   ` Johan Hedberg
2012-05-21 20:56     ` Paulo Alcantara
2012-05-21 20:48 ` [PATCH BlueZ v2 0/2] Address type in keys on storage filesystem Paulo Alcantara
2012-05-21 20:48   ` [PATCH BlueZ v2 1/2] storage: Store BLE address type in "primary" file Paulo Alcantara
2012-05-22  8:05     ` Johan Hedberg [this message]
2012-05-22 17:08       ` Paulo Alcantara
2012-05-21 20:48   ` [PATCH BlueZ v2 2/2] core: Fix creating device from " Paulo Alcantara
2012-05-22  8:00     ` Johan Hedberg
2012-05-22 17:33       ` Claudio Takahasi
2012-05-22 19:45 ` [PATCH BlueZ v3 0/3] Store address type on storage Paulo Alcantara
2012-05-22 19:45   ` [PATCH BlueZ v3 1/3] storage: Store BLE address type in "primary" file Paulo Alcantara
2012-05-22 19:45   ` [PATCH BlueZ v3 2/3] core: Fix creating device from " Paulo Alcantara
2012-05-22 19:45   ` [PATCH BlueZ v3 3/3] core: Fix removing device services " Paulo Alcantara
2012-05-23 14:05   ` [PATCH BlueZ v3 0/3] Store address type on storage Johan Hedberg

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=20120522080536.GB9688@x220 \
    --to=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=paulo.alcantara@openbossa.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