From: Johan Hedberg <johan.hedberg@gmail.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH BlueZ v2] AVRCP: Fix not registering to VolumeChanged event again when notified
Date: Mon, 28 May 2012 18:29:44 +0300 [thread overview]
Message-ID: <20120528152944.GA28797@x220> (raw)
In-Reply-To: <1338203808-15142-1-git-send-email-luiz.dentz@gmail.com>
Hi Luiz,
On Mon, May 28, 2012, Luiz Augusto von Dentz wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> The spec says:
>
> "A registered notification gets changed on receiving CHANGED event
> notification. For a new notification additional NOTIFY command is
> expected to be sent."
> ---
> v2: Fix check to do logical AND not OR
>
> audio/avrcp.c | 9 ++++++++-
> 1 files changed, 8 insertions(+), 1 deletions(-)
Applied. Thanks.
Johan
prev parent reply other threads:[~2012-05-28 15:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-28 11:16 [PATCH BlueZ v2] AVRCP: Fix not registering to VolumeChanged event again when notified Luiz Augusto von Dentz
2012-05-28 15:16 ` Lucas De Marchi
2012-05-28 15:29 ` Johan Hedberg [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=20120528152944.GA28797@x220 \
--to=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@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;
as well as URLs for NNTP newsgroup(s).