From: Johan Hedberg <johan.hedberg@gmail.com>
To: Paulo Alcantara <pcacjr@zytor.com>
Cc: paulo.alcantara@openbossa.org, linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 00/15] Store address type on storage - remaining files
Date: Fri, 25 May 2012 10:39:22 +0300 [thread overview]
Message-ID: <20120525073922.GA13680@x220> (raw)
In-Reply-To: <20120524.145707.1901844181634748035.pcacjr@zytor.com>
Hi Paulo,
On Thu, May 24, 2012, Paulo Alcantara wrote:
> > On Wed, May 23, 2012, Paulo Alcantara wrote:
> > > This patchset contains the remaining changes for the new storage format
> > > used (bdaddr#type) on storage files (LE-only or shared files).
> > >
> > > The files that have been changed so far are:
> > > primaries, characteristics, appearance, ccc, names, aliases,
> > > longtermkeys, attributes, blocked.
> >
> > Any files that are used for BR/EDR would have to keep their backwards
> > compatibility. Otherwise someone who upgrades from 4.99 to 4.100 will
> > suddenly find that the device they had blocked is not blocked anymore
> > and none of their devices have any names. We can't break something like
> > that between 4.x versions. Are these patches guaranteeing this backwards
> > compatibility? Looking at the patches it doesn't look like they give
> > this guarantee.
>
> Ok, you're right. The only file that we should keep backward compatibility on
> this series is the blocked file, since it's shared by both BR/EDR and LE devices.
The aliases and names files are also shared with BR/EDR. It seems your
patches do not take this into account.
Johan
next prev parent reply other threads:[~2012-05-25 7:39 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-23 18:48 [PATCH BlueZ 00/15] Store address type on storage - remaining files Paulo Alcantara
2012-05-23 18:48 ` [PATCH BlueZ 01/15] storage: Store address type in "characteristics" Paulo Alcantara
2012-05-23 18:48 ` [PATCH BlueZ 02/15] storage: Store address type in "appearance" file Paulo Alcantara
2012-05-23 18:48 ` [PATCH BlueZ 03/15] storage: Store address type in "ccc" file Paulo Alcantara
2012-05-23 18:48 ` [PATCH BlueZ 04/15] storage: Store address type in "names" file Paulo Alcantara
2012-05-23 18:48 ` [PATCH BlueZ 05/15] storage: Store address type in "aliases" file Paulo Alcantara
2012-05-23 18:48 ` [PATCH BlueZ 06/15] core: Fix reading stored data from "aliases" and "names" file Paulo Alcantara
2012-05-23 18:48 ` [PATCH BlueZ 07/15] storage: Store address type in blocked file Paulo Alcantara
2012-05-23 18:48 ` [PATCH BlueZ 08/15] storage: Do not store address type twice Paulo Alcantara
2012-05-23 18:48 ` [PATCH BlueZ 09/15] storage: Store address type in "longtermkeys" file Paulo Alcantara
2012-05-23 18:48 ` [PATCH BlueZ 10/15] core: Fix creating device from " Paulo Alcantara
2012-05-23 18:48 ` [PATCH BlueZ 11/15] storage: Store address type in "attributes" file Paulo Alcantara
2012-05-23 18:48 ` [PATCH BlueZ 12/15] core: Fix creating device from "blocked" file Paulo Alcantara
2012-05-23 18:48 ` [PATCH BlueZ 13/15] storage: Rename characteristic to characteristics Paulo Alcantara
2012-05-23 18:48 ` [PATCH BlueZ 14/15] storage: Rename primary file to primaries Paulo Alcantara
2012-05-23 18:48 ` [PATCH BlueZ 15/15] core: Fix deleting entries Paulo Alcantara
2012-05-24 7:59 ` [PATCH BlueZ 00/15] Store address type on storage - remaining files Johan Hedberg
2012-05-24 17:57 ` Paulo Alcantara
2012-05-25 7:39 ` Johan Hedberg [this message]
2012-05-24 18:45 ` [PATCH BlueZ v2 00/16] " Paulo Alcantara
2012-05-24 18:45 ` [PATCH BlueZ v2 01/16] storage: Store address type in "characteristics" Paulo Alcantara
2012-05-24 18:45 ` [PATCH BlueZ v2 02/16] storage: Store address type in "appearance" file Paulo Alcantara
2012-05-24 18:46 ` [PATCH BlueZ v2 03/16] storage: Store address type in "ccc" file Paulo Alcantara
2012-05-24 18:46 ` [PATCH BlueZ v2 04/16] storage: Store address type in "names" file Paulo Alcantara
2012-05-24 18:46 ` [PATCH BlueZ v2 05/16] storage: Store address type in "aliases" file Paulo Alcantara
2012-05-24 18:46 ` [PATCH BlueZ v2 06/16] core: Fix reading stored data from "aliases" and "names" file Paulo Alcantara
2012-05-24 18:46 ` [PATCH BlueZ v2 07/16] storage: Store address type in blocked file Paulo Alcantara
2012-05-24 18:46 ` [PATCH BlueZ v2 08/16] storage: Do not store address type twice Paulo Alcantara
2012-05-24 18:46 ` [PATCH BlueZ v2 09/16] storage: Store address type in "longtermkeys" file Paulo Alcantara
2012-05-24 18:46 ` [PATCH BlueZ v2 10/16] core: Fix creating device from " Paulo Alcantara
2012-05-24 18:46 ` [PATCH BlueZ v2 11/16] storage: Store address type in "attributes" file Paulo Alcantara
2012-05-24 18:46 ` [PATCH BlueZ v2 12/16] core: Fix creating device from "blocked" file Paulo Alcantara
2012-05-24 18:46 ` [PATCH BlueZ v2 13/16] storage: Rename characteristic to characteristics Paulo Alcantara
2012-05-24 18:46 ` [PATCH BlueZ v2 14/16] storage: Rename primary file to primaries Paulo Alcantara
2012-05-24 18:46 ` [PATCH BlueZ v2 15/16] core: Fix deleting entries Paulo Alcantara
2012-05-24 18:46 ` [PATCH BlueZ v2 16/16] storage: Keep backward compatibility Paulo Alcantara
2012-05-25 15:46 ` [PATCH BlueZ v3 00/18] Store address type on storage - remaining files Paulo Alcantara
2012-05-25 15:46 ` [PATCH BlueZ v3 01/18] storage: Store address type in "characteristics" Paulo Alcantara
2012-05-25 15:46 ` [PATCH BlueZ v3 02/18] storage: Store address type in "appearance" file Paulo Alcantara
2012-05-25 15:46 ` [PATCH BlueZ v3 03/18] storage: Store address type in "ccc" file Paulo Alcantara
2012-05-25 15:46 ` [PATCH BlueZ v3 04/18] storage: Store address type in "names" file Paulo Alcantara
2012-05-25 15:46 ` [PATCH BlueZ v3 05/18] storage: Store address type in "aliases" file Paulo Alcantara
2012-05-25 15:46 ` [PATCH BlueZ v3 06/18] core: Fix reading stored data from "aliases" and "names" file Paulo Alcantara
2012-05-25 15:46 ` [PATCH BlueZ v3 07/18] storage: Store address type in blocked file Paulo Alcantara
2012-05-25 15:47 ` [PATCH BlueZ v3 08/18] storage: Do not store address type twice Paulo Alcantara
2012-05-25 15:47 ` [PATCH BlueZ v3 09/18] storage: Store address type in "longtermkeys" file Paulo Alcantara
2012-05-25 15:47 ` [PATCH BlueZ v3 10/18] core: Fix creating device from " Paulo Alcantara
2012-05-25 15:47 ` [PATCH BlueZ v3 11/18] storage: Store address type in "attributes" file Paulo Alcantara
2012-05-25 15:47 ` [PATCH BlueZ v3 12/18] core: Fix creating device from "blocked" file Paulo Alcantara
2012-05-25 15:47 ` [PATCH BlueZ v3 13/18] storage: Rename characteristic to characteristics Paulo Alcantara
2012-05-25 15:47 ` [PATCH BlueZ v3 14/18] storage: Rename primary file to primaries Paulo Alcantara
2012-05-25 15:47 ` [PATCH BlueZ v3 15/18] core: Fix deleting entries Paulo Alcantara
2012-05-25 15:47 ` [PATCH BlueZ v3 16/18] storage: Keep backward compatibility in "blocked" file Paulo Alcantara
2012-05-25 15:47 ` [PATCH BlueZ v3 17/18] storage: Keep backward compatibility in "names" file Paulo Alcantara
2012-05-25 15:47 ` [PATCH BlueZ v3 18/18] storage: Keep backward compatibility in "aliases" file Paulo Alcantara
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=20120525073922.GA13680@x220 \
--to=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=paulo.alcantara@openbossa.org \
--cc=pcacjr@zytor.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).