All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Sheldon Demario <sheldon.demario@openbossa.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] Cleanup of device class update signal
Date: Thu, 19 May 2011 16:35:44 -0700	[thread overview]
Message-ID: <20110519233544.GC4016@dell.ger.corp.intel.com> (raw)
In-Reply-To: <1305814620-8649-1-git-send-email-sheldon.demario@openbossa.org>

Hi Sheldon,

On Thu, May 19, 2011, Sheldon Demario wrote:
> Adds a new device function to address the PropertyChanged
> signal when the device's class changes. event.c file should
> avoid sending signals that belongs to device objects.
> ---
>  src/device.c |    8 ++++++++
>  src/device.h |    1 +
>  src/event.c  |    9 ++-------
>  3 files changed, 11 insertions(+), 7 deletions(-)

Applied. Thanks.

Johan

  reply	other threads:[~2011-05-19 23:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-19 14:17 [PATCH] Cleanup of device class update signal Sheldon Demario
2011-05-19 23:35 ` Johan Hedberg [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-04-20 21:42 Sheldon Demario

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=20110519233544.GC4016@dell.ger.corp.intel.com \
    --to=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=sheldon.demario@openbossa.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 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.