netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: Bluetooth update for 2.6
Date: Thu, 28 Sep 2006 23:14:44 +0200	[thread overview]
Message-ID: <1159478084.21120.75.camel@localhost> (raw)
In-Reply-To: <20060927.225817.106770711.davem@davemloft.net>

Hi Dave,

> > > here are the pending patches that didn't make it into the 2.6.18 kernel
> > > release. I have some additional fixes, but all of them need some more
> > > additional testing from my side.
> > 
> > it seems that you haven't pulled in these changes so far. So I didn't
> > rebase the tree and simply pushed some additional ones on top of it. All
> > three of them address the issues we had with non-blocking connects.
> 
> I applied all of your fixes into my tree, sorry for taking so long.

no big problem. If you haven't synced with Linus yet, then I have two
small additional fixes that should go in with the others.

Regards

Marcel


Please pull from

        git://git.kernel.org/pub/scm/linux/kernel/git/holtmann/bluetooth-2.6.git

This will update the following files:

 net/bluetooth/hci_event.c |    8 ++++----
 net/bluetooth/hci_sysfs.c |    2 +-
 2 files changed, 5 insertions(+), 5 deletions(-)

through these ChangeSets:

Marcel Holtmann <marcel@holtmann.org> Thu, 28 Sep 2006 20:23:29 +0200 

    [Bluetooth] Fix section mismatch of bt_sysfs_cleanup()
    
    The bt_sysfs_cleanup() is marked with __exit attribute, but it will
    be called from an __init function in the error case. So the __exit
    attribute must be removed.
    
    Signed-off-by: Arnaud Patard <arnaud.patard@rtp-net.org>
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>

Marcel Holtmann <marcel@holtmann.org> Tue, 26 Sep 2006 22:18:03 +0200 

    [Bluetooth] Don't update disconnect timer for incoming connections
    
    In the case of device pairing the only safe method is to establish
    a low-level ACL link. In this case, the remote side should not use
    the disconnect timer to give the other side the chance to enter the
    PIN code. If the disconnect timer is used, the connection will be
    dropped to soon, because it is impossible to identify an actual user
    of this link.
    
    Signed-off-by: Marcel Holtmann <marcel@holtmann.org>




  reply	other threads:[~2006-09-28 21:14 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-21 19:47 Bluetooth update for 2.6 Marcel Holtmann
2006-09-26 10:46 ` Marcel Holtmann
2006-09-28  5:58   ` David Miller
2006-09-28 21:14     ` Marcel Holtmann [this message]
2006-09-28 22:30       ` David Miller
  -- strict thread matches above, loose matches on Subject: below --
2006-11-19  0:34 Marcel Holtmann
2006-11-21  0:14 ` David Miller
2006-10-20  7:49 Marcel Holtmann
2006-10-20  8:16 ` David Miller
2006-10-15 16:10 Marcel Holtmann
2006-10-16  6:13 ` David Miller
2006-07-14 14:38 Marcel Holtmann
2006-07-18 17:08 ` Marcel Holtmann
2006-07-12 21:49 Marcel Holtmann
2006-07-12 22:34 ` David Miller
2006-07-06 20:09 Marcel Holtmann
2006-07-07  7:17 ` David Miller
2006-07-07 22:54   ` Marcel Holtmann
2006-07-07 23:14     ` David Miller

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=1159478084.21120.75.camel@localhost \
    --to=marcel@holtmann.org \
    --cc=davem@davemloft.net \
    --cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).