From: David Miller <davem@davemloft.net>
To: marcel@holtmann.org
Cc: netdev@vger.kernel.org
Subject: Re: Pull request: bluetooth-2.6 2010-01-30
Date: Sun, 31 Jan 2010 23:35:38 -0800 (PST) [thread overview]
Message-ID: <20100131.233538.125549914.davem@davemloft.net> (raw)
In-Reply-To: <cover.1264859950.git.marcel@holtmann.org>
From: Marcel Holtmann <marcel@holtmann.org>
Date: Sat, 30 Jan 2010 06:08:43 -0800
> this includes two L2CAP fixes. One for a memory leak and another one for
> a double free.
>
> For Bluetooth PCMCIA cards a BUG_ON caused a few issues when we have
> shared interrupts. So revert this and put a clear comment in the source
> that this is what we actually want.
>
> The Bluetooth HID fix for raw reports has a big diffstat, but the logical
> change is small. By accident we send the reports on the interrupt channel
> and the original test device seems to cope with that. Devices that follow
> the specification more closer will break. The right thing is to use the
> control channel. This is similar to what is done via USB.
>
> And by request from Luis, include the driver for Atheros Bluetooth chipset
> AR3011. It is a new driver and by itself small and self contained. If you
> feel that it should not be merged, then let me know and I redo this
> patchset.
Pulled, thanks Marcel.
prev parent reply other threads:[~2010-02-01 7:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-30 14:08 Pull request: bluetooth-2.6 2010-01-30 Marcel Holtmann
2010-01-30 14:08 ` [PATCH 1/5] Bluetooth: Remove double free of SKB pointer in L2CAP Marcel Holtmann
2010-01-30 14:08 ` [PATCH 2/5] Bluetooth: Fix memory leak " Marcel Holtmann
2010-01-30 14:08 ` [PATCH 3/5] Bluetooth: Redo checks in IRQ handler for shared IRQ support Marcel Holtmann
2010-01-30 14:08 ` [PATCH 4/5] Bluetooth: Add DFU driver for Atheros Bluetooth chipset AR3011 Marcel Holtmann
2010-01-30 14:08 ` [PATCH 5/5] Bluetooth: Use the control channel for raw HID reports Marcel Holtmann
2010-02-01 7:35 ` David Miller [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=20100131.233538.125549914.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=marcel@holtmann.org \
--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).