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 4/4 v2] Add proper tracking mechanism to NREC
Date: Wed, 19 Jan 2011 20:53:51 +0530 [thread overview]
Message-ID: <20110119152351.GH2112@jh-x301> (raw)
In-Reply-To: <1295352671-5533-1-git-send-email-luiz.dentz@gmail.com>
Hi Luiz,
On Tue, Jan 18, 2011, Luiz Augusto von Dentz wrote:
> NREC may change during the connections so it has to be tracked in order
> to signal changes to applications.
> ---
> audio/headset.c | 55 ++++++++++++++++++++++++++++++++++++++++++++++++++++-
> audio/headset.h | 6 +++++
> audio/transport.c | 19 ++++++++++++++++++
> 3 files changed, 79 insertions(+), 1 deletions(-)
I didn't realize there was a v2 of this and I already went ahead and
pushed v1. What was the difference? Can you send a patch to update the
upstream tree to whatever this v2 does?
Johan
next prev parent reply other threads:[~2011-01-19 15:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-18 12:11 [PATCH 4/4 v2] Add proper tracking mechanism to NREC Luiz Augusto von Dentz
2011-01-19 15:23 ` Johan Hedberg [this message]
2011-01-19 16:51 ` Johan Hedberg
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=20110119152351.GH2112@jh-x301 \
--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