linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Divya Yadav <divya.yadav@samsung.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH obexd] MAP: Add application parameter parsing support
Date: Thu, 12 Jan 2012 15:16:07 +0200	[thread overview]
Message-ID: <20120112131607.GA13175@x220.ger.corp.intel.com> (raw)
In-Reply-To: <1326373161-4618-1-git-send-email-divya.yadav@samsung.com>

Hi,

On Thu, Jan 12, 2012, Divya Yadav wrote:
> Add application parameter parsing and check for
> mandatory parameters.
> ---
>  plugins/mas.c      |  187 ++++++++++++++++++++++++++++++++++++++++++++++++++--
>  plugins/messages.h |   19 +++++
>  2 files changed, 199 insertions(+), 7 deletions(-)

Are you aware of src/map_ap.h that we have in the obexd tree?

Johan

  reply	other threads:[~2012-01-12 13:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-12 12:59 [PATCH obexd] MAP: Add application parameter parsing support Divya Yadav
2012-01-12 13:16 ` Johan Hedberg [this message]
2012-01-13  7:18   ` Slawomir Bochenski

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=20120112131607.GA13175@x220.ger.corp.intel.com \
    --to=johan.hedberg@gmail.com \
    --cc=divya.yadav@samsung.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;
as well as URLs for NNTP newsgroup(s).