All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] hcid dbus patches
Date: Fri, 15 Sep 2006 13:55:34 +0200	[thread overview]
Message-ID: <1158321334.5233.13.camel@localhost> (raw)
In-Reply-To: <45015406.60208@vasmac.com>

Hi Jose,

> Here are a couple of patches that implement the following
> commands in dbus-test:
> GetRemoteClass
> GetRemoteServiceHandles
> GetRemoteServiceRecord
> 
> This required modifications to dbus-sdp.c. The problem was
> that the call to dbus_message_get_args in this file used a NULL
> pointer for the error structure. This patch adds a pointer in
> the same way that dbus-adapter.c calls dbus_messsage_get_args.
> The end result is that both GetRemoteService* calls now seem
> to work.

I am not following that argument. If we don't care about the error code,
then why should we fill one it. If this is a problem, then the problem
is in the D-Bus low-level library or the Python bindings.

Regards

Marcel



-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2006-09-15 11:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-08 11:29 [Bluez-devel] hcid dbus patches Jose Vasconcellos
2006-09-15 11:55 ` Marcel Holtmann [this message]
2006-09-15 13:42   ` Jose Vasconcellos
2006-09-15 13:46     ` 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=1158321334.5233.13.camel@localhost \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.