From: "Maksim (Max) " Krasnyanskiy <maxk@qualcomm.com>
To: torvalds@transmeta.com, linux-kernel@vger.kernel.org
Subject: [BK 1/6] 2.5.x Bluetooth subsystem update. Core.
Date: 05 Oct 2002 15:25:37 -0700 [thread overview]
Message-ID: <1033856154.6656.87.camel@champ.qualcomm.com> (raw)
Hi Linus,
Here is the set of patches to sync up 2.5.x Bluetooth subsytem with
2.4.x and add latest fixes and features.
You can either pull all of them from:
bk://linux-bt.bkbits.net/bt-2.5
Or apply them indivdually. Patches are pretty big and therefor not
inlined.
Patch #1:
# This is a BitKeeper generated patch for the following project:
# Project Name: Linux kernel tree
# This patch format is intended for GNU patch command version 2.5 or
higher.
# This patch includes the following deltas:
# ChangeSet 1.597 -> 1.598
# net/bluetooth/hci_event.c 1.1 -> 1.2
# net/bluetooth/lib.c 1.3 -> 1.4
# net/bluetooth/af_bluetooth.c 1.4 -> 1.5
# net/bluetooth/sco.c 1.2 -> 1.3
# net/bluetooth/hci_core.c 1.6 -> 1.7
# include/net/bluetooth/bluetooth.h 1.4 -> 1.5
# include/net/bluetooth/hci_core.h 1.3 -> 1.4
# net/bluetooth/hci_sock.c 1.5 -> 1.6
# net/bluetooth/l2cap.c 1.6 -> 1.7
# include/net/bluetooth/hci.h 1.3 -> 1.4
# net/bluetooth/hci_conn.c 1.1 -> 1.2
#
# The following is the BitKeeper ChangeSet Log
# --------------------------------------------
# 02/10/04 root@viper.(none) 1.598
# Sync up Bluetooth core with 2.4.x.
# SMP locking fixes.
# Support for Hotplug.
# Support for L2CAP connectionless channels (SOCK_DGRAM).
# HCI filter handling fixes.
# Other minor fixes and cleanups.
# --------------------------------------------
http://bluez.sourceforge.net/patches/bt-2.5-core.gz
Max
next reply other threads:[~2002-10-05 22:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-05 22:25 Maksim (Max) Krasnyanskiy [this message]
2002-10-05 23:47 ` [BK 1/6] 2.5.x Bluetooth subsystem update. Core Linus Torvalds
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=1033856154.6656.87.camel@champ.qualcomm.com \
--to=maxk@qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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