Linux bluetooth development
 help / color / mirror / Atom feed
From: Szymon Janc <szymon.janc@tieto.com>
To: Andrzej Kaczmarek <andrzej.kaczmarek@tieto.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 00/11] Socket HAL updates
Date: Wed, 12 Feb 2014 13:54:08 +0100	[thread overview]
Message-ID: <3646292.iBuS7jY2Rq@leonov> (raw)
In-Reply-To: <1392137901-3403-1-git-send-email-andrzej.kaczmarek@tieto.com>

Hi Andrzej,

On Tuesday 11 of February 2014 17:58:10 Andrzej Kaczmarek wrote:
> Hi,
> 
> Current socket HAL implementation is missing major feature which is
> ability to register RFCOMM server from application (so use some UUID
> and assign channel number dynamically). This corresponds to
> BluetoothAdapter::listenUsing(insecure)RfcommWithServiceRecord APIs
> in Android.
> 
> This series of patches adds this feature with other required fixes
> and also some does some minor refactoring.
> 
> Andrzej Kaczmarek (11):
>   android/bluetooth: Handle 128-bit UUIDs
>   android/socket: Refactor socket related symbol names
>   android/socket: Improve logging
>   android/socket: Simplify SDP records handling
>   android/socket: Make servers list as static array
>   android/tester: Update test data
>   android/socket: Add support for dynamic channel numbers
>   android/socket: Register SDP record for application service
>   android/socket: Include HF AG in built-in profiles
>   android/socket: Update channel numbers
>   android/socket: Fix sockets security
> 
>  android/android-tester.c |   2 +-
>  android/bluetooth.c      |  61 ++---
>  android/hal-msg.h        |   3 +
>  android/socket.c         | 658
> +++++++++++++++++++++++------------------------ 4 files changed, 349
> insertions(+), 375 deletions(-)

All patches in this set are now upstream, thanks a lot.

-- 
BR
Szymon Janc

      parent reply	other threads:[~2014-02-12 12:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-11 16:58 [PATCH 00/11] Socket HAL updates Andrzej Kaczmarek
2014-02-11 16:58 ` [PATCH 01/11] android/bluetooth: Handle 128-bit UUIDs Andrzej Kaczmarek
2014-02-11 16:58 ` [PATCH 02/11] android/socket: Refactor socket related symbol names Andrzej Kaczmarek
2014-02-11 16:58 ` [PATCH 03/11] android/socket: Improve logging Andrzej Kaczmarek
2014-02-11 16:58 ` [PATCH 04/11] android/socket: Simplify SDP records handling Andrzej Kaczmarek
2014-02-11 16:58 ` [PATCH 05/11] android/socket: Make servers list as static array Andrzej Kaczmarek
2014-02-11 16:58 ` [PATCH 06/11] android/tester: Update test data Andrzej Kaczmarek
2014-02-11 16:58 ` [PATCH 07/11] android/socket: Add support for dynamic channel numbers Andrzej Kaczmarek
2014-02-11 16:58 ` [PATCH 08/11] android/socket: Register SDP record for application service Andrzej Kaczmarek
2014-02-11 16:58 ` [PATCH 09/11] android/socket: Include HF AG in built-in profiles Andrzej Kaczmarek
2014-02-11 16:58 ` [PATCH 10/11] android/socket: Update channel numbers Andrzej Kaczmarek
2014-02-11 16:58 ` [PATCH 11/11] android/socket: Fix sockets security Andrzej Kaczmarek
2014-02-12  9:57 ` [PATCH 00/11] Socket HAL updates Andrei Emeltchenko
2014-02-12 12:55   ` Szymon Janc
2014-02-12 12:54 ` Szymon Janc [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=3646292.iBuS7jY2Rq@leonov \
    --to=szymon.janc@tieto.com \
    --cc=andrzej.kaczmarek@tieto.com \
    --cc=linux-bluetooth@vger.kernel.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