public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] patch-2.6.7-mh
Date: Thu, 02 Dec 2004 08:02:00 +0100	[thread overview]
Message-ID: <1101970920.15615.69.camel@pegasus> (raw)
In-Reply-To: <200412020151.06979.gillan82@centrum.cz>

Hi Gillan,

> I tried to do it by myself, but I'm too lame for that. Have anybody this patch 
> on locale? I'm looking for patch-2.6.7-mhX.gz .. thanks.

the latest one for 2.6.7 is -mh4. Besides the test patches these are the
ones that are missing between 2.6.7-mh4 and 2.6.9-mh4:

  o Check checksums for BNEP
  o Don't send L2CAP reject command for bad responses
  o Don't use ISOC transfers for Broadcom dongle
  o Stop TX task before notifying the driver
  o Add security manager flags and options
  o Add module parameter for disabling ISOC transfers
  o Let the CAPI free the SKB in the error case
  o Fix race when unlinking incoming connections
  o Improve connection hash handling
  o Allow vendor specific packet types
  o Fix another disconnect race
  o Ignore the BPA 100/105 devices
  o Add security callback to the core
  o Send HCI_Reset for new Microsoft dongle
  o Check for L2CAP reliability
  o Add support for L2CAP secure mode
  o Correct locking for zero SCID responses
  o Update copyright information
  o Some trivial s/int/unsigned int/
  o Make some functions static
  o Support responses with zero SCID
  o Add function for triggering a link key change
  o Use usb_kill_urb() for synchronous unlink
  o Fix connection hash bug

Regards

Marcel




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

      reply	other threads:[~2004-12-02  7:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-01 14:38 [Bluez-users] patch-2.6.7-mh Gillan
2004-12-01 14:47 ` Marcel Holtmann
2004-12-01 14:53   ` Gillan
2004-12-01 15:00     ` Marcel Holtmann
2004-12-02  0:51       ` Gillan
2004-12-02  7:02         ` Marcel Holtmann [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=1101970920.15615.69.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-users@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox