From: "Harri Mähönen" <harri.mahonen@gmail.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH] audio: fix memory leak with typefinding
Date: Thu, 24 Jun 2010 17:36:38 +0300 [thread overview]
Message-ID: <AANLkTinpwLVnJwrAyDS87p0wavVFCNzssiNJl7TkyTaE@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimbLBxcU5nZE9UUQJGkHgMLe5LNnvLt1G0jckVF@mail.gmail.com>
On Thu, Jun 24, 2010 at 11:09 AM, Luiz Augusto von Dentz
<luiz.dentz@gmail.com> wrote:
> Sorry, I misunderstood the problem, it is really gstreamer only issue,
> but I would suggest using the return of sbc_parse so we don't have to
> hardcode sbc sync word detection, something like the following:
Thank you for your comments, I agree with using sbc_parse to avoid
hardcoded sbc sync word detection. I'll repost updated patch.
Br,
Harri
prev parent reply other threads:[~2010-06-24 14:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-23 19:10 [PATCH] audio: fix memory leak with typefinding harri.mahonen
2010-06-24 7:52 ` Luiz Augusto von Dentz
2010-06-24 8:09 ` Luiz Augusto von Dentz
2010-06-24 14:36 ` Harri Mähönen [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=AANLkTinpwLVnJwrAyDS87p0wavVFCNzssiNJl7TkyTaE@mail.gmail.com \
--to=harri.mahonen@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).