Linux bluetooth development
 help / color / mirror / Atom feed
From: Szymon Janc <szymon.janc@tieto.com>
To: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 00/10] Some HAL IPC work
Date: Thu, 12 Jun 2014 13:07:47 +0200	[thread overview]
Message-ID: <4128609.vozAJ6Wg1V@uw000953> (raw)
In-Reply-To: <1402497172-12436-1-git-send-email-szymon.janc@tieto.com>

On Wednesday 11 of June 2014 16:32:42 Szymon Janc wrote:
> Hi,
> 
> Those patches are cleanups and fixes for HAL part of IPC. Those are
> first step to making HAL IPC library like so that it can be reused
> by audio and sco HALs.
> 
> Eventually this should also allow for better recovery in case of IPC
> error i.e. not calling exit() directly but custom destroy callback.
> But this is not implemented yet.
> 
> Last two patches add FD passing in notification (as of now this is
> needed only for health HAL).
> 
> BR
> Szymon Janc
> 
> Szymon Janc (10):
>   android/ipc: Make struct service_handler private
>   android/hal-ipc: Allow to pass custom path to IPC
>   android/hal-ipc: Fix missing mutex unlock
>   android/hal-ipc: Move exit calls outside of handle_msg
>   android/hal-ipc: Move exit calls under failed label in hal_ipc_cmd
>   android/hal-ipc: Move exit calls under label in notification_handler
>   android/hal-ipc: Split IPC init and accept to separate functions
>   android/hal-ipc: Move daemon starting to bluetooth HAL
>   android/hal-ipc: Pass FD to notification handlers
>   android/ipc: Add support for sending FD in notifications
> 
>  android/hal-a2dp.c      |   4 +-
>  android/hal-avrcp.c     |  24 +++----
>  android/hal-bluetooth.c |  40 +++++++----
>  android/hal-gatt.c      |  62 ++++++++--------
>  android/hal-handsfree.c |  32 ++++-----
>  android/hal-health.c    |   2 +-
>  android/hal-hidhost.c   |  12 ++--
>  android/hal-ipc.c       | 186 ++++++++++++++++++++++++++----------------------
>  android/hal-ipc.h       |   5 +-
>  android/hal-pan.c       |   4 +-
>  android/ipc.c           |  13 +++-
>  android/ipc.h           |   8 +--
>  12 files changed, 214 insertions(+), 178 deletions(-)
> 
> 

Pushed.

-- 
Best regards, 
Szymon Janc

      parent reply	other threads:[~2014-06-12 11:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-11 14:32 [PATCH 00/10] Some HAL IPC work Szymon Janc
2014-06-11 14:32 ` [PATCH 01/10] android/ipc: Make struct service_handler private Szymon Janc
2014-06-11 14:32 ` [PATCH 02/10] android/hal-ipc: Allow to pass custom path to IPC Szymon Janc
2014-06-11 14:32 ` [PATCH 03/10] android/hal-ipc: Fix missing mutex unlock Szymon Janc
2014-06-11 14:32 ` [PATCH 04/10] android/hal-ipc: Move exit calls outside of handle_msg Szymon Janc
2014-06-11 14:32 ` [PATCH 05/10] android/hal-ipc: Move exit calls under failed label in hal_ipc_cmd Szymon Janc
2014-06-11 14:32 ` [PATCH 06/10] android/hal-ipc: Move exit calls under label in notification_handler Szymon Janc
2014-06-11 14:32 ` [PATCH 07/10] android/hal-ipc: Split IPC init and accept to separate functions Szymon Janc
2014-06-11 14:32 ` [PATCH 08/10] android/hal-ipc: Move daemon starting to bluetooth HAL Szymon Janc
2014-06-11 14:32 ` [PATCH 09/10] android/hal-ipc: Pass FD to notification handlers Szymon Janc
2014-06-11 14:32 ` [PATCH 10/10] android/ipc: Add support for sending FD in notifications Szymon Janc
2014-06-12 11:07 ` 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=4128609.vozAJ6Wg1V@uw000953 \
    --to=szymon.janc@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