From: Gustavo Padovan <padovan@profusion.mobi>
To: Szymon Janc <szymon@janc.net.pl>
Cc: linux-bluetooth@vger.kernel.org, Peter Hurley <peter@hurleysoftware.com>
Subject: Re: [PATCH] Don't use cmd_timer to timeout HCI reset command
Date: Mon, 1 Aug 2011 16:30:06 -0300 [thread overview]
Message-ID: <20110801193006.GC18480@joana> (raw)
In-Reply-To: <1311713214-2414-1-git-send-email-szymon@janc.net.pl>
Hi Szymon,
* Szymon Janc <szymon@janc.net.pl> [2011-07-26 22:46:54 +0200]:
> No command should be send before Command Complete event for HCI
> reset is received. This fix regression introduced by commit
> 6bd32326cda(Bluetooth: Use proper timer for hci command timout)
> for chips whose reset command takes longer to complete (e.g. CSR)
> resulting in next command being send before HCI reset completed.
>
> Signed-off-by: Szymon Janc <szymon@janc.net.pl>
> ---
> net/bluetooth/hci_core.c | 6 ++++--
> 1 files changed, 4 insertions(+), 2 deletions(-)
Applied, thanks.
Gustavo
prev parent reply other threads:[~2011-08-01 19:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-26 20:46 [PATCH] Don't use cmd_timer to timeout HCI reset command Szymon Janc
2011-08-01 19:30 ` Gustavo 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=20110801193006.GC18480@joana \
--to=padovan@profusion.mobi \
--cc=linux-bluetooth@vger.kernel.org \
--cc=peter@hurleysoftware.com \
--cc=szymon@janc.net.pl \
/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).