From: Johan Hedberg <johan.hedberg@gmail.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Bug in audio/AVRCP
Date: Wed, 2 Apr 2008 17:50:49 +0300 [thread overview]
Message-ID: <D9DBA8CC-0F30-4B95-8B94-A0DEC4F73674@gmail.com> (raw)
In-Reply-To: <014c01c894ca$6cfbe010$6701a8c0@freqonedev>
Hi David,
On Apr 2, 2008, at 17:04, David Stockwell wrote:
> There appears to be a bug in 3.29/audio/control.c, lines 1050-1051.
> In avrcp_exit, the code removes the ct_record_id twice, and does
> nothing to remove the tg_record_id.
Thanks for the info, however it had already been fixed in the CVS.
Johan
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2008-04-02 14:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-02 14:04 [Bluez-devel] Bug in audio/AVRCP David Stockwell
2008-04-02 14:50 ` 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=D9DBA8CC-0F30-4B95-8B94-A0DEC4F73674@gmail.com \
--to=johan.hedberg@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox