linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frederic Danis <frederic.danis@linux.intel.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] sdp: Prevent duplicate records registration
Date: Fri, 29 Jun 2012 15:52:30 +0200	[thread overview]
Message-ID: <4FEDB31E.50806@linux.intel.com> (raw)
In-Reply-To: <CABBYNZ+JXbzCKc4NyLdfCSKqd65E1X2n14cOko_4YO3dgghZUA@mail.gmail.com>

Hello Luiz,

On 29/06/2012 15:43, Luiz Augusto von Dentz wrote:
> Hi Johan,
>
> On Fri, Jun 29, 2012 at 4:35 PM, Johan Hedberg <johan.hedberg@gmail.com> wrote:
>>> This complicates a little bit more the code, the other option is to
>>> oFono don't do the socket management itself, this might be possible
>>> with org.bluez.Telephony, so just register an agent for DUN as it will
>>> be for HFP, bluetoothd takes care of handling the connection and
>>> authorization and when its done
>>
>> Isn't that exactly what the last two patches (for DUN and SAP) from the
>> telephony patch set do?
>
> I guess so, but I didn't remember those in the original series so it
> might be introduced latter, Frederic?
>
You are right, this was introduced in v10 of patches.


-- 
Frederic Danis                            Open Source Technology Center
frederic.danis@intel.com                              Intel Corporation




      reply	other threads:[~2012-06-29 13:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-20  9:02 [PATCH] sdp: Prevent duplicate records registration Frédéric Danis
2012-06-20  9:35 ` Johan Hedberg
2012-06-20 13:09   ` Frederic Danis
2012-06-21  8:36   ` Luiz Augusto von Dentz
2012-06-29 13:35     ` Johan Hedberg
2012-06-29 13:43       ` Luiz Augusto von Dentz
2012-06-29 13:52         ` Frederic Danis [this message]

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=4FEDB31E.50806@linux.intel.com \
    --to=frederic.danis@linux.intel.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@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).