From: Johan Hedberg <johan.hedberg@gmail.com>
To: Slawomir Bochenski <lkslawek@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH v2 4/4] Add detection of MAP function in OBEX requests
Date: Fri, 11 Mar 2011 13:13:13 +0200 [thread overview]
Message-ID: <20110311111313.GA20128@jh-x301> (raw)
In-Reply-To: <1299829612-3704-4-git-send-email-lkslawek@gmail.com>
Hi Slawek,
On Fri, Mar 11, 2011, Slawomir Bochenski wrote:
> There is also first part of mas.c <-> backend API. The mas_request
> structure will be used when calling backend functions.
> ---
> plugins/mas.c | 57 ++++++++++++++++++++++++++++++++++++++++++++++++++++
> plugins/messages.h | 15 +++++++++++++
> 2 files changed, 72 insertions(+), 0 deletions(-)
I've pushed 2/4 and 3/4 upstream, but there's at least issue one with
this last patch:
> +enum messages_function_id {
> + MFID_INVALID = 0,
> + MFID_SET_NOTIFICATION_REGISTRATION,
> + MFID_GET_FOLDER_LISTING,
> + MFID_GET_MESSAGES_LISTING,
> + MFID_GET_MESSAGE,
> + MFID_SET_MESSAGE_STATUS,
> + MFID_PUSH_MESSAGE,
> + MFID_UPDATE_INBOX,
> +};
Since "function" here doesn't seem to be referring to a C function but
to the type of request, could you call it e.g. request_type instead? Is
there a reason you you want to have this enum instead of e.g. storing
the original value of the type header?
Johan
next prev parent reply other threads:[~2011-03-11 11:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 7:46 [PATCH v2 0/4] Message Access Profile plugin Slawomir Bochenski
2011-03-11 7:46 ` [PATCH v2 2/4] Add actual service for Message Access Profile Slawomir Bochenski
2011-03-11 7:46 ` [PATCH v2 3/4] Add MIME driver to MAP plugin Slawomir Bochenski
2011-03-11 7:46 ` [PATCH v2 4/4] Add detection of MAP function in OBEX requests Slawomir Bochenski
2011-03-11 11:13 ` Johan Hedberg [this message]
2011-03-11 11:40 ` Slawomir Bochenski
2011-03-11 14:48 ` Johan Hedberg
2011-03-11 21:27 ` Johan Hedberg
2011-03-14 14:27 ` 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=20110311111313.GA20128@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