Linux bluetooth development
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: Dmitriy Paliy <dmitriy.paliy@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, Dmitriy Paliy <dmitriy.paliy@nokia.com>
Subject: Re: [PATCH 1/2] Add NO CARRIER response to HFP
Date: Mon, 18 Apr 2011 10:50:21 +0300	[thread overview]
Message-ID: <20110418075021.GA6013@jh-x301> (raw)
In-Reply-To: <1303075754-15375-1-git-send-email-dmitriy.paliy@nokia.com>

Hi Dmitriy,

On Mon, Apr 18, 2011, Dmitriy Paliy wrote:
> HFP is updated by NO CARRIER response accordingly to HFP 1.5 p.68.
> ---
>  audio/headset.c |   17 ++++++++++-------
>  1 files changed, 10 insertions(+), 7 deletions(-)

Both patches have been pushed upstream after I fixed your author email
(please fix your git config) and a minor coding style issue in the
second patch.

Johan

      parent reply	other threads:[~2011-04-18  7:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-17 21:29 [PATCH 1/2] Add NO CARRIER response to HFP Dmitriy Paliy
2011-04-17 21:29 ` [PATCH 2/2] Add NO CARRIER reponse to maemo6 telephony driver Dmitriy Paliy
2011-04-18  7: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=20110418075021.GA6013@jh-x301 \
    --to=johan.hedberg@gmail.com \
    --cc=dmitriy.paliy@gmail.com \
    --cc=dmitriy.paliy@nokia.com \
    --cc=linux-bluetooth@vger.kernel.org \
    /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