From: David Miller <davem@davemloft.net>
To: ohad@bencohen.org
Cc: marcel@holtmann.org, linux-kernel@vger.kernel.org,
bluez-devel@lists.sourceforge.net
Subject: Re: [PATCH][FIX] Bluetooth: always send explicit hci_ll wake-up acks
Date: Thu, 10 Jan 2008 22:24:56 -0800 (PST) [thread overview]
Message-ID: <20080110.222456.209443591.davem@davemloft.net> (raw)
In-Reply-To: <tkrat.091a3ceefb96c3e3@bencohen.org>
From: Ohad Ben-Cohen <ohad@bencohen.org>
Date: Mon, 7 Jan 2008 18:22:48 +0200 (IST)
> In the (rare) event of simultaneous mutual wake up requests,
> do send the chip an explicit wake-up ack. This is required
> for Texas Instruments's BRF6350 chip.
>
> Signed-off-by: Ohad Ben-Cohen <ohad@bencohen.org>
Applied, thanks.
next prev parent reply other threads:[~2008-01-11 6:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-07 16:22 [PATCH][FIX] Bluetooth: always send explicit hci_ll wake-up acks Ohad Ben-Cohen
2008-01-07 18:58 ` [Bluez-devel] [PATCH] headset.c fixes Alok
2008-01-11 6:24 ` David Miller [this message]
2008-01-11 7:58 ` [PATCH][FIX] Bluetooth: always send explicit hci_ll wake-up acks Ohad Ben-Cohen
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=20080110.222456.209443591.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bluez-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=ohad@bencohen.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