public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: "Gustavo F. Padovan" <gustavo@padovan.org>
To: Ron Shaffer <rshaffer@codeaurora.org>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: [PATCH 0/1] Bluetooth: Synchronize SCO/eSCO connection requests to ACL state
Date: Mon, 24 May 2010 18:19:16 -0300	[thread overview]
Message-ID: <20100524211916.GB5241@vigoh> (raw)
In-Reply-To: <4BFAEB5C.4040300@codeaurora.org>

Hi Ron,

* Ron Shaffer <rshaffer@codeaurora.org> [2010-05-24 16:10:52 -0500]:

> Marcel:
> 
> This patch resolves some issues with what looks to be certain CSR
> based headsets. When requesting SCO or eSCO while the connection
> is transitioning from sniff to active, i.e. unsniff has been requested
> but the headset has not responded with accepted, these headsets seem
> to enter a state where they don't positively respond the SCO/eSCO
> request. This was first noticed in and Motorola H350 Headset.
> 
> In addition, I've cleaned up some extraneous spaces and the original
> Copyright has been changed from Qualcomm to Code Aurora Forum as
> Qualcomm has reassigned these rights to Code Aurora Forum.

Could you please split this patch in 3 patches? Clearly it mixes 3 things:
your fix, the copyright change, and the cleanup.

> 
> -- 
> Ron Shaffer
> Qualcomm Innovation Center, Inc.
> Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
Gustavo F. Padovan
http://padovan.org

      reply	other threads:[~2010-05-24 21:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-24 21:10 [PATCH 0/1] Bluetooth: Synchronize SCO/eSCO connection requests to ACL state Ron Shaffer
2010-05-24 21:19 ` Gustavo F. Padovan [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=20100524211916.GB5241@vigoh \
    --to=gustavo@padovan.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=rshaffer@codeaurora.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