From: Johan Hedberg <johan.hedberg@gmail.com>
To: Antonio Ospite <ospite@studenti.unina.it>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ 0/2] Add device_set_trusted()
Date: Fri, 15 Feb 2013 11:27:40 +0200 [thread overview]
Message-ID: <20130215092740.GB11352@x220> (raw)
In-Reply-To: <1359908071-15024-1-git-send-email-ospite@studenti.unina.it>
Hi Antonio,
On Sun, Feb 03, 2013, Antonio Ospite wrote:
> In patch 1 a device_set_trusted() function is proposed, which I plan to
> use for the playstation-peripheral plugin; I am in the process of
> rebasing the plugin on top of BlueZ 5.2.
>
> In patch 2 the newly introduced function is used in order to avoid some
> duplication.
>
> device_set_trusted() looks a lot like device_set_temporary() and
> device_set_legacy(), I hope it makes sense to you too.
>
> Thanks,
> Antonio
>
> Antonio Ospite (2):
> device: add a device_set_trusted() function
> device: use device_set_trusted() in set_trust()
>
> src/device.c | 30 +++++++++++++++++++-----------
> src/device.h | 1 +
> 2 files changed, 20 insertions(+), 11 deletions(-)
Both patches are now applied (after adding some needed info to the
commit messages for the justification of these changes).
Johan
next prev parent reply other threads:[~2013-02-15 9:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-03 16:14 [PATCH BlueZ 0/2] Add device_set_trusted() Antonio Ospite
2013-02-03 16:14 ` [PATCH BlueZ 1/2] device: add a device_set_trusted() function Antonio Ospite
2013-02-03 16:14 ` [PATCH BlueZ 2/2] device: use device_set_trusted() in set_trust() Antonio Ospite
2013-02-03 17:32 ` Anderson Lizardo
2013-02-03 17:51 ` Antonio Ospite
2013-02-03 18:27 ` Anderson Lizardo
2013-02-10 21:30 ` [PATCH BlueZ 0/2] Add device_set_trusted() Antonio Ospite
2013-02-15 8:36 ` Johan Hedberg
2013-02-15 8:40 ` Bastien Nocera
2013-02-15 8:57 ` Johan Hedberg
2013-02-15 9:17 ` Bastien Nocera
2013-02-15 9:24 ` Johan Hedberg
2013-02-15 9:27 ` Johan Hedberg [this message]
2013-02-15 11:01 ` Antonio Ospite
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=20130215092740.GB11352@x220 \
--to=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=ospite@studenti.unina.it \
/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