From: Max Krasnyansky <maxk@qualcomm.com>
To: Marcelo Tosatti <marcelo@conectiva.com.br>
Cc: linux-kernel@vger.kernel.org
Subject: [BK] Bluetooth updates for 2.4.21-pre4
Date: Tue, 25 Feb 2003 12:58:57 -0800 [thread overview]
Message-ID: <5.1.0.14.2.20030225125619.02015ce8@mail1.qualcomm.com> (raw)
In-Reply-To: <Pine.LNX.4.53L.0302251738170.16726@freak.distro.conectiva>
At 12:38 PM 2/25/2003, Marcelo Tosatti wrote:
>On Mon, 24 Feb 2003, Tomas Szepe wrote:
>
>> It's been 4 weeks since 2.4.21-pre4 went out and the pre4->current
>> diff is over 3 megabytes. Anything special holding off -pre5?
>>
>> I wouldn't be surprised if Alan had 100+ patches queued up
>> to be merged after a new tag release.
>
>I'm very late yes. I will release it today or tomorrow.
Before you do that could you please pull a couple of Bluetooth fixes from
bk pull bk://linux-bt.bkbits.net/bt-2.4
This will update the following files:
include/net/bluetooth/hci.h | 104 +++++++++++++-------------
include/net/bluetooth/hci_core.h | 12 +--
net/bluetooth/hci_core.c | 118 ++++++++++-------------------
net/bluetooth/hci_sock.c | 156 +++++++++++++++++++++------------------
net/bluetooth/syms.c | 6 -
5 files changed, 191 insertions(+), 205 deletions(-)
through these ChangeSets:
<maxk@qualcomm.com> (03/01/27 1.884.1.113)
[Bluetooth] Add support for vendor specific commands.
All vendor commands are treated as raw data and
applications are responsible for flow control.
Thanks
Max
next prev parent reply other threads:[~2003-02-25 20:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-24 14:37 What's up with pre5? Tomas Szepe
2003-02-24 15:51 ` Maciej Soltysiak
2003-02-25 0:30 ` David Woodhouse
2003-02-25 20:38 ` Marcelo Tosatti
2003-02-25 20:58 ` Max Krasnyansky [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-14 22:15 [BK] Bluetooth updates for 2.4.21-pre4 Max Krasnyansky
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=5.1.0.14.2.20030225125619.02015ce8@mail1.qualcomm.com \
--to=maxk@qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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
all inboxes | Powered by JetHome®