From: Johan Hedberg <johan.hedberg@gmail.com>
To: lkslawek@gmail.com
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v2 1/4] Add skeleton for Message Access Profile plugin
Date: Thu, 10 Mar 2011 13:58:28 +0200 [thread overview]
Message-ID: <20110310115828.GB18256@jh-x301> (raw)
In-Reply-To: <1299755065-4816-1-git-send-email-lkslawek@gmail.com>
Hi Slawek,
On Thu, Mar 10, 2011, lkslawek@gmail.com wrote:
> This patch introduces skeleton of a plugin supporting server role side
> of Bluetooth SIG profile defining procedures for exchanging message
> objects.
>
> The plugin can be compiled with different backends used for accessing
> message repository. This can be selected during configure:
>
> ./configure --with-messages=backend_name
>
> When no backend is specified, the default dummy is chosen.
>
> There is also a new command line option to obexd needed to start Message
> Access service:
>
> obexd [...] --mas
> ---
> v2: fix copyright declarations
>
> .gitignore | 1 +
> Makefile.am | 10 +++++++++-
> configure.ac | 12 ++++++++++++
> plugins/mas.c | 42 ++++++++++++++++++++++++++++++++++++++++++
> plugins/messages-dummy.c | 28 ++++++++++++++++++++++++++++
> plugins/messages.h | 22 ++++++++++++++++++++++
> src/main.c | 11 +++++++++--
> src/obex.h | 1 +
> 8 files changed, 124 insertions(+), 3 deletions(-)
> create mode 100644 plugins/mas.c
> create mode 100644 plugins/messages-dummy.c
> create mode 100644 plugins/messages.h
This patch has been pushed upstream, however I'll wait until we reach a
consensus on the coding style issues for the other patches before
proceeding with them.
Johan
prev parent reply other threads:[~2011-03-10 11:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 11:04 [PATCH v2 1/4] Add skeleton for Message Access Profile plugin lkslawek
2011-03-10 11:58 ` Johan Hedberg [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=20110310115828.GB18256@jh-x301 \
--to=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=lkslawek@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