From: Johan Hedberg <johan.hedberg@gmail.com>
To: BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: [patch] fix the bug of obex_object_resume(), obex_server() in openobex
Date: Wed, 24 Dec 2008 03:23:26 +0200 [thread overview]
Message-ID: <3D8E1963-54E4-4974-98B3-6E9095046D30@gmail.com> (raw)
In-Reply-To: <ac8af0be0812221733j262e8077re27476f18772079e@mail.gmail.com>
Hi Forrest,
On Dec 23, 2008, at 3:33, Zhao Forrest wrote:
> When developing the PBAP server in obexd we found that
> obex_object_resume() can't work as expected. After debugging openobex
> we post this patch to fix the bug. We did the internal test with PBAP
> server/client. The below patch fixes the bug in obex_object_resume()
> and obex_server().
The patch seems fine and has been pushed upstream, thanks! Btw, in the
future please use the openobex-users mailing list for openobex
specific patches.
Johan
next prev parent reply other threads:[~2008-12-24 1:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-23 1:33 [patch] fix the bug of obex_object_resume(), obex_server() in openobex Zhao Forrest
2008-12-24 1:23 ` Johan Hedberg [this message]
2008-12-24 3:13 ` [patch] obexd: if path == NULL, don't call dbus_connection_get_object_path_data Liu, Raymond
2008-12-24 3:41 ` Marcel Holtmann
2008-12-24 5:05 ` Liu, Raymond
2008-12-24 6:17 ` Marcel Holtmann
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=3D8E1963-54E4-4974-98B3-6E9095046D30@gmail.com \
--to=johan.hedberg@gmail.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