public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Claudio Takahasi <claudio.takahasi@openbossa.org>
Cc: BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: [PATCH] Fix extra PropertyChanged signal sent after DeviceRemoved
Date: Tue, 22 Sep 2009 14:54:30 -0700	[thread overview]
Message-ID: <1253656470.2931.5.camel@localhost.localdomain> (raw)
In-Reply-To: <f9d4bd30909221431p33970fe8weab8c440b3d35edf@mail.gmail.com>

Hi Claudio,

> for paired devices, there is an extra PropertyChanged signal sent
> after DeviceRemoved:
> 
> signal sender=:1.78 -> dest=(null destination) serial=145
> path=/org/bluez/24533/hci0; interface=org.bluez.Adapter;
> member=PropertyChanged
>    string "Devices"
>    variant       array [
>       ]
> signal sender=:1.78 -> dest=(null destination) serial=146
> path=/org/bluez/24533/hci0; interface=org.bluez.Adapter;
> member=DeviceRemoved
>    object path "/org/bluez/24533/hci0/dev_00_1F_00_CE_BE_AF"
> signal sender=:1.78 -> dest=(null destination) serial=147
> path=/org/bluez/24533/hci0/dev_00_1F_00_CE_BE_AF;
> interface=org.bluez.Device; member=PropertyChanged
>    string "Paired"
>    variant       boolean false
> 
> 
> The patch to fix this issue is in my branch devel:
> 
> git://git.infradead.org/users/cktakahasi/bluez.git devel

patch has been applied. Thanks.

> I removed  "textfile_caseget()" call before call "textfile_casedel()",
> let me know if you wanna keep this check, I can revert this minor
> change.

I can't remember why it is there. Johan might know and we can revert it
then later if I missed the reason.

Regards

Marcel



      reply	other threads:[~2009-09-22 21:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-22 21:31 [PATCH] Fix extra PropertyChanged signal sent after DeviceRemoved Claudio Takahasi
2009-09-22 21:54 ` Marcel Holtmann [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=1253656470.2931.5.camel@localhost.localdomain \
    --to=marcel@holtmann.org \
    --cc=claudio.takahasi@openbossa.org \
    --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