From: Brad Midgley <bmidgley@xmission.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] First try
Date: Mon, 05 Jun 2006 23:05:48 -0600 [thread overview]
Message-ID: <44850D2C.9080708@xmission.com> (raw)
In-Reply-To: <447EA02C.3070703@palmsource.com>
Fr=E9d=E9ric
I had a look at your a2dp patches to move globals into the
per-connection struct. It all looks like a clear improvement. I didn't
have any problems with changes in quality after the change.
Would you like to check things out of cvs and verify it works for you?
thanks
Brad
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-06-06 5:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-30 17:03 [Bluez-devel] First try Frédéric DALLEAU
2006-06-01 7:19 ` Brad Midgley
2006-06-01 8:07 ` Frédéric DALLEAU
2006-06-01 8:27 ` Marcel Holtmann
2006-06-06 5:05 ` Brad Midgley [this message]
2006-06-19 8:03 ` Frédéric DALLEAU
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=44850D2C.9080708@xmission.com \
--to=bmidgley@xmission.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;
as well as URLs for NNTP newsgroup(s).