From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: [Bluez-devel] Bluetooth kernel patch for 2.6.1
Date: Thu, 15 Jan 2004 20:07:29 +0100 [thread overview]
Message-ID: <1074193649.2629.23.camel@pegasus> (raw)
Hi Folks,
the third Bluetooth kernel patch for 2.6.1 is now available [1]. It
fixes the inquiry after boot problem and the RFCOMM reference counting
bug. Here is the changelog:
o Change maintainer role of the Bluetooth subsystem
o Start inquiry if cache is empty
o Fix reference counting for incoming connections
Regards
Marcel
[1] http://www.holtmann.org/linux/kernel/patch-2.6.1-mh3.gz
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2004-01-15 19:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-15 19:07 Marcel Holtmann [this message]
2004-01-15 19:50 ` BCM2033 firmware loader [was Re: [Bluez-devel] Bluetooth kernel patch for 2.6.1] Max Krasnyansky
2004-01-15 20:16 ` [Bluez-devel] Re: BCM2033 firmware loader Marcel Holtmann
2004-01-16 21:14 ` Max Krasnyansky
2004-01-17 1:19 ` [Bluez-devel] " Marcel Holtmann
2004-01-20 19:27 ` Max Krasnyansky
2004-01-15 20:03 ` [Bluez-devel] Bluetooth kernel patch for 2.6.1 Max Krasnyansky
2004-01-15 20:30 ` Marcel Holtmann
2004-01-16 21:25 ` Max Krasnyansky
2004-01-17 1:08 ` Marcel Holtmann
2004-01-20 19:23 ` Max Krasnyansky
2004-01-21 1:36 ` Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2004-01-13 3:59 Marcel Holtmann
2004-01-09 14:56 Marcel Holtmann
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=1074193649.2629.23.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.